Explore skills
Showing 49381–49410 of 71536 skills
Assembles an alternative means and methods request as an argument rather than a form: establishes the prescriptive requirement that cannot be met and why, states the intent behind that requirement in the code's own words, sets out what is proposed and how it meets that intent, and gathers the evidence, the compensating measures and the conditions the applicant is willing to accept. Trigger on "alternative means and methods", "AMMR", "code modification request", "equivalency request", "we cannot meet this section, what now", "alternative-means-builder", or a prescriptive requirement named as unachievable with a request to make the case. Carries no code text, no precedent from other jurisdictions and no performance criteria; the requirement, its stated intent and any referenced standard all come from documents you supply. It does not approve anything, does not perform fire modelling or engineering analysis, and does not replace the fire protection engineer, the code consultant, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexTakes any requirement — a code section, a standard, an ordinance, a lease clause, an owner's design standard, a certification credit — and answers the question that comes before every other one: does this apply to this project at all. Works the six tests that decide it: is the document adopted or binding here, does the project fall inside its stated scope, has the trigger been met, does an exemption remove it, is this the edition that binds, and is something else more restrictive. Trigger on "does this apply to us", "is this section relevant", "do we have to comply with this", "they say this applies", "applicability-check", or a requirement quoted at you. Carries no text and no thresholds: every answer comes from the document you supply or the jurisdiction's own source. It does not interpret the requirement — `code-reader` takes it apart — and does not replace the code consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexTakes any envelope assembly you are handed — a wall, a roof, a floor, a below-grade construction, from a consultant, a contractor, a manufacturer or an earlier phase of your own project — and reads it for what it is trying to do and where it does not. Locates the four control layers, checks each is continuous through the stack and has somewhere to go at the edges, names every layer with no job, and reports which direction it can dry. Trigger on "review this assembly", "is this wall build-up any good", "they sent us a section", "read this stack", "assembly-review", or any layered construction handed over for an opinion. Carries no R-values, permeance figures or code minimums; every value comes with the assembly or is marked missing. The `design-` assembly skills build one from demands; this reads one that already exists. It runs no arithmetic — `condensation-check` does — and does not replace the enclosure consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWorks the conversation every project has and most handle badly: the design costs more than the budget. Establishes first what each number actually is, since a client's budget often excludes things an estimate includes and half the gap disappears there. Then sorts the ways of closing it into the four that behave differently — less area, less quality, less scope, more money — and prices each move in what it costs the design rather than only in what it saves. Trigger on "we are over budget", "the estimate came back high", "what do we cut", "value engineering at design stage", "the client's budget will not cover this", "budget-reconciliation", or an estimate set against a budget with a gap between them. Carries no costs, no rates and no benchmarks; every figure comes from the estimator, the contractor, or a source you name. `value-engineering-advisor` sorts a cost-cutting list during construction; this is the design-stage conversation. It does not estimate and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads any calculation an architect is handed — structural, thermal, egress, drainage, load, acoustic — and checks the part an architect can and should check: the inputs, the assumptions, the standard it was worked to, and the version of the design it was worked from. The arithmetic is sealed by somebody and is not the architect's to verify; the inputs frequently describe a building that has changed since. Trigger on "read this calculation", "they sent calcs", "what did the engineer assume here", "is this calc still valid", "calculation-reader", or any calculation handed over. Carries no formulas, values or code limits. It verifies no arithmetic, has no engineering opinion, and does not replace the engineer of record or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexKeeps one dated log of every change from the moment it is first raised, not from the moment it becomes a change order: records where each one came from, what instrument carried it, its cost and time position at every stage, and who it is sitting with, so that the work directed but not yet priced and the changes stalled between proposal and execution are both visible. Reports the running total against the contingency and the count of changes proceeding on direction alone. Trigger on "change order log", "track changes", "how much have we spent of the contingency", "what changes are outstanding", "work proceeding without a change order", "change-order-tracker", or a change register handed over to keep. Carries no cost data, no markup rates and no contract periods; all come from the contract and the proposals. It does not price, review, or negotiate a change — `change-order-review` does that for one — and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexStudies circulation as a set of named journeys rather than as corridor area: establishes who moves through the building and why, traces each journey door to door, finds the places two journeys cross that should not, and reports where a route depends on something being unlocked, staffed or explained. Separates the circulation a plan needs from the circulation it happens to have. Trigger on "circulation study", "trace the routes", "do these flows cross", "clean and dirty separation", "public and staff routes", "wayfinding through the plan", "circulation-study", or a plan handed over with a question about how people move through it. Carries no corridor widths, no efficiency ratios and no separation requirements; egress widths and distances belong to `design-egress` and accessibility to the accessibility standard you quote. It does not lay out a plan and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexTakes a citation somebody handed you — in a review comment, a consultant's report, a contractor's letter, a manufacturer's claim, or your own earlier drawing — and checks the three things that make it usable: does the document exist and in which edition, does the section number resolve inside it, and does the text actually say what it is being used to say. Reports which of the three could be verified and which could not, rather than a yes or a no. Trigger on "is this citation right", "check this code reference", "they quoted a section at us", "does this clause say that", "cite-check", or a section number pasted with a claim attached. Carries no code text: verification comes from the document you supply or from the jurisdiction's own published source, never from recall and never from a search result that is not the publisher. It does not interpret the clause — `explain-code` does — and does not replace the code consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a civil set against the architectural set for the disagreements that only show up where the two meet: the finished floor against the finished grade at every door, the accessible route against the actual slopes, where utilities enter the building against where the risers are, and what the civil drawings assume about a building they were not drawn from. Reports every conflict with both values and rules on neither. Trigger on "review the civil drawings", "do the civil and architectural agree", "grading around the building", "utility entry coordination", "civil-drawing-review", or a civil set issued for coordination. Carries no slope limits, no cover requirements and no utility standards; accessibility limits come from the standard you quote and utility requirements from the utility. It is not civil engineering, does not check drainage design, and does not replace the civil engineer or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds and tracks the closeout deliverables list in docs/construction/closeout.md: O&M manuals, warranties, test and inspection reports, record documents, spare parts and attic stock, training, each with the spec section that requires it. Trigger on "closeout", "closeout checklist", "O&M manuals", "warranties", "attic stock", "record drawings", "as-builts", "turnover package", "handover", "closeout-check", or the end of construction approaching. The list is built by reading the closeout requirements out of your spec book or typed by you; the skill never invents a deliverable a spec did not require. Received items are recorded with dates; the report leads with what is outstanding, by division. Whether the contract's closeout conditions are met is the architect's certification, not this skill's.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexTakes a code section, a standard, or an ordinance you paste and pulls it apart into the separate requirements inside it: what each one applies to, what it demands, what triggers it, what exempts it, and which other section it hands off to. A single paragraph routinely contains four requirements and two exceptions, and reading it as one sentence is how half of it gets missed. Trigger on "read this code section", "what does this clause actually require", "pull the requirements out of this", "code-reader", or a pasted section that has to be worked through. Carries no code text and recalls no section: everything comes from what you paste or from the jurisdiction's own published source. `explain-code` puts one clause in plain English; this takes the clause apart into a table you can check a design against. It does not check the design — `compliance-check` does — and does not replace the code consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexTakes a drawing and the code text that governs it and works through them together, one requirement at a time: what the text demands, what the drawing shows, and whether the drawing shows enough to tell. The third answer is the common one and it is the useful one, because a drawing that does not say is not a drawing that complies. Trigger on "does this drawing meet this code", "check this against the code text", "we pasted the section, now check the plan", "compliance-check", or a drawing and a quoted requirement handed over together. Carries no code text and recalls no limit: everything comes from what you paste. `code-compliance-review` audits a plan across eight fixed axes without being given text; this checks whatever text you bring against whatever drawing you bring. It does not interpret the clause, does not certify anything, and does not replace the code consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a drawing from any consultant — structural, mechanical, electrical, plumbing, fire protection, civil, landscape, acoustic, kitchen, security — against the architectural set, from the architect's side. Checks the things that go wrong the same way whatever the discipline: the background it was drawn on, the grids and levels, what it lands in that has to stay clear, what it defers to somebody else, and where the two sets simply disagree. Trigger on "review the consultant drawings", "read this engineer's drawing", "do these agree with our plans", "they issued a set, what do we check", "consultant-drawing-review", or any consultant's drawing handed over. Carries no engineering values and checks no engineering. `mep-review`, `structural-drawing-review` and `civil-drawing-review` go deeper on those three; this is the one that works for the disciplines that have no skill of their own. It does not replace the engineers or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads an owner-drafted or heavily amended professional services agreement for the provisions that shift risk onto the architect, working in the order the money moves rather than the order the document is written: standard of care, indemnity, limitation of liability, insurance, scope creep, payment and termination, ownership, and the dispute path. Reports each finding with the clause quoted, what it changes from the industry-standard position, whether it is insurable, and whether it is usually negotiable. Trigger on "review this contract", "the client sent their own agreement", "is this indemnity clause standard", "can we sign this", "contract-review", or an agreement handed over before signing. Carries no standard-form text and no legal positions; comparisons to a standard form require you to supply it. It is not legal advice and does not replace the attorney, the broker, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexKeeps one dated log of conflicts between disciplines and follows each to the only ending that counts: both sets showing the same thing. Records which two documents disagree, what each says, who resolves it, and then the step everyone skips — whether the agreed answer reached both drawings and at which revision. Consolidates what the review skills find rather than leaving each discipline's findings in its own report. Trigger on "coordination log", "track the clashes", "did that conflict get fixed in both sets", "coordination issues", "coordination-log", or the output of a discipline review handed over to keep. Carries no positions of its own; the conflicts come from `mep-review`, `structural-drawing-review`, `civil-drawing-review`, `penetration-review` and `design-ceiling`. It does not resolve anything and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads any document with money in it — an estimate, a budget, a cost plan, a supplier quote, a contractor's proposal, a client's own number — and does the part an architect can do without being an estimator: establish what it covers, what it excludes, what it assumed, and what date it is on. Those four decide almost every argument about a price, and none of them require checking the arithmetic. Trigger on "read this estimate", "what does this quote actually include", "the budget came back", "is this number comparable", "cost-reader", or any priced document handed over. Carries no rates, no benchmarks and no cost data; `/lookup-cost` quotes a benchmark with its source and `senior-cost-estimator` gives judgement. It checks no arithmetic, prices nothing, and does not replace the estimator, the contractor, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a curtain wall or unitised facade submittal package as a system rather than as a set of sections: checks that the drainage and pressure-equalisation strategy is coherent through every joint, that the thermal break line is continuous and lands where the wall's insulation does, that movement is provided for at stack joints and anchors, that the tested system and the drawn system are the same system, and that the interfaces to every adjoining assembly have an owner. Trigger on "curtain wall shop drawing review", "unitised facade submittal", "review the glazing submittal", "stack joint detail review", "is the thermal break continuous", "curtain-wall-submittal-review", or a facade shop drawing package handed over for comment. Carries no performance criteria, no test values and no tolerances; all come from the specification and the test reports, quoted. It reviews and comments, does not stamp or approve, and does not replace the facade engineer or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexSorts a delay before it becomes a claim: establishes what is actually late against what baseline, whether the delayed activity was ever controlling the completion date, who caused it, and whether the contract makes it compensable, excusable, or neither. Separates the three questions that get merged — is it late, is it critical, and whose is it — because a delay can be real and cost nobody anything. Trigger on "we are behind", "the contractor says we delayed them", "is this a critical delay", "do we owe them time", "delay-triage", or a delay asserted with a letter likely to follow. Carries no contract terms and no float conventions; entitlement comes from the executed agreement you quote. It is not a delay analysis, which is forensic and has a methodology, and it does not replace the scheduler, the attorney, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexLays out an accessible restroom or toilet room as a set of overlapping clearances rather than as a list of items to tick: establishes which clearances may overlap and which may not from the standard you quote, places the fixtures in the order that constrains the plan most, works the door swing against the clear floor space it eats, and reports every dimension as a question rather than an answer. Trigger on "accessible restroom layout", "toilet room won't fit", "ADA bathroom", "single-user accessible washroom", "turning circle in the toilet", "design-accessible-restroom", or a toilet room plan with a request for whether it works. Carries no dimensions, no clearances and no reach ranges; every one is text you quote from the standard your jurisdiction adopts, which is not always the one you expect. For checking one clearance already dimensioned use `/test-ada`; for a project-wide record use `ada-tracker`. It does not replace the accessibility consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWorks acoustic separation between two spaces as a whole rather than as a wall or floor rating: establishes what the source is and what the receiver needs, then traces every path sound can take between them, because the assembly's tested rating describes the direct path only and the built result is set by whatever flanks around it. Names the structural decisions that have to be made early and cannot be fixed later. Trigger on "acoustic separation", "STC between these units", "impact noise from above", "flanking", "why is this wall not working acoustically", "design-acoustic-separation", or two spaces with a noise problem between them. Carries no ratings, no laboratory values and no criteria; the target comes from the code, the brief or the acoustician, and every assembly value is a tested figure you cite. It is not acoustic engineering and does not replace the acoustician or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWorks an addition or a renovation at the place it actually gets decided: the joint between new and existing. Settles the relationship the new work takes to the old, then works the six things that cross the joint — structure, envelope, services, levels, fire separation and finishes — and separately establishes what the work triggers in the existing building, since a change of use or a threshold crossed can require upgrades to parts of the building nobody was touching. Trigger on "addition", "extension", "renovation", "how does the new bit meet the old", "does this trigger an upgrade", "matching the existing", "design-addition", or new work proposed against a building that already exists. Carries no code thresholds and no structural values; existing-building provisions are jurisdictional text you quote and capacity is the engineer's. Read `existing-conditions-survey` first: an addition designed against unverified dimensions is designed twice. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWorks a balcony, terrace or projecting deck as the place where the envelope is deliberately broken: something structural passes through the insulation, the waterproofing has to turn up and drain away from a door, and a guard has to fix to whatever is left. Establishes the structural relationship first, since a cantilevered slab, a thermally broken connection and an independently supported balcony are three different buildings, then works the falls, the threshold, the drainage and the guard. Trigger on "balcony detail", "cantilever slab thermal bridge", "terrace over occupied space", "balcony door threshold", "where does the balcony drain", "design-balcony", or a projecting floor with a wall behind it. Carries no dimensions, no thermal values, no loads and no code requirements; guard and drainage requirements are code you quote and the structure is the engineer's. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexLays out a domestic bathroom or ensuite from the two things that actually constrain it — where the waste can run and which way the door swings — rather than from the fixtures. Works ventilation, the wet area and its waterproofing, storage, and the reach and clearance around each fixture, and separates what is fixed by the building from what is a choice. Trigger on "bathroom layout", "ensuite", "can we move the toilet", "powder room", "where does the shower drain go", "design-bathroom", or a bathroom to be laid out or moved. Carries no clearances, no fixture dimensions and no ventilation rates; each comes from the code you quote, the accessibility standard, or the fixture's own data. For an accessible restroom to a standard use `design-accessible-restroom`; for commercial fixture counts use `/count-plumbing-fixtures`. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds a below-grade wall or slab assembly from the water condition first: takes the groundwater regime, the soil, the structure, how the space below grade will be used and whether the waterproofing can ever be reached again, then places the water, thermal and vapor control layers in an order, gives every layer a job, and works the joints, penetrations and the at-grade transition where below-grade work actually fails. Trigger on "below grade waterproofing", "basement wall build-up", "foundation wall assembly", "slab on grade vapor barrier", "blindside waterproofing", "design-below-grade-assembly", or a foundation wall and a water table named with a request for what goes between them. Supplies the ordering logic and the questions each condition has to answer; supplies no thickness, no permeance, no hydrostatic head, no code requirement and no proprietary product. It does not size drainage, does not do geotechnical or structural work, and does not replace the waterproofing consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexChecks a floor or a tenancy against the means-of-egress items every building code regulates: egress capacity per occupant, number of exits required, single-exit allowance, common path of travel, exit separation, travel distance, corridor width, dead-end length, door clear width, and door swing threshold. Trigger on "check egress", "egress review", "exit count", "travel distance", "common path", "exit separation", "dead end corridor", "design-egress", "IBC 1006", "IBC 1017", "OBC 3.4", or a pasted plan with occupant load and exit positions. Works in any jurisdiction. The user names the governing code and edition and supplies each limit by typing it, pasting the clause, or naming a file to read. The skill never supplies a limit from memory or from web search, and any item without a supplied limit is reported as unverified rather than assumed. Does not compute occupant load, and does not replace the Architect of Record or the AHJ.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexLays out an electrical, communications or service entrance room around the working clearances that surround the equipment rather than around the equipment itself, because those clearances are code, they are volumes, and they appear on no architectural drawing by default. Works the utility's own requirements separately from the code's, since a service entrance room is designed to the utility's standard and they will refuse a room that meets the code and not their manual. Trigger on "electrical room layout", "how big does the switchgear room need to be", "working clearance in front of the panel", "service entrance room", "transformer vault", "design-electrical-room", or an electrical equipment schedule with a room to put it in. Carries no clearance dimensions, no equipment sizes and no utility requirements. It does not do electrical design and does not replace the electrical engineer or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexHolds the architectural space an elevator installation needs from the consultant's or manufacturer's data: the hoistway, the pit below the lowest landing, the overrun above the highest, the machine and controller wherever the product puts them, and the lobby and door dimensions at every level. Works the constraints that decide the building — what the pit does to the foundation, what the overrun does to the roof or the height limit, and where the machine has to be if there is no machine room. Trigger on "elevator pit depth", "lift overrun", "machine room-less", "how big is the hoistway", "elevator shaft coordination", "design-elevator", or an elevator specification handed over to fit into a building. Carries no dimensions, no capacities, no speeds and no code requirements; every one comes from the manufacturer, the elevator consultant, or the code you quote. It does not do traffic analysis and does not replace the elevator consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWorks the entrance as a continuous sequence rather than as a door: how it is found from the street, what happens on the way in, what the threshold has to hold at once, and where somebody stands when they arrive and nobody is expecting them. Names the four things that meet at a doorway and cannot all be optimised — level access, weather, energy, and security — and says which one this project lets win. Trigger on "entrance design", "the entry sequence", "where is the front door", "vestibule", "the entrance is hard to find", "design-entry", or an entrance that is a door on a plan and nothing more. Carries no dimensions, no threshold limits and no requirements; accessible thresholds and vestibule requirements are code and standards you quote. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexThe door into envelope work, and the step usually skipped: before any assembly is built up, decide how many envelope types the building actually has, which face gets which, where the junctions between them fall, and what each one has to achieve. Produces the schedule of types and junctions that the assembly and junction skills then execute against, and hands each part off by name. Trigger on "design the envelope", "how many wall types do we need", "what should this facade be", "envelope strategy", "where do the assemblies change", "design-envelope", or an envelope scope with no strategy behind it. Carries no R-values, no assemblies and no code minimums; performance requirements come from the code and the brief you quote. It builds nothing itself — `design-wall-assembly`, `design-roof-assembly` and the junction skills do — and does not replace the enclosure consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexWorks movement in the enclosure as two questions rather than one: where the joints have to be, given the movements you can name and where they accumulate, and then how each of the four control layers (water, air, vapor, thermal) crosses a gap that opens and closes for the life of the building. Trigger on "expansion joint", "movement joint", "control joint", "where do the joints go", "building separation joint", "how does the air barrier cross a joint", "design-expansion-joint", or a long facade or a structural break named with a request for how the enclosure handles movement. Supplies the reasoning about movement sources, accumulation and joint hierarchy, and the questions each crossing has to answer; supplies no joint spacing, no movement coefficient, no joint width, no code requirement and no proprietary product. It does no structural or thermal calculation and does not replace the enclosure consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodex