Explore skills
Showing 49351–49380 of 71536 skills
Turns a project deck PDF, renders, site photos or drawing images into one web page that reads on a phone and can be sent as a link. Uses only the words and numbers in the files or typed in the chat, lists what it found and asks how each part should be shown (full width or grid, side by side or slider, one scroll or one section per screen) before building, keeps PDF drawings sharp when zoomed, and writes the page as one index.html that a drag-and-drop host can put online. Trigger on "make this a website", "project website", "send the deck as a link", "shareable project page", "a page the client can open on their phone", "project-website-builder", or files attached with a request for something a client can open. It does not write project copy, and it does not put anything online by itself.
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 an RFP or RFQ response around the evaluation criteria rather than around the practice's usual material: pulls every requirement and every question out of the document into a compliance matrix, follows the issuer's structure and numbering exactly, and checks before submission that every requirement has an answer and every page limit and format rule is met. Trigger on "respond to this RFP", "RFQ response", "build the proposal response", "do we answer everything in this RFP", "rfp-response-builder", or a solicitation handed over to answer. Carries no boilerplate and no standard firm material; everything comes from the practice's own content. For a federal qualifications package use `sf330-builder`; to decide whether to respond at all use `go-no-go-review` first. It does not decide the fee and does not replace the principal.
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 any engineer's or consultant's schedule — mechanical equipment, plumbing fixtures, electrical panels, lighting, fire protection devices, structural members — and translates it into the architectural consequences: what has to fit somewhere, what needs a room, what needs access, what needs a route, what lands on a wall or a ceiling, and what weighs something the structure has to carry. Trigger on "read this equipment schedule", "what does this mechanical schedule mean for us", "they sent a schedule", "schedule-reader", or any consultant's schedule handed over. Carries no dimensions, capacities or clearances; every figure comes from the schedule or the product data. Not to be confused with `schedule-review`, which reads a contractor's construction programme — a different document entirely. `explain-panel-schedule` goes deeper on one electrical panel. It does not check the engineering and does not replace the engineers or 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 CodeCodexReads a plan for security as a property of the layout rather than as equipment added later: who is meant to be where and how the building tells them, where somebody can be unobserved, where the boundary between public and controlled actually falls, and what happens to all of it after hours when the staff who make it work have gone home. Works the design questions first, because a camera is what gets bought when the plan did not answer them. Trigger on "security review", "CPTED", "is this plan secure", "where do we put the access control", "how do we secure this after hours", "security-design-review", or a plan for a building with a controlled boundary. Carries no standards, no ratings and no requirements; the client's security policy, the operator's rules and any regulation come from you. It does not design systems, does not do threat assessment, and does not replace the security consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a complete drawing set rather than a drawing: works out what phase it actually is regardless of what the title block claims, what is in it and what is missing for that phase, which disciplines are present and at what revision, how the set is organised, and what somebody receiving it would have to ask about first. Built for the set that arrives from somewhere else — a previous architect, a client, a design-build partner, a project you are taking over. Trigger on "read this set", "what have we been given", "we are taking over this project", "is this set complete", "set-reader", or a whole set handed over. Carries no standards and no phase definitions; completeness is judged against what the set itself claims to be. `drawing-reader` reads one sheet, `plan-review` reads a plan, `drawing-standards-audit` sweeps for conventions. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexAssembles a federal qualifications submission section by section, and does the part that decides the score: selecting the example projects and writing them so that each one demonstrates a specific evaluation criterion rather than being included because it is good work. Builds the team organisation against the projects named, keeps résumés consistent with the projects they claim, and checks every section against the solicitation's own instructions before submission. Trigger on "SF330", "federal qualifications package", "which projects go in Section F", "architect-engineer qualifications", "sf330-builder", or a federal solicitation handed over to answer. Carries no form instructions and no evaluation criteria; both come from the current form and the specific solicitation, which override any general guidance. It does not replace the principal, who signs.
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 a site for the things that will decide the building rather than for a set of diagrams: what is fixed and cannot move, what the approach and the ground do to where a building can sit, where the sun and the weather come from, what the neighbours and the context require, and what has to be found out before anything is committed. Separates observation from inference throughout, and ends with the list of what is still unknown and who answers it. Trigger on "site analysis", "read this site", "what does the site tell us", "first visit to the site", "site-analysis", or a new site with nothing decided yet. Carries no climate data, no zoning limits and no soil values; `climate-zone-mapper`, `seismic-lookup`, `wind-snow-lookup` and `zoning-summary` collect those and this reads what they found for what it means. It is not a survey and does not replace the surveyor, the civil engineer, or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads the drawings that are not drawings: a hand sketch, a napkin diagram, a photograph of a whiteboard, a rendered view, a screenshot of a model. Separates what is decided from what is drawn loosely and what is placeholder, since the three look alike in a sketch and the difference is the whole content. Then names what the sketch has already committed to without anybody deciding it. Trigger on "read this sketch", "what does this diagram say", "the client sent a drawing they did", "read this rendering", "what does this model view show", "sketch-reader", or any informal drawing handed over. Carries no dimensions and reads no scale off an unscaled drawing. `drawing-reader` reads a measured PDF; this reads the ones drawn by hand or produced to look convincing. It does not judge the design and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds a specification's section list from the drawings rather than from the last project's table of contents: walks the set for every material, system and scope shown, maps each to a section, then runs the check in both directions — work drawn with no section, and sections carried forward with no work. Marks each section's status so the book's real completeness is visible rather than implied by a full-looking contents page. Trigger on "what spec sections do we need", "build the table of contents", "spec outline", "do we have a section for this", "spec-outline-builder", or a drawing set handed over before the book is written. Carries no section numbers, no titles and no master list; numbering comes from the format your office uses and `/lookup-csi` finds one number. For auditing a book that exists use `spec-review`; for one paragraph use `/draft-spec-snippet`.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexDistributes a programme vertically against the constraints that actually decide it: the floor plate you have, the core capacity, the loads and heights each use demands, and the ground-level frontage everything competes for. Places the uses that cannot move first, then works down the list, and reports every floor where the programme assigned exceeds what the plate can hold. Trigger on "stacking diagram", "stack the programme", "which floor does this go on", "vertical zoning", "how many floors do we need", "stacking-diagram", or a programme and a floor plate handed over with a request for how it distributes. Carries no areas, no floor-to-floor dimensions, no lift capacities and no loading figures; every one comes from you or from `space-program`, `design-core` and `test-fit`. It does not size the core, does not lay out a floor and does not replace 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 CodeCodexThe first hour on a new project: separates the decisions that have to be made before anything is drawn from the ones that can wait, because most projects reverse that and spend a month on the ones that could have waited. Establishes who decides what, what the project is actually being measured on, which unknowns block work and which do not, and what has to be commissioned now to arrive in time. Produces the decision list and the commissioning list, and hands each part off by name. Trigger on "we just won a project", "where do I start", "kick off", "what do we need before we start designing", "start-the-project", or a new commission with nothing set up. Carries no schedules, no fees and no checklists of deliverables; `drawing-checklist` holds what a phase produces and this holds what a phase has to decide. It does not replace the principal or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads a structural set the way an architect has to: not to check the engineering, but to find where the structure and the architecture disagree, where the frame lands in a space that has to stay clear, where a member's depth eats a ceiling, where the drawings defer something to a delegated design nobody has scoped, and where the structural set assumes an architectural layout that has since changed. Reports every conflict with both values and rules on neither. Trigger on "review the structural drawings", "does the structure work with the plan", "beam depth coordination", "is this deferred to a delegated design", "structural-drawing-review", or a structural set issued for coordination. Carries no loads, no spans and no code requirements; it does not check or second-guess the engineering. The counterpart for MEP is `mep-review`. It does not replace the structural engineer or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexReads subconsultant agreements against the prime agreement to find the gap the architect is standing in: obligations promised to the owner that were never passed down, insurance required upstream and not required downstream, payment terms that oblige payment before you are paid, and scope that appears in neither agreement. Works clause by clause across both documents and reports every mismatch with what each side says. Trigger on "review the subconsultant agreement", "does our consultant agreement match the prime", "flow down check", "who carries this obligation", "subconsultant-agreement-review", or a consultant agreement handed over before execution. Carries no standard-form text and no legal positions; both agreements come from you. It is not legal advice and does not replace the attorney or the Architect of Record. Read `contract-review` on the prime first.
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 project specification section by section, pulls out every submittal each one calls for, classifies it, and assembles a submittal log ready to issue. Trigger on "build submittal log", "submittal log", "extract submittals from spec", "shop drawing log", "submittal register", "submittal-log-builder", or a pasted specification section list. Works with any specification format and any contract. The user supplies the spec text by pasting it, naming files to read, or pointing at an indexed PDF, and supplies the review durations from their own contract. The skill never invents a submittal, never carries a list of typical submittals, and never assumes a review duration: every row traces to a line in the user's spec, and anything it could not find is listed as a gap rather than filled in.
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 CodeCodexReads a thread of emails or messages and answers the question that starts most disputes: what did we actually agree. Separates what was decided from what was proposed and never answered, tracks who was on the thread at each point since a decision made after somebody dropped off is a decision they never saw, finds the requests that were never replied to, and flags anything that quietly accepted scope, cost or time. Trigger on "read this thread", "what did we agree on this", "go through this email chain", "did we ever answer this", "thread-reader", or a chain of correspondence handed over. Carries no contract terms; whether something is binding comes from the agreement. `draft-email` writes one message; this reads a chain of them. It does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexKeeps one dated record of hours against fee at the level where it can still be acted on: by phase and by person rather than by project total, with the percentage of work complete recorded separately from the percentage of fee spent, since a project can be on budget and forty percent behind. Records what caused each overrun so the pattern separates from the incident, and flags the hours that should have been additional services before they are written off. Trigger on "utilization tracker", "are we over on this project", "hours against fee", "track the team's time by phase", "utilization-tracker", or a timesheet export handed over to make sense of. Carries no rates, no utilization targets and no benchmarks; the practice sets those. It does not replace the accounting system — it reads what that produces — and it does not replace `fee-tracker`, which follows the fee itself.
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 CodeCodexWorks views in both directions, because a window is two things at once: what a room looks at, and what looks back into it. Establishes what is worth seeing and whether it will still be there, what each room needs to see and what it must not, where privacy runs both ways between this building and its neighbours, and which views depend on land somebody else owns. Trigger on "view analysis", "what does this room look at", "will we still have this view", "overlooking", "privacy from the neighbours", "view-analysis", or a scheme where the windows have been placed by elevation rather than by what they see. Carries no angles, no distances and no separation requirements; overlooking rules are local text you quote and sun angles come from `shadow-study`. It does not model and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds a programme adjacency matrix from movement and constraint rather than from stated preference: takes the room list, asks for each pair what actually travels between them and how often, separates a required adjacency from a desired one and from a required separation, then reads the finished matrix for the rooms that want to be everywhere at once and the conflicts that no plan can satisfy. Trigger on "adjacency matrix", "bubble diagram", "which rooms need to be near each other", "programme relationships", "adjacency-matrix", or a room list handed over with a request for how it should be organised. Carries no adjacency conventions for any building type, because who has to be near whom is the client's operation and not a rule. Reads a room list from `space-program` where one exists and does not duplicate its area tracking. It does not lay out a plan and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexBuilds an agenda for any project meeting from the decisions it has to produce rather than from the topics somebody wants to raise. Establishes who has to be there for each decision and whether they are coming, what has to be sent in advance for a decision to be possible, and what is being discussed with nobody present who can decide it — which is how a meeting produces a follow-up meeting. Trigger on "agenda for tomorrow", "what should we cover in this meeting", "build the agenda", "prep for the client meeting", "agenda-builder", or a meeting coming up with nothing prepared. Carries no meeting formats and no standard agendas; the items come from what this project actually needs settled. `meeting-notes-cleaner` handles what comes out of the meeting; this handles what goes in. It does not replace the principal or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexTraces each of the four enclosure control layers, air first, then water, vapor, and thermal, around a building section as one continuous line, and reports every joint where that line changes material, changes plane, or is crossed by something: foundation, slab edge, wall base, floor lines, window and door openings, corners and cladding changes, parapets and eaves, roof level changes, and every penetration. Each joint records what carries the layer on either side, what makes the connection, and which drawing shows it. Trigger on "air barrier continuity", "trace the air barrier", "control layer check", "where does the air barrier break", "is the WRB continuous", "air-barrier-trace", or a wall section handed over with a continuity question. The drawings, the layer assignments, and any airtightness target come from the user; the skill supplies the joint sequence and the questions asked at each one, and never names a membrane, tape, sealant, or leakage rate.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodexKeeps one dated record of a project's airtightness target from the moment it is written into the specification to the moment it is tested: what the target is and where it came from, which surface the enclosure boundary follows, every junction that has to be sealed and who owns it, every intermediate test and what it found, and every change that moves the number or the boundary. Trigger on "airtightness tracker", "blower door target", "track the air leakage requirement", "who owns this junction", "air barrier sign-off log", "airtightness-tracker", or an air leakage target named with a request to keep track of it. Carries no target values, no test standards and no unit conversions; the target, its units and its test method all come from the specification or the certification the project is chasing. It is not a test, does not model leakage, and does not replace the enclosure consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Stars: 1Claude CodeCodex