interior-fitout-design
Skill39 starsChanged 23 days agoMITView on GitHub
Develop architectural interior and fit-out layouts, room planning, furniture/equipment zoning, reflected ceiling concepts, finish strategies, millwork/joinery briefs, lighting coordination and fit-out documentation. Use for workplace, residential, retail, hospitality, education and other interior projects.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architectural-drawing-generationSkill
- architecture-orchestratorSkill
- architecture-programmingSkill
- architecture-red-teamSkill
- area-quantity-auditSkill
- autocad-dwg-workflowSkill
- building-envelope-performanceSkill
- cad-bim-automationSkill
- civil-site-designSkill
- concept-design-reviewSkill
- concept-schematic-designSkill
- construction-administrationSkill
- construction-documentationSkill
- cost-planning-value-engineeringSkill
- drawing-qaSkill
- handover-fm-postoccupancySkill
- life-safety-accessibilitySkill
- materials-specificationsSkill
- mep-coordinationSkill
- openbim-ifc-coordinationSkill
- precedent-researchSkill
- presentation-reviewSkill
- revit-workflowSkill
- rhino-grasshopper-workflowSkill
- site-analysis-feasibilitySkill
- site-regulation-researchSkill
- structural-coordinationSkill
- sustainability-daylight-energySkill
- visualization-renderingSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Keep verified facts, project assumptions, design options, and unresolved questions visibly separate.
- Distinctive: line 41
Do not invent fire ratings, accessibility clearances or product certifications.
- Distinctive: line 46
If the native application is unavailable, produce a reproducible plan, script, structured data, SVG/DXF artifact, or exact in-application …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Interior & Fit-Out Design
Coordinate space, user experience, finishes, furniture/equipment and services without fabricating product or code data.
Preflight
- Room program, occupancy, accessibility needs, existing shell/core, fixed services/structure, equipment and client standards.
- Finish performance requirements, budget/lead-time constraints and target documentation stage.
Keep verified facts, project assumptions, design options, and unresolved questions visibly separate. If a required input is absent, record it as UNKNOWN rather than inventing it.
Workflow
- Zone functions and circulation; test furniture/equipment clearances against sourced requirements.
- Develop finish/material palette by performance, maintenance, acoustics, moisture, fire and visual intent.
- Coordinate reflected ceiling, lighting, sprinklers/diffusers, access panels, signage and major joinery interfaces at the appropriate level.
- Produce room/finish/equipment schedules and detail briefs; record long-lead or custom items.
Deliverables
- Furniture/equipment plan
- RCP/lighting coordination brief
- Finish/material schedule
- Room data and joinery/detail briefs
- Fit-out issue checklist
Verification
- Room IDs, levels, dimensions and schedules reconcile with architectural plans.
- Specified products and performance values are sourced and versioned.
For file/model changes, compare the result against a pre-change baseline and report changed items, skipped items, failures, and checks actually run.
Professional boundaries
- Do not invent fire ratings, accessibility clearances or product certifications.
- Electrical/lighting calculations and life-safety layouts require qualified discipline verification.
If a live CAD/BIM/GIS/analysis tool or MCP integration is available, inspect the current document/model and tool version before write operations. Prefer read-only inspection, dry runs, bounded samples, new output paths, and native undo/transaction mechanisms. Never claim a model or drawing was changed unless the tool confirms it.
If the native application is unavailable, produce a reproducible plan, script, structured data, SVG/DXF artifact, or exact in-application procedure instead of pretending to have operated the software.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.