Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 46621–46650 of 54607 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| precedent-critiqueDavidCho1999/archaiflow-skillsCritiques the user's scheme through lenses extracted from reference projects the user supplies, instead of a generic rubric. Trigger on "critique this through these precedents", "hold my scheme against these references", "critique this like these projects", "precedent-critique", or a scheme shared alongside two or more admired projects. The user supplies both sides: their own scheme (concept text, plans, sections, images) and material for each reference (project descriptions, photographs, drawings, published texts). The skill derives three to five lenses from the supplied material, confirms them with the user, then reads the scheme through each lens. It never characterizes a firm or a project from memory: a name without material stops the run. Divergence from the references is reported and questioned, never scored. It does not design, does not rank, and does not replace the designer's judgment or a design review. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| precedent-finderDavidCho1999/archaiflow-skillsThis skill should be used when the user describes a project concept, program, atmosphere, or site condition and needs architectural precedents. Trigger on 'find references', 'similar projects', 'precedents for', or natural-language descriptions paired with phrases like 'something with this feeling'. Caches a curated precedent list in `docs/precedents/` (one file per topic) and updates the project precedent index. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| program-readerDavidCho1999/archaiflow-skillsReads any brief or programme document — a client's schedule of accommodation, a spreadsheet from a user group, a consultant's brief, a previous architect's programme — and establishes what its numbers actually are before anybody designs against them: which are measured, which are standards, which are wishes, what area basis they are on, whether the total is the sum of the parts, and what the document counts that a building would not. Trigger on "read this brief", "they sent a schedule of accommodation", "what does this programme actually say", "is this area realistic", "program-reader", or a brief handed over. Carries no area standards and no benchmarks; the basis comes from the document or from `area-measurement`. `brief-review` interrogates a brief for gaps and contradictions; this reads one for what its figures rest on, and it runs first. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| project-website-builderDavidCho1999/archaiflow-skillsTurns 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| section-reviewDavidCho1999/archaiflow-skillsReads any section — a sketch section, a building section, a wall section, a consultant's, an inherited one — for the thing a section exists to settle: whether the vertical dimensions actually add up, and what has been drawn around rather than resolved. A section is the only drawing where the structure, the services, the ceiling, the floor build-up and the envelope have to agree in the same line, which is why it is the drawing most often cut where the conflicts are not. Trigger on "read this section", "does this section work", "they sent a wall section", "check this section", "section-review", or any section handed over. Carries no dimensions or depths; anything measured is read off the drawing at its stated scale. `plan-review` reads a plan and `assembly-review` reads a stack; this reads the drawing where the vertical dimensions meet. It does not replace the Architect of Record. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| security-design-reviewDavidCho1999/archaiflow-skillsReads 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| shadow-studyDavidCho1999/archaiflow-skillsComputes solar altitude and azimuth from latitude, date, and time, then the shadow a massing casts: length, direction, and, if the user supplies the distance, whether it reaches a neighboring line. Trigger on "shadow study", "how far does the shadow go", "solstice shadows", "will my building shade the neighbor", "shadow-study", or a massing height paired with a date and a place. The solar geometry is computed from published astronomy formulas, the one thing this skill works out itself; everything else comes from the user: heights, distances, grades, and any shadow criteria the jurisdiction enforces. Flat ground is assumed unless the user supplies grades. It is a design-stage tool for comparing massing options, not a submission-grade shadow study, and it does not know which hours or open spaces any city protects. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| site-analysisDavidCho1999/archaiflow-skillsReads 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| sketch-readerDavidCho1999/archaiflow-skillsReads 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| space-programDavidCho1999/archaiflow-skillsMaintains a space program in docs/program/program.md: every space the project must contain, its required quantity and target area from the brief, the area the current plan gives it, and the delta. Trigger on "space program", "program of requirements", "room list", "area program", "programming", "target area", "are we over program", "space-program", or a pasted brief with a room schedule to capture. Targets come from the brief or the client, measured areas come from your plan, and the grossing factor comes from you; the skill supplies none of them and computes only the arithmetic between them, shown. Works in the unit system the brief uses. Reports name every space still missing a target or a measured area rather than hiding them in totals. Interrogating the brief itself is brief-review's job. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| stacking-diagramDavidCho1999/archaiflow-skillsDistributes 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| test-fitDavidCho1999/archaiflow-skillsRuns feasibility arithmetic for a site: floors times plate against your FAR and height limits, gross to net through your efficiency, net to units through your unit sizes, parking through your ratio, laid out as side-by-side scenarios with every step shown. Trigger on "test fit", "what fits", "does it pencil", "how many units", "buildable area", "yield study", "massing numbers", "test-fit", or a pasted site area with zoning limits. Every limit and assumption comes from you or your zoning summary, cited: the skill never supplies a FAR, an efficiency factor, a unit size, or a parking ratio from memory or from web search, and a scenario built on an unverified limit says so on its face. Arithmetic only, no geometry: setback envelopes, floor plates that actually fit the lot, and massing are drawing work it does not do. Early feasibility, not a zoning compliance check (test-far checks one scheme) and never a substitute for the zoning analysis. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| view-analysisDavidCho1999/archaiflow-skillsWorks 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| air-barrier-traceDavidCho1999/archaiflow-skillsTraces 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| airtightness-trackerDavidCho1999/archaiflow-skillsKeeps 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| assembly-reviewDavidCho1999/archaiflow-skillsTakes 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| condensation-checkDavidCho1999/archaiflow-skillsWorks out where water condenses inside a wall, roof, or floor assembly: the temperature at every layer boundary from the layer R-values and the design conditions, the dew point of the indoor air from its temperature and relative humidity, and which boundary is the first to fall below it. Then walks the layers in order of vapor permeance to flag a vapor-tight layer sitting on the cold side of the insulation, or two of them sealing the assembly from both directions. Trigger on "condensation check", "dew point in this wall", "will this assembly condense", "vapor retarder on the wrong side", "sheathing temperature", "condensation-check", or an assembly listed layer by layer with indoor and outdoor conditions. Every R-value, permeance, design temperature, and humidity comes from the user, out of manufacturer data, a climate data set, or the project's own documents; the skill supplies the heat-flow and psychrometric relations and never a material property. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| curtain-wall-submittal-reviewDavidCho1999/archaiflow-skillsReads 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| decarbonization-strategistDavidCho1999/archaiflow-skillsBuilds a phased decarbonisation roadmap for a building over five to fifteen years, covering operational carbon (envelope, systems, electrification, on-site renewables, off-site supply) and embodied carbon (materials, reuse against new build), sequenced against the mandate dates and incentives the user names. Trigger on "decarbonization roadmap", "decarb plan", "net zero strategy", "electrification roadmap", "embodied carbon plan", "carbon reduction plan", a pasted owner brief with a carbon target, or an energy baseline with a jurisdiction. Works in any jurisdiction. Every mandate date, cap, threshold, and incentive value comes from the user; the skill supplies the sequencing method and never a regulatory figure. Produces a roadmap memo, not an energy model, not a life cycle assessment, and not a binding commitment. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-balconyDavidCho1999/archaiflow-skillsWorks 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-below-grade-assemblyDavidCho1999/archaiflow-skillsBuilds 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-envelopeDavidCho1999/archaiflow-skillsThe 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-expansion-jointDavidCho1999/archaiflow-skillsWorks 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-parapetDavidCho1999/archaiflow-skillsWorks 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-roof-assemblyDavidCho1999/archaiflow-skillsBuilds 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-roof-drainageDavidCho1999/archaiflow-skillsWorks 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-wall-assemblyDavidCho1999/archaiflow-skillsBuilds 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| design-window-perimeterDavidCho1999/archaiflow-skillsDetails 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| embodied-carbon-trackerDavidCho1999/archaiflow-skillsKeeps 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| envelope-checklistDavidCho1999/archaiflow-skillsBuilds 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. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |