Explore skills
Showing 49171–49200 of 71536 skills
Lays 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 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 CodeCodexFollows 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 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 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 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 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 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 CodeCodexKeeps one dated log of every approval a project has to obtain, from the agencies you name rather than from an assumed list: what each permit is, which agency issues it, what it depends on, who owns it, what has been submitted and when, every comment received and its response, and every expiry. Reads back what is on the critical path and what is waiting on somebody. Trigger on "permit tracker", "track the approvals", "what permits do we need", "permit log", "who owns this approval", "when does the permit expire", "permit-tracker", or a list of agencies named with a request to keep track of them. Carries no agency lists, no review durations, no fee schedules and no permit types; every one comes from the jurisdiction, because they differ between adjacent municipalities and change without notice. It does not file anything, does not predict a duration, and does not replace the expediter, the code consultant, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexTurns a plan check or plan review comment set into a response matrix that answers every comment individually and on the record: splits comments that contain more than one question, sorts each into agreed, clarification, or disagreement, points every response at the specific sheet and detail that changed, and keeps the disagreements civil and evidenced because those are the ones that get read twice. Trigger on "plan check comments", "respond to the plan reviewer", "correction letter", "plan review response", "resubmittal response matrix", "plan-check-response-builder", or a set of reviewer comments pasted with a request to answer them. Carries no code positions of its own and never argues a clause from memory; every response either cites the drawing that changed or quotes the code text you supply. For a letter to the department rather than a comment matrix use `/draft-letter`; for tracking the submission itself use `permit-tracker`.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexStudies everything that has to reach a site and finds where two of them want the same frontage: lists every arrival — people, cars, deliveries, refuse, fire apparatus, utilities, moving vans, coaches — traces each from the public way to where it has to end up, and reports the conflicts, the curb cuts that will not be granted, and the frontage the project has already spent. Trigger on "site access study", "how does the truck get in", "where does the fire access go", "can we get a curb cut here", "loading and refuse access", "site-access-study", or a site plan with a question about how anything reaches it. Carries no dimensions, no turning radii, no fire apparatus requirements and no curb cut standards; all come from the jurisdiction, the fire department and the utility. It does no traffic engineering and no swept path analysis, and does not replace the civil engineer or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads any referenced standard — a test method, a product standard, a design standard, an industry guideline — and answers the four questions that decide whether it means anything on this project: what it actually covers, whether it binds here or is only advisory, which edition is the one that binds, and what it deliberately does not address. A standard cited in a specification is often doing none of the work anybody assumes. Trigger on "what does this standard say", "is ASTM E-something relevant here", "they referenced a standard", "does this standard apply to us", "standard-reader", or a standard cited in a spec, a submittal, or a manufacturer's claim. Carries no standard text: everything comes from the document you supply or the publisher, never from recall, since standards are revised and paraphrase drifts. It does not certify compliance and does not replace the code consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a letter from an authority — a correction letter, a completeness notice, a staff report, a conditional approval, a denial — and separates the four things inside it that behave differently: what must change, what must be shown, what must be answered, and what is a comment with nothing to do. Then finds the parts that carry a clock, since a response period or an appeal window is usually one line in the middle of a page. Trigger on "they sent this back", "read this correction letter", "what does the city actually want", "plan check comments came in", "submission-reader", or any letter from an authority handed over to work out. Carries no procedures and no periods; every deadline comes from the letter or from the jurisdiction. `plan-check-response-builder` writes the response; this works out what the letter asked. It does not replace the code consultant, the expeditor, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a land survey the way a design team has to: establishes what kind of survey it is and therefore what it is certified to show, checks it against what the project actually needs, and reports the gaps before a scheme gets built on top of them. Separates what was measured from what was compiled from records, works the boundary, the encumbrances, the topography, the utilities and the datum in that order, and flags every place the drawing shows a line that no instrument supports. Trigger on "review the survey", "is this survey adequate", "what's missing from this survey", "ALTA survey review", "survey-review", or a survey handed over at the start of a project. Carries no survey standards and no certification requirements; the standard the survey was made to comes from its own certificate. It is not a survey, does not verify a boundary, and does not replace the surveyor or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds a variance or discretionary relief application around the findings the deciding body is legally required to make, rather than around why the project wants it: extracts each required finding from the jurisdiction's own criteria, works the evidence for each one separately, tests whether the hardship claimed is of the kind the criteria recognise, and assembles the record so the decision can survive an appeal. Trigger on "variance request", "zoning relief application", "hardship findings", "special exception", "what do we have to prove for a variance", "variance-request-builder", or a zoning requirement named as unmeetable with a request to seek relief. Carries no criteria, no precedent and no legal positions; the findings come from the jurisdiction's own text. It does not give legal advice and does not replace the land use attorney, the planner, 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 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 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 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 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 a marked-up drawing — a redline, a scanned sketch over a print, a PDF with comments, a photograph of a drawing somebody wrote on — and turns it into a numbered list of what each mark asks for, who it is for, and whether it can be acted on as drawn. Separates the marks that instruct from the marks that ask, and flags every mark whose meaning cannot be determined, because a guessed markup is worse than an unread one. Trigger on "read this redline", "they marked up the drawing", "what does this markup say", "turn these comments into a list", "markup-reader", or a marked drawing handed over. Carries no conventions: what a colour or a symbol means is the office's or the marker's, and it is asked rather than assumed. `drawing-diff` compares two issued revisions; this reads what somebody wrote on one. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexAudits a building model for the practices that decide whether it stays usable: what the model is actually for and whether it is being built to that, whether geometry is modeled or drafted over, whether the data the project committed to deliver is present and consistent, what is warning or duplicated, and whether the file can be shared with consultants without an explanation. Reports by frequency and separates what will get worse from what is merely untidy. Trigger on "model health check", "audit this Revit model", "why is the model so slow", "is the model ready to share", "BIM standards audit", "model-health-audit", or a model handed over before an exchange. Carries no software-specific counts, no thresholds and no office BIM standard; the standard and the delivery requirements come from your BEP or your office. It reviews practice rather than drawings — `drawing-standards-audit` reads the sheets. It does not replace the BIM manager or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads any photograph an architect ends up with — a site visit, an existing building, a defect somebody wants explained, a phone picture from a client, a product on a shelf — and separates what is visible from what is inferred, because a photograph is the most persuasive and least complete document on a project. Establishes when and where it was taken and which way the camera faced before reading anything, since a photograph with no location is evidence of nothing. Trigger on "read this photo", "what am I looking at here", "the client sent a picture", "is this a problem", "photo-reader", or an image handed over with a question. Carries no dimensions and measures nothing from an image. It diagnoses nothing: a photograph of a stain is not a diagnosis, and `leak-triage` takes it from there. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexMaintains a project punch list in docs/construction/punch-list.md. Trigger on "punch list", "punch item", "snag list", "deficiency list", "defect list", "punch walk", "punch-list", or a pasted site visit report whose observations should become tracked items. Each item carries a location, a description, the responsible trade, the date raised, its source, and a status that separates completed from verified, because a contractor marking work done is not the same as the architect seeing it done. The skill never invents an item, a responsible party, or a completion; what it was not told stays open. Feeds on create-site-visit-report output. It does not decide substantial completion and does not certify anything; those are contract acts.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexKeeps one dated RFI log and reads what the log says that no single RFI does: every RFI with who owns it, when it arrived, when the contract required an answer, when the answer went, and how it was classified, plus the running counts that reveal a pattern — a sheet generating a stream of questions, a contractor sending already-answered ones, a consultant consistently late, a set of clarifications quietly accumulating into a change. Trigger on "RFI log", "RFI tracker", "how many RFIs are open", "are we late on RFI responses", "which drawings are generating RFIs", "rfi-tracker", or an RFI register handed over to keep. Carries no response periods and no classifications of its own; the contract sets the turnaround and each RFI's class comes from whoever answered it. It does not answer RFIs — `/draft-rfi-response` does — and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds a drawing schedule of any type — door, window, finish, room, wall type, equipment — by settling the column set before any row is filled, since the columns are what the schedule is and adding one later means revisiting every row. Takes the items from your drawings or model, fills only what you supply, marks every gap rather than defaulting it, and checks the finished schedule against the plans for items scheduled but not drawn and drawn but not scheduled. Trigger on "build a door schedule", "window schedule", "finish schedule", "room data sheet", "wall type schedule", "make a schedule from these drawings", "schedule-builder", or a request to assemble any drawing schedule. Carries no default column sets, no hardware sets, no fire ratings and no product data; the columns come from your office standard and every value comes from you. For extracting a schedule that already exists in a PDF use `schedule-extractor`. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a contractor's construction schedule from the design team's side rather than as a planner: finds every activity that depends on the architect, the consultants or the owner and checks whether the durations allowed match the contract, traces the critical path to see what actually controls the end date, looks for the logic that makes a delay claim inevitable, and separates what is a genuine concern from what is only unfamiliar. Trigger on "review the contractor's schedule", "CPM schedule review", "is this baseline reasonable", "submittal durations in the schedule", "schedule update review", "schedule-review", or a programme submitted for comment. Carries no durations, no productivity rates and no float conventions; the contract sets the review periods and the schedule specification sets the rules. It is not planning software, does not re-plan the work, does not opine on means and methods, and does not replace the scheduler or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodex