Skip to the rows

agentsclimarketplace

Interior design os

Skill chiragg-ds/claude-skills/skills/interior-design-os

Composable Claude Code skills for building Notion CRM + Operations OS workspaces.

Install

npx -y skills add chiragg-ds/claude-skills --skill interior-design-os

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

End-to-end bootstrap of an opinionated Notion CRM + Operations OS for an interior design studio. Orchestrates the other 5 notion-* skills. Use when onboarding a new interior designer client.

SKILL.md

3.5 KB, 803 tokens by cl100k_base, as published. Nobody here has run it

interior-design-os

Bootstrap a complete Notion OS for an interior design studio. Orchestrates the other 5 notion-* skills in the correct order. End-to-end target: under 2 hours from empty workspace to seeded OS + walkthrough doc.

What gets built

9 sections, 19 databases, full cross-DB relations
8 helper formulas (Is Overdue, SLA Breach, Is Active, Needs Follow-up, etc.)
5 rollups (Checklist Done/Total, Task Done/Total, Handover Completion %)
~25 task templates with dependency-wiring
~25 QC checklist items, ~29 drawing-register entries, 44 handover items
Operations Cockpit page with Decision Queue + KPIs + filtered views
Personalized walkthrough doc (Jinja2 templated)
GitHub Actions for hourly task auto-seeding + Monday Weekly Status Log

Prerequisites

NOTION_API_KEY env var
A root page created in the target Notion workspace, shared with the integration
That page's ID
The chiragg-ds/interior-design-os template repo (cloned via gh repo create --template)
client.config.yaml populated (brand name, GST rate, fee stages, work scopes)

Steps

Confirm config — verify client.config.yaml has been edited from the example. Required fields: client.name, brand.name, financials.gst_rate, financials.fee_stages, financials.invoice_due_days, notion.root_page_id.
Provision (notion-provision) — sections + DBs:
```
python3 notion-os/provision.py
```
Validate: ids.json written with all 19 DBs.
Schema dump (notion-schema-dump) — generate canonical reference:
```
python3 notion-os/dump_schema.py
```
Helper formulas (notion-helper-formulas) — apply Studio Nuvah formula presets:
```
python3 notion-os/add_helper_formulas.py
```
Seed templates (notion-seed) — load all 4 seed files:
```
python3 notion-os/seed_all.py
```
Cockpit (notion-cockpit) — render Operations Dashboard:
```
python3 notion-os/build_cockpit.py
```

Walkthrough — render branded doc:

python3 scripts/generate_walkthrough.py

Hand off to client:
- Walk through docs/WALKTHROUGH.md
- Walk through docs/MANUAL-UI-STEPS.md (Cockpit linked views, native automations, permissions)
- Configure NOTION_API_KEY secret in GitHub Actions for the auto-seed + weekly-status workflows

When to use this skill

Onboarding a new interior-design client.
Spinning up a test workspace to validate template changes.

When NOT to use

For a non-interior-design vertical (architect, photographer, event-planner). Compose the other 5 skills with that vertical's seeds + cockpit spec instead.
For surgical edits to an existing OS. Use the underlying skills (notion-helper-formulas, notion-seed, etc.) directly.

Why a meta-skill

Each underlying primitive skill is vertical-agnostic and reusable. This meta-skill captures the interior-design opinion: which DBs, which seeds, which formulas, which cockpit layout. Future vertical meta-skills (architect-os, furniture-studio-os) will compose the same primitives differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.