Explore skills
Showing 49411–49440 of 71536 skills
Follows one rated assembly as a continuous surface rather than as a wall type on a plan: establishes what kind of separation it is and therefore what continuity the code demands, traces it from floor slab to deck above and along its full length, and works every place the rating is interrupted by a penetration, a joint, a duct, a door, a glazed opening or the structure it is attached to. Trigger on "fire barrier detail", "rated wall continuity", "does this wall go to deck", "firestopping at the top of wall", "fire partition versus fire barrier", "rated assembly penetrations", "design-fire-barrier", or a rated wall named with a question about how it is built. Carries no hourly ratings, no opening limits, no tested assembly numbers and no firestop listings; the required rating comes from `/test-fire-rating` or your code analysis, and every assembly and firestop is a tested and listed system you cite. It does not replace the fire protection engineer, the code consultant, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexThe door into interior work, and the step that is usually missing: before partitions, ceilings, millwork or finishes are drawn, establish what each space actually has to withstand, where the money should go, which spaces repeat and which get attention, and what the base building has already decided. Produces the strategy the specific skills then execute against, and hands each part off by name. Trigger on "design the interior", "interior strategy", "where do we spend on this fit-out", "what finishes for this project", "the interior feels arbitrary", "design-interior", or an interior scope with no strategy behind it. Carries no finishes, no specifications, no costs and no ratings; every requirement comes from the brief, the client's operation, or the code you quote. It details nothing itself — `design-partition`, `design-ceiling`, `design-millwork` and `schedule-builder` do that — and does not replace the interior designer or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexLays out a domestic or small commercial kitchen from the sequence of work rather than from a triangle: where things arrive, where they are stored, prepared, cooked, served and cleaned, and what has to be within reach of what. Then works the two things that decide whether the layout survives — where the services can actually go, and what the ventilation demands of the plan and the elevation. Trigger on "kitchen layout", "design the kitchen", "galley or island", "where does the hood vent", "kitchen work triangle", "design-kitchen", or a kitchen with appliances chosen and nowhere settled. Carries no clearances, no aisle widths, no appliance dimensions and no ventilation rates; each comes from the code you quote, the accessibility standard, or the appliance's own data. Commercial kitchens beyond a small back-of-house are a specialist consultant's. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexLays out a mechanical plant room from the equipment schedule the engineer gives you, and adds the four things that make it bigger than the equipment: the service clearances each unit needs, the route to get equipment in during construction and out at replacement, the air the room itself has to take in and exhaust, and the connections that leave it. Reports the required footprint and height against what is drawn. Trigger on "size the mechanical room", "plant room layout", "will the AHU fit", "how do we get the chiller in", "mechanical room design", "design-mechanical-room", or an equipment schedule handed over with a room to put it in. Carries no equipment dimensions, no clearances, no ventilation rates and no code requirements; all come from the engineer, the manufacturer and the code text you quote. It does not select or size equipment and does not replace the MEP engineer or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexDetails built-in joinery to the point a shop can price it without asking: what is fixed and what moves, how it meets a floor and a wall that are neither level nor straight, what it hangs off and whether that backing exists, where the services in it come from, and which decisions are the shop's rather than the drawing's. Trigger on "millwork", "casework", "joinery detail", "built-in", "reception desk", "how does this cabinet meet the wall", "design-millwork", or a built-in element that has to be drawn for tender. Carries no dimensions, no clearances, no material thicknesses and no hardware; ergonomic and accessible dimensions come from the standard you quote and every material figure from the fabricator or the data sheet. It is not shop drawing — `submittal-review` reads those when they come back — and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWrites the project description that gets asked for again and again in different lengths and for different readers: a planning submission, a design review board, an award entry, a website page, a client's own report. Establishes who is reading and what they can do about it before writing a word, since a board that can refuse and a magazine that cannot are different documents, then builds one account of the project that the shorter versions are cut from rather than rewritten. Trigger on "design narrative", "project description", "write up the project", "we need a paragraph for the submission", "award entry text", "design-narrative", or a request for words about a building. Carries no house voice and no claims of its own; every fact comes from the project and every claim has to be true of the drawings. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWorks a parapet as the junction of two assemblies rather than as a wall that continues past the roof: takes the wall build-up and the roof build-up you already have, then carries each of the four control layers (water, air, vapor, thermal) up the inside face, over the top and down the outside, naming where each one transfers from one assembly to the other and what happens at the coping, the through-wall flashing, the corners and every interruption. Trigger on "design a parapet", "parapet detail", "coping", "where does the air barrier turn at the roof", "through-wall flashing at the parapet", "parapet thermal bridge", "design-parapet", or a wall and a roof named with a request for how they meet at the top. Supplies the ordering and transfer logic and the questions each condition has to answer; supplies no height, no thickness, no slope, no code requirement and no proprietary product. Requires the two assemblies as input and does not design either of them.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexLays out a parking floor from the module rather than from the space left over: settles the bay and aisle dimensions and the column grid that follows from them, works the ramp against the floor-to-floor it has to climb, places accessible spaces where the standard requires them rather than where they fit, and reports the count achieved against the count required. Trigger on "parking layout", "how many cars fit", "parking bay module", "ramp slope and transitions", "where do the accessible spaces go", "design-parking-layout", or a garage floor plate with a count to hit. Carries no bay dimensions, no aisle widths, no ramp slopes, no headroom and no accessible ratios; every one comes from the jurisdiction's standard or the accessibility standard you quote. `/test-parking` counts what is required. It does not do traffic or structural engineering and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds an interior partition type from what the partition has to do rather than from a wall type legend copied forward: takes the acoustic separation, the fire rating, the structural condition above and what has to be fixed to it, then works the build-up and the two decisions that decide whether it performs — how far up it goes, and what happens at the head where the structure above moves. Trigger on "partition type", "interior wall build-up", "does this wall go to deck", "STC between these rooms", "deflection head detail", "wall type legend", "design-partition", or a room adjacency with a question about the wall between. Carries no ratings, no STC values, no stud spacings and no listings; performance comes from the specification or the acoustician and every rated assembly is a tested system you cite. For an exterior wall use `design-wall-assembly`; for a rated assembly's continuity use `design-fire-barrier`. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds a low-slope or steep-slope roof assembly from what the roof has to do rather than from a remembered stack: takes the membrane or covering, the deck, the climate, the interior humidity, the equipment landing on it and the slope you have to work with, then places the four control layers (water, air, vapor, thermal) in an order, gives every layer a stated job, and works the curbs, drains, penetrations and edges where roofs actually leak. Trigger on "design a roof assembly", "roof build-up", "compact roof", "what goes above the deck", "insulation above or below the deck", "vented or unvented roof", "design-roof-assembly", or a membrane and a deck named with a request for what sits between them. Supplies the ordering logic and the questions each condition has to answer; supplies no R-value, no permeance, no slope minimum, no code requirement and no proprietary product. The arithmetic belongs to condensation-check and the continuity audit to air-barrier-trace, both of which this hands off to.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWorks roof drainage as the architectural half of a problem the plumbing engineer sizes: where the falls come from and what they cost the build-up, where the drains land against the structure and the spaces below, where the secondary drainage goes and whether anyone would notice it running, and what the roof weighs if the primary drains block. Trigger on "roof drainage", "where do the drains go", "tapered insulation layout", "overflow scuppers", "is the roof ponding", "design-roof-drainage", or a roof plan with a question about falls. Carries no drain sizes, no rainfall intensities, no slope minimums and no code requirements; sizing is the plumbing engineer's against the code you quote, and the ponding load is the structural engineer's. `design-roof-assembly` builds the stack and names this as out of its scope. It does not replace the engineers or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexChecks one stair flight item by item: width, headroom, riser, tread, uniformity, nosing, landing, vertical rise between landings, handrail height, wall clearance, cross section, extensions, both-sides requirement, and open risers. Trigger on "check stair", "stair compliance", "stair dimension check", "riser tread check", "handrail extension", "stair code check", "IBC 1011", "ADA stair", "OBC stair", "NBC stair", or pasted stair geometry. Works in any jurisdiction. The user names the governing code and edition, then supplies each limit by typing it, pasting the clause, or naming a file to read. The skill never supplies a code value from memory or from web search, and any row without a supplied limit is reported as unverified rather than guessed. Does not replace the Architect or Engineer of Record, and does not cover curved, spiral, winder, or alternating tread stairs.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds an exterior wall assembly from what the wall has to do rather than from a remembered stack: takes the cladding, the structure, the climate, the fire and acoustic demands and the drying direction you state, then places the four control layers (water, air, vapor, thermal) in an order, gives every layer a stated job, and works each interface where two layers meet and each transition where the wall stops. Trigger on "design a wall assembly", "wall build-up", "what goes in this wall", "layer the exterior wall", "where does the air barrier go", "rainscreen build-up", "design-wall-assembly", or a cladding and a structure named with a request for what sits between them. Supplies the ordering logic and the questions each interface has to answer; supplies no R-value, no permeance, no code minimum and no proprietary product. The arithmetic on the finished stack belongs to condensation-check and the continuity audit to air-barrier-trace, both of which this hands off to.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexDetails the three sides of an opening as a sequence rather than as three sections: takes the wall assembly, the window type and how it is anchored, then works the head, the jamb and the sill in the order the trades actually build them, laps each control layer over the one below it, and names where water that gets past the window is collected and put back out. Trigger on "window head jamb sill", "window perimeter detail", "sill pan", "flashing sequence at an opening", "how does the air barrier close at a window", "punched opening detail", "design-window-perimeter", or a window and a wall build-up named with a request for how they meet. Supplies the sequencing and lap logic and the questions each side has to answer; supplies no dimension, no shim space, no sealant joint size, no code requirement and no proprietary product. Requires the wall assembly as input and does not design it. It does no structural work and does not replace the enclosure consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexCompares two versions of a written document — an agreement, a specification section, a programme, a code analysis, an owner's requirements — and reports every change, not the ones the covering note listed. Separates a wording change from a change in obligation, flags every deletion because deletions are what a redline is worst at showing, and reports what moved rather than changed, since relocated text reads as unchanged in most comparisons. Trigger on "what changed between these two versions", "compare these contracts", "diff this spec section", "they sent a revised agreement", "document-diff", or two versions of anything written handed over together. Carries no view on what any clause should say; `contract-review` and `spec-review` read one version on its merits. It is not legal advice and does not replace the attorney or the Architect of Record. For drawings use `drawing-diff`.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexMaintains a drawing issue log in docs/drawings/log.md: every sheet in the set, its current revision, and every dated issuance with its purpose. Trigger on "drawing log", "issue log", "sheet log", "revision log", "what rev is", "when did we issue", "drawing register", "drawing-log", or a request to record that a set went out. The sheet list can be seeded from a drawing-set-bookmarker index or typed; revisions and issue dates come from you, never from a guess. Superseded sheets are marked, not deleted, so the log answers what was in force on any past date. It records what was issued to whom; the cover sheet for a package is create-transmittal's job, and what changed inside a sheet is drawing-diff's.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexSweeps a whole drawing set for the conventions that decide whether it can be read: whether the sheet index matches the sheets, whether every reference lands on something that exists, whether the title block is complete and consistent, whether symbols and abbreviations are used as the legend defines them, and whether the same information appears twice with two answers. Reports by frequency so the systematic problems separate from the isolated ones. Trigger on "drawing standards audit", "check the set for consistency", "do the references resolve", "title block check", "is this set ready to issue", "drawing-standards-audit", or a set handed over before issue. Carries no office standard, no layer convention and no line weight table; the standard comes from your office or the project's own set. It reviews conventions rather than content — `drawing-checklist` covers what a phase should contain and `spec-review` covers the book. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads any elevation for the two things it is doing at once: composing a facade, and hiding the depth that makes it buildable. An elevation is a flat drawing of something that is not flat, so joints, reveals, returns, thicknesses and everything behind the surface are all drawn as lines of equal weight or not at all. Checks what it commits to, what it leaves to a section, and where it disagrees with the plan. Trigger on "read this elevation", "does this facade work", "they sent elevations", "check this elevation against the plan", "elevation-review", or any elevation handed over. Carries no dimensions or module sizes; anything measured is read at the stated scale. `facade-module` divides an elevation into panels and `design-envelope` decides what each face has to be; this reads the drawing. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexKeeps one dated record of a project's embodied carbon as the design changes: quantities from your own take-off, factors from the data source you name, and the result kept per element and per life-cycle stage rather than as one number, because a single figure hides which decision moved it. Records the boundary and the data vintage on every entry, since two projects' figures are comparable only when both are stated. Trigger on "embodied carbon", "track the carbon on this design", "whole life carbon", "EPD", "upfront carbon", "A1-A3", "embodied-carbon-tracker", or a material change with a question about its carbon. Carries no emission factors and no benchmarks; every factor comes from an EPD or a database you name, with its vintage. `decarbonization-strategist` plans the operational path over years; this counts what the materials carry. It is not an LCA and does not replace the sustainability consultant.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexKeeps one dated record of a discretionary land use approval, which behaves nothing like a permit: the decision-maker is a body that meets on a calendar, the outcome is negotiated rather than checked, and the conditions attached at the end become obligations the project carries for its life. Logs every submission, every hearing, every commitment made in a room, and every condition with what discharges it and who owns it. Trigger on "entitlement tracker", "track the rezoning", "planning approval log", "what did we commit to at the hearing", "conditions of approval", "entitlement-tracker", or a discretionary application handed over to keep track of. Carries no process, no timelines and no hearing calendars; all come from the jurisdiction. It does not track building permits — `permit-tracker` does — and does not replace the land use attorney, the planner, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds the envelope checklist for one project rather than handing over a generic one: takes the assemblies this building actually has and the phase it is at, and produces what should be resolved by now, what can still wait, and what is already late. Works from the junction list rather than from the assemblies, because assemblies get drawn and junctions get discovered. Trigger on "envelope checklist", "what should be resolved by DD", "are we ready to issue the envelope", "what have we missed on the facade", "envelope-checklist", or an envelope scope at a phase change. Carries no standard checklist and no performance values; the items come from the assemblies and junctions this project has. `drawing-checklist` covers the drawing set by phase; this covers the envelope by what it is made of. It does not replace the enclosure consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexCompares two versions of an envelope assembly or detail and reports what the change does rather than what it looks like: which control layer moved, what continuity was gained or lost, which junction details are now wrong, and whether the drying direction changed. Built for the moment a contractor proposes an alternate, a manufacturer's detail replaces yours, or a value-engineering round comes back, because those changes arrive one layer at a time and their consequences arrive at the junctions. Trigger on "what changed in this assembly", "they proposed a different build-up", "compare these two sections", "is this substitution equivalent", "envelope-diff", or two versions of an envelope construction handed over together. Carries no values; every figure comes with the versions. `document-diff` compares written documents and `drawing-diff` drawing revisions; this compares what an assembly does. It does not replace the enclosure consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads any product or equipment data sheet and pulls out the six things a building has to provide for it: the space it occupies, the clearance it needs on each side to be serviced, the route to get it in and out, the services it needs and from where, what it weighs and what carries it, and what it does to the room around it in heat, noise and vibration. Works for a rooftop unit, a lift, a range, a transformer, a door closer or a light fitting. Trigger on "read this cut sheet", "what does this unit need", "they sent product data", "will this fit", "equipment-reader", or a data sheet handed over with a question about space. Carries no dimensions or clearances of its own: every figure comes off the sheet, and a figure absent from the sheet is reported missing rather than assumed from a similar product. It does not select or size equipment and does not replace the engineers or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexPlans and records a measured survey of an existing building so that every dimension later designed against carries its provenance: what to capture before going, how to close a measurement so errors are caught on site rather than in the office, and the discipline of marking every line as measured, taken from a record drawing, or assumed. Produces the record and the list of what still has to be opened up or verified. Trigger on "measure the existing building", "as-built survey", "existing conditions", "we only have the old drawings", "what do I measure on the site visit", "existing-conditions-survey", or a renovation starting with no reliable information. Carries no tolerances and no survey standards; the level of accuracy needed comes from what the drawings will be used for. It is not a land survey — `survey-review` reads one — and not a structural, hazardous materials, or condition assessment, each of which is a specialist's and is named as a hand-off.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWorks out how every part of a building's envelope will be reached after it is built: cleaned, inspected, repaired, and, for glass, replaced. Inventories the envelope by zone, holds candidate access methods against each one — reach from grade, rope descent, davits, a building maintenance unit, interior access — and reports what each method demands of the design now: roof space, structure, anchors, parapets, and ground kept clear. Trigger on "facade access", "how do we clean this", "window washing", "BMU", "davits", "rope access", "facade-access-study", "how does the glass get replaced", or a tall or complex envelope with no maintenance story. The zoning of the envelope and the demands table are the skill's method; every load, every regulation, and every equipment figure comes from elsewhere: anchor and davit loads are the structural engineer's, the rules for suspended access are regulatory text the user quotes, and reach figures come from the equipment's own data.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a geotechnical report from the architect's side: separates what was actually investigated from what was inferred between boreholes, pulls out every recommendation that becomes a design obligation, finds the conditions the report makes contingent on something happening later, and reports what it means for the building rather than for the foundation engineer. Trigger on "review the geotech report", "what does this soils report mean for us", "read the geotechnical recommendations", "borehole log review", "geotech-report-review", or a soils report handed over at the start of design. Carries no bearing values, no soil classifications and no design parameters; every figure comes from the report, quoted. It is not geotechnical engineering, does not verify a recommendation, and does not replace the geotechnical engineer, the structural engineer, or the Architect of Record. For one recommendation in plain English use `/explain-soils`.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexScores a pursuit before the proposal is written, against the factors that actually predict whether a project is won and whether it is worth winning: the relationship, the client's decision process and funding, the competition, the fit with what the practice does, the fee and terms, and the capacity to deliver it. Records the decision and the reasoning so it can be read back against the outcome. Trigger on "go no go", "should we chase this", "pursuit review", "is this RFP worth answering", "go-no-go-review", or an opportunity raised for a decision. Carries no scoring weights and no thresholds; the practice sets what matters to it and what score means yes. It does not write the response — `rfp-response-builder` does — and does not decide. It records a decision somebody made, with the reasoning, so the next one is better informed.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds and maintains one file per project that records the limits a code sets, each with the clause it came from, so the checking skills stop asking for the same number on every run. Trigger on "jurisdiction profile", "set up the code profile", "record the code limits", "reuse my code values", "where do the limits come from", or a request to fill in or extend an existing profile. Works in any jurisdiction. The profile ships empty: every value is typed, pasted from the clause, or read out of a file the user names, and a row without a clause is marked as such rather than being treated as verified. Does not look a code value up, does not carry a default, and does not decide which code governs.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWorks out what kind of water is appearing before anyone opens a wall: rain driven in, groundwater, a plumbing failure, condensation, or air-carried moisture, which look identical inside and have entirely different causes, owners and repairs. Reads the evidence that separates them — when it appears, what the weather was doing, whether it is warm or cold, whether it is clean, whether it stops — then narrows the source and names what would confirm it. Trigger on "there is a leak", "water is coming in", "a stain appeared on the ceiling", "is this condensation or a leak", "where is this water coming from", "leak-triage", or water appearing anywhere with no agreed cause. Carries no dew points, no rainfall figures and no test standards; every value comes from the building's own data or the tester. It diagnoses rather than repairs, does not apportion liability, and does not replace the enclosure consultant, the plumber, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexKeeps a lessons-learned log in docs/practice/lessons.md: what happened, what it cost or saved, why it happened as stated, and what to do differently, each entry tagged by phase and topic so it can be found when the situation recurs. Trigger on "lessons learned", "post-mortem", "what went wrong", "remember this for next time", "add a lesson", "lessons-learned", the close of a project, or the start of one, when the right move is reading the log rather than writing it. Lessons are recorded as you state them: the skill never invents a lesson, softens one, or assigns blame beyond what you said. At project start or before a phase it reads back the entries whose tags match, which is the entire return on writing them. A lesson is one incident; recurring patterns become visible because the log accumulates, not because the skill generalizes.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodex