Showing 44611–44640 of 77205 skills
Computes 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.
DavidCho1999/archaiflow-skills
Maintains 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.
DavidCho1999/archaiflow-skills
This skill should be used when the user shares a project specification — full spec book, individual CSI MasterFormat sections, or specs paired with drawings — and wants it audited for division completeness, drawing-spec coordination, prescriptive vs performance balance, basis-of-design products, reference-standard currency, AHJ amendments, section-internal completeness, and OPR alignment. Trigger on 'spec review', 'spec audit', 'CSI review', 'check this spec section', 'are the specs and drawings coordinated', 'reference standards', 'basis of design', 'or equal language', or pasted spec content with completeness intent. Generates a structured review markdown in `docs/spec-reviews/` and appends to the project spec-review index.
DavidCho1999/archaiflow-skills
This skill should be used when the user wants to map the stakeholders, decision rights, and communication structure of an AEC project. Trigger on 'stakeholder map', 'who decides what', 'project stakeholder analysis', 'RACI matrix for this project', 'map the stakeholders', 'governance plan', or pasted project context where governance, sign-off authority, or communication cadence is the question. Generates a structured stakeholder map markdown in `docs/stakeholders/` and appends to the project stakeholder index.
DavidCho1999/archaiflow-skills
This skill should be used during construction administration when the user shares a contractor submittal — shop drawings, product data, samples, or mockup documentation — and wants it reviewed for conformance with the contract documents. Trigger on 'review this submittal', 'shop drawing review', 'check this product data', 'submittal log', 'is this approved', 'spec compliance check', 'AIA G712', or pasted submittal content paired with CA-phase context. Generates a structured submittal-review markdown in `docs/submittals/` and appends to the project submittal log.
DavidCho1999/archaiflow-skills
Runs 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.
DavidCho1999/archaiflow-skills
Sorts a cost-cutting list against an issued design into accept, accept with an alternate, and block, with the reasoning written out per item across design intent, performance, lifecycle cost, schedule, risk transfer, and reversibility. Trigger on "VE review", "value engineering", "review this VE list", "where can we cut", "cost reduction options", "VE round 2", or a pasted contractor proposal with substitutions and savings figures. Works with any contract and any specification format. Performance requirements come from the user's own specification and contract; the skill supplies the sorting method and never a code threshold or a performance value from memory. Produces a recommendation memo, not a directive.
DavidCho1999/archaiflow-skills
Assembles the site environmental criteria block a project needs before any structural or envelope design starts: wind, snow, seismic, ice, rain, and flood parameters, each recorded with the source it came from. Trigger on "wind speed for this site", "ground snow load", "site hazard parameters", "design criteria block", "seismic parameters", "rainfall intensity", "wind-snow-lookup", or a pasted site location with a request for design values. Works in any jurisdiction. The skill knows which parameters a design needs and what each one feeds; the values come from the user's own code maps, official hazard tool, or authority, supplied by typing, pasting, or naming a file. It never supplies a hazard value from memory or from web search, and reports every parameter it could not source as a gap. Returns mapped parameters only, never design pressures or loads.
DavidCho1999/archaiflow-skills
This skill should be used when the user provides a site address, parcel info, or zoning lookup text and needs a structured zoning summary for early design. Trigger on 'zoning summary', 'zoning lookup', 'site zoning for [address]', or pasted zoning portal output. Targets North American projects (US + Canada). Generates a worksheet markdown in `docs/zoning/` and updates the project zoning index.
DavidCho1999/archaiflow-skills
Builds an accessibility compliance checklist for a project in two passes: scoping, meaning how many of each element must be accessible, and technical, meaning what each accessible element must measure. Trigger on "accessibility checklist", "ADA check", "accessibility compliance", "accessible parking count", "accessible toilet count", "barrier free check", "ada-tracker", or a pasted program with counts of parking, units, or toilet rooms. Works with any accessibility standard. The user names the standard and supplies both the scoping rule and each technical dimension, by typing them, pasting the clause, or naming a file to read. The skill never supplies an accessibility value from memory or from web search, and every row it could not source is reported as unverified rather than filled in. Writes a CSV checklist and appends to a project index.
DavidCho1999/archaiflow-skills
Converts structured Markdown into Word, Excel, or PDF for issue to a client, contractor, or authority: meeting minutes, RFIs, transmittals, change orders, punchlists, decision logs, payment applications. Trigger on "render this as Word", "export to Excel", "save as PDF", "make this a transmittal", or when a slash command in this catalog reaches its output step with a non-Markdown format declared. One direction only, Markdown to file. Carries the conversion recipes and the rules that stop a converter from quietly rewriting project content: units are never converted, dates are never re-localised, clause symbols and authority names survive intact, and a table stays a real table rather than becoming an image or a block of text.
DavidCho1999/archaiflow-skills
Settles the question every project answers three times and differently: which area standard is being used, where its boundary is drawn, and what counts toward it. A building has a zoning floor area, a code floor area, a gross and a net for programming, and a leasable area, and each is measured by a different rule from a different document. Records one basis per purpose with its source, reconciles the figures that result, and reports the difference rather than resolving it into one number. Trigger on "which area standard", "gross versus net", "what counts as floor area here", "our areas do not match the lease", "BOMA measurement", "area-measurement", or two area figures that disagree. Carries no standards, no definitions and no factors; each comes from the document you quote. It measures nothing itself and does not replace the Architect of Record.
DavidCho1999/archaiflow-skills
This skill should be used during the bid phase when the user shares contractor bids, sub-bids, or proposal packages and wants them reviewed for completeness, scope alignment, qualifications, exclusions, alternates, and contract terms before owner award. Trigger on 'review these bids', 'bid review', 'check this proposal', 'compare bids', 'are these bids complete', 'bid leveling', 'bid analysis', 'qualifications and exclusions', or pasted bid content with award-decision intent. Generates a structured bid-review markdown in `docs/bids/` and appends to the project bid index.
DavidCho1999/archaiflow-skills
This skill should be used when the user shares a project brief, RFP, or Owner's Project Requirements (OPR) and wants it interrogated for unstated assumptions, gaps, contradictions, and missing constraints before design work proceeds. Trigger on 'review this brief', 'check the RFP', 'unpack this brief', 'analyze the OPR', 'is this brief complete', or pasted brief text accompanied by a request to evaluate completeness. Generates a structured brief review markdown in `docs/briefs/` and appends to the project brief index.
DavidCho1999/archaiflow-skills
Reviews a proposed change order against a fixed checklist and keeps a running change log in docs/construction/change-log.md. Trigger on "change order", "CO review", "change proposal", "PCO", "COP", "cost of this change", "change log", "change-order-review", or a pasted change proposal. The checklist asks whether the scope is described, the cost is broken down, the time impact is stated, the contractual basis is named, and the markup matches what the contract allows as you quote it. The skill supplies no judgment of fair price and no contract terms from memory; clause text comes from you or explain-aia, and price sanity is lookup-cost's separate job. The log carries every change with the running total against the original contract sum, arithmetic shown. Approval is the owner's and architect's act, not this skill's.
DavidCho1999/archaiflow-skills
This skill should be used when the user has architecture/engineering technical text needing client-friendly rephrasing, OR a vague client wish needing translation into actionable technical options. Trigger on 'translate this for the client', 'put this in plain language', 'client-facing version', or pasted technical specs alongside client communication context. Generates a paired client-facing or technical document in `docs/client-comms/`.
DavidCho1999/archaiflow-skills
Records the climate or thermal zone a project sits in, then builds the envelope requirement scorecard component by component: roof, walls above and below grade, floors, slab edge, fenestration thermal, fenestration solar gain, and air leakage. Trigger on "what climate zone is this", "climate zone for this site", "envelope requirements for zone X", "energy code envelope scorecard", "climate-zone-mapper", or a pasted project address with an envelope question. Works with any energy code. The zone determination and every requirement value come from the user, typed, pasted, or read from a file they name. The skill never supplies a zone, an R-value, a U-factor, or a solar gain figure from memory or from web search, and any component without a supplied requirement is reported as unverified. Writes a CSV scorecard and a summary.
DavidCho1999/archaiflow-skills
Assembles the code analysis block that goes on a permit set cover sheet, in six parts: occupancy classification, construction type, height and area with the allowable-area arithmetic shown, fire-resistance summary, means-of-egress summary, and accessibility statement. Trigger on "code analysis", "cover sheet code block", "G001 code block", "code-analysis-builder", "allowable area calc", "construction type check", or a pasted program with use, footprint, and sprinkler condition. Works in any jurisdiction. The user names the governing code and edition and supplies every value by typing it, pasting the clause or table row, or naming a file to read. The skill never supplies a code value from memory or from web search, and any line without a supplied value is printed as unverified rather than filled in. Does not replace the Architect of Record or the AHJ.
DavidCho1999/archaiflow-skills
Reads a code analysis produced by somebody else — a previous architect, a code consultant, a design-build partner, an earlier phase of your own project — and separates its three layers: the determinations it made, the arithmetic it showed, and the conclusions it stated without either. A code analysis is a chain of decisions and the first link, the occupancy classification, silently sets everything after it. Trigger on "read this code analysis", "we inherited a code summary", "is this code sheet still right", "the consultant sent their analysis", "code-analysis-reader", or a code analysis handed over. Carries no code text and no limits; every figure in it is checked for whether it was cited, not for whether it is correct. `code-analysis-builder` assembles your own; this reads one you were given. It does not verify compliance and does not replace the code consultant or the Architect of Record.
DavidCho1999/archaiflow-skills
Audits a floor plan, schematic set, or program layout across eight egress and accessibility axes: use and occupant load, egress capacity and exit count, common path of travel, travel distance, exit access and door width, exit separation, accessibility, and fire-resistance assemblies. Trigger on "code review", "egress check", "life safety review", "plan check", "check egress", "accessibility check", "exit count", "travel distance", or a pasted plan with a code question. 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. Writes a dated review file and appends to a project index, with every unverified axis counted on the face of the review. Does not replace the Architect of Record or the AHJ.
DavidCho1999/archaiflow-skills
Works 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.
DavidCho1999/archaiflow-skills
This skill should be used when the user shares construction documents (DD set, 50%/100% CD, GMP set) and wants them reviewed through a constructor's lens — sequencing, tolerance stack-ups, MEP coordination, install access, lay-down logistics, temporary works, long-lead procurement, and phased operations. Trigger on 'constructability review', 'CM review', 'sequencing check', 'install access', 'crane reach', 'lay-down', 'long-lead', 'MEP coordination clearance', 'site logistics', or pasted CD context with build-feasibility intent. Generates a structured review markdown in `docs/constructability/` and appends to the project constructability index.
DavidCho1999/archaiflow-skills
Checks each room's depth against how far sidelight can reach it, from the window head heights, room depths, and glazing areas the user supplies: daylit depth by a stated convention, glazing-to-floor arithmetic held against a code minimum the user quotes, and the no-sky line when a facing building is in the way. Trigger on "daylight study", "how deep does daylight reach", "is this room too deep for daylight", "no-sky line", "daylight-study", or room depths paired with window head heights. The depth convention and the obstruction geometry are the only things this skill supplies itself; every dimension, glazing area, and code minimum comes from the user. It is a plan-stage tool for comparing layouts, not a daylighting simulation: no daylight factor, no illuminance, no glare, no LEED credit documentation, all of which come from a model. Exterior shadows on neighbors belong to shadow-study; energy-code glazing checks belong to test-glazing.
DavidCho1999/archaiflow-skills
Builds 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.
DavidCho1999/archaiflow-skills
Sizes a single simply-supported beam in steel, wood, or reinforced concrete for a known span, tributary load, and deflection limit, showing every step of the arithmetic. Trigger on "size beam", "preliminary beam size", "pick a section", "glulam beam size", "concrete beam size", "beam deflection check", "design-beam", or a pasted span with loads. Works with any design standard. The user names the standard, the design method, and supplies the load combinations, material properties, section properties, resistance factors, and deflection limit, by typing them, pasting the table, or naming a file. The skill never supplies an engineering value from memory or from web search. Preliminary sizing only, for a fully braced simple span, and never a substitute for the Engineer of Record.
DavidCho1999/archaiflow-skills
Works the ceiling as the place every discipline's leftovers land: adds up what has to fit in the plenum in the order it gets installed, finds the one crossing that sets the height for the whole floor, and works access, transitions and the elements that arrive late and wreck a reflected ceiling plan. Reports the height available against the height wanted. Trigger on "ceiling height", "what fits in the plenum", "reflected ceiling plan", "will the duct clear the beam", "ceiling access", "design-ceiling", or a floor-to-floor with a question about what it leaves. Carries no depths, no clearances and no code requirements; structural depths come from the engineer, service sizes from the MEP set, and required heights from the code you quote. It does not size services or structure and does not replace the engineers or the Architect of Record.
DavidCho1999/archaiflow-skills
Checks a single axially loaded, braced column against the capacity your standard's values produce, with every step of the arithmetic shown: slenderness from your effective length factor, capacity from the expression or table row you supply, demand over capacity at the end. Trigger on "column check", "column size", "post size", "axial capacity", "slenderness check", "KL/r", "design-column", or a pasted column load with a trial section. Works with any design standard. The user names the standard and method and supplies the load combinations, the effective length factor, the section and material properties, and the capacity expression or its tabulated value, by typing, pasting, or naming a file; the skill never supplies an engineering value, a buckling curve, or a section from memory or web search. Concentric axial load on a braced member only; combined bending needs your interaction equation or it stops. Preliminary sizing, never a substitute for the Engineer of Record.
DavidCho1999/archaiflow-skills
Aggregates the pieces of a building core (elevator shafts, stairs, toilets, mechanical and electrical shafts and rooms) from dimensions the user supplies, applies the user's own wall-and-circulation factor, and reports total core area and core-to-floor-plate ratio against the user's benchmark, showing every step. Trigger on "core sizing", "how big is my core", "core-to-floor ratio", "core efficiency", "design-core", or a floor plate paired with a list of core components. Every dimension comes from the user: shaft sizes from manufacturer cut sheets, stair footprints from the user's stair layout, room sizes from the user's plans, the grossing factor and the target ratio from the user's own benchmarks. The skill never supplies a typical shaft size, fixture count, or target ratio. It does not decide elevator count (the elevator consultant's traffic analysis does), does not check stair or fixture code compliance, and is not a substitute for the Architect of Record.
DavidCho1999/archaiflow-skills
This skill should be used when the user shares an architectural project (concept text, plans, sections, renderings, references) and asks for critique, feedback, or a second opinion. Trigger on 'design critique', 'review this design', 'critique this', 'second opinion', or when context implies the user wants challenge over validation. Generates a structured critique markdown in `docs/reviews/` and appends to the project review index.
DavidCho1999/archaiflow-skills
Sizes a duct segment from an airflow and the limits you set: area from the velocity limit you state, rectangular dimensions within your aspect ratio, the equivalent-diameter arithmetic between round and rectangular, and a pressure-drop tally over a run when you supply the loss values, every step shown. Trigger on "duct size", "duct sizing", "duct velocity", "equivalent diameter", "static pressure", "cfm to duct size", "design-duct", or a pasted airflow with a size question. Works in either unit system, as given. The user supplies the airflow, the velocity or friction-rate limit with where it came from, aspect ratio limits, and any fitting loss values, cited; the skill never supplies a velocity limit, a friction rate, or a loss coefficient from memory or from web search. Geometry and arithmetic only: fan selection, system effect, acoustics, and leakage class are the mechanical engineer's calls. Preliminary, never a substitute for the mechanical Engineer of Record.
DavidCho1999/archaiflow-skills