Interior designer
- When to use it
- Furniture plans for one room: every piece at its real size and facing the way it's used, drawn as a dimensioned SVG, and shown only once a script has checked it for overlaps, pieces in a door's swing, blocked bed sides, chair pull-backs and wardrobe doors, and a clear walking route to everything.
- Covers
- Furnish a room (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 interior-designer
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 interior-designer
In Claude Code, as a plugin (after /plugin marketplace add sananthanarayan/skilldrop):
/plugin install interior-designer@skilldrop
Into Cursor, Kiro or another IDE:
npx skilldrop-cli install --pack interior-designer --ide cursor
Start here: Get a checked, dimensioned furniture plan for one room
Paste this into your agent:
Lay out our bedroom: 3.6 m wide × 3.3 m deep, door at the right end of the south wall opening in, window centred on the north wall with a 0.9 m sill. Furniture: a king bed (1.8 × 2.0 m), two nightstands, a 1.2 m wardrobe with hinged doors, and a small desk with a chair.
- Before you start
- The room's width and depth, where its door and windows are, and the furniture you want in it
- Python 3 on the machine, which the checker and drawing script run on
- How to tell it worked
- furniture-layout states its zoning in a few lines, writes an SVG plan with the room's dimensions, every piece with its size, its clearances shaded and the walking route drawn, and says plainly what it changed or couldn't fit.
- If nothing happens
- If furniture-layout does not activate, ask for it by name ("use furniture-layout"). If a piece won't fit, ask for the best smaller option, or say which piece may go.
A typical session
When: You have a room and a list of furniture, and want to know what fits and where.
You bring:
- the room's width and depth, or its corner measurements if it isn't a rectangle
- the doors (which way they open) and the windows
- the furniture, with sizes if you know them
- anything that must stay clear, such as a radiator or a balcony door
-
- You
- Give it the room, its doors and windows, and the furniture list.
- You get
- Zoning in a few lines, then a dimensioned SVG plan that has passed the clearance check, with every piece's size and where it goes.
- You decide
- Keep the plan, or ask for another arrangement.
-
- You
- Ask for a variant: a bigger bed, a desk added, a wheelchair-turning space.
- You get
- Another checked plan, or the exact number that keeps a piece out and the best option that fits.
You end with: A furniture plan that fits, ready to measure against the real room.
Compare Interior designer 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