Civil architect
- When to use it
- Building design from a client's room list and a footprint: a schematic floor plan placed at real sizes and drawn as a dimensioned SVG, shown only once a script has checked it for overlapping rooms, rooms outside the footprint, doors on no shared wall, rooms no one can reach and habitable rooms with no window.
- Covers
- Design a building (1)
- Where you decide
- No gated loop of its own; the skills run one at a time.
- Size
- 6 skills · 0 loops
npx skilldrop-cli install --pack civil-architect
Installs 6 skills, including core.
Other ways to install
The pack's loops too, each as an invokable skill:
npx skilldrop-cli install --loop --pack civil-architect
In Claude Code, as a plugin (after /plugin marketplace add sananthanarayan/skilldrop):
/plugin install civil-architect@skilldrop
Into Cursor, Kiro or another IDE:
npx skilldrop-cli install --pack civil-architect --ide cursor
Start here: Get a checked, dimensioned concept plan from a room list and a footprint
Paste this into your agent:
Draw a ground floor plan for a 10 m wide × 9 m deep footprint, road on the south, front door from the road. Rooms: foyer 6 m², living 26 m², dining 14 m², kitchen 12.6 m², utility 4 m² next to the kitchen, prayer room 4.5 m² not next to the kitchen or the toilet, guest toilet 3.2 m², and a stair. Living, dining, kitchen and prayer room need windows.
- Before you start
- The rooms you need with their sizes, and the footprint's width and depth
- Python 3 on the machine, which the checker and drawing script run on
- How to tell it worked
- floor-plan-layout states its zoning in a few lines, writes an SVG plan with overall dimensions, room sizes and areas, door swings, windows, a scale bar and a north arrow, and shows a room table from a checker that reported no overlaps, every door on a shared wall and every room reachable.
- If nothing happens
- If floor-plan-layout does not activate, ask for it by name ("use floor-plan-layout"). If the plan is too tight, ask for a second option with the rooms it may shrink named.
A typical session
When: You have a client's room list and a footprint, and want a first plan to discuss.
You bring:
- the rooms, with their sizes or areas
- the footprint's width and depth, or its corner coordinates
- the road or entrance side, and north
- what must sit next to what, and what must be kept apart
-
- You
- Give it the rooms, the footprint and the entrance side.
- You get
- Zoning in a few lines, then a dimensioned SVG plan per floor that has passed the checker, with every room's size and area.
- You decide
- Take the plan to the client, or ask for another option.
-
- You
- Ask for a second option, naming what may change (a smaller hall, the stair moved).
- You get
- Another checked plan, with each room that changed against its target.
You end with: A checked concept plan, ready to develop in your CAD or BIM tool.
Compare Civil architect with another pack
Skills in this pack (1)
Included from core (5)
- brief-intake Turn raw mess — a Slack thread, meeting transcript, Jira ticket, half-written Notion page, email chain, or paragraph of free-form context — into a structured brief that the downstream skill (adr-generator, design-doc, runbook-generator, exec-summary, slide-outliner) can consume without further intake. Use whenever the user has unstructured source material and is about to invoke another skilldrop skill, or when a draft is missing the load-bearing context the next step will need. standard
- context-graph Map the decisions behind a codebase from its ADRs, RFCs and design records — each record's status and date, what supersedes or amends what, which records cite which, the files and folders each decision governs, and with git the commits that implemented it and the commits that changed each decision's code since it was made, and who made them — then answer "why is it like this?" from the record and check the record is still true. Finds supersessions only one side records, current decisions pointing at code that is gone, code that has drifted from its decision, two current decisions governing the same path, and references to records that don't exist. Use when the user asks "why do we use X", "which decisions govern this file or service", "is this ADR still current", "has the code drifted since we decided this", "are our ADRs out of date", "what was decided before I change this", wants a map of the architecture decisions, or is onboarding onto a codebase's history. standard
- council-review Convene a council of distinct senior-engineer personas (Architect, Security, Operator/SRE, Pragmatist, User-Advocate, plus optional bench seats) to deliberate a decision, design, or code change — each takes an independent stance, the genuine disagreements are surfaced as named cruxes, and a Chair issues a reconciled verdict that records dissents and states what would change the decision. The "Claude Council." Use when a choice has real tradeoffs and one reviewer's voice isn't enough: architecture decisions, risky changes before merge, RFC/design scrutiny, "should we adopt X?", rewrite-vs-refactor, or a pre-mortem. heavy
- doc-critique Review an existing document — ADR, design doc, runbook, exec summary, tech-comparison matrix, deck outline, decision log — and produce a structured critique against the same quality bars the skilldrop generators enforce. Categorizes findings by severity (blocker / major / minor / nit), points to the exact section/line, and suggests a concrete fix for each. Use when the user wants a second-pair-of-eyes review before sharing a doc, or has been handed someone else's artifact and wants to know what to push back on. heavy
- output-hygiene Review agent-written text before it ships and strip the machine artifacts it carries — invisible Unicode, non-breaking spaces, homoglyphs, harness-added provenance trailers, trailing chat closers — then flag the prose tells a script cannot catch, each quoted with a rewrite. Use when the user wants to clean up AI-generated output, asks to remove a Claude watermark, attribution footer, or "Generated with" line, wants a draft that does not read as machine-written, or needs a pre-ship hygiene pass on a document, commit message, or pasted chat answer. light