Skip to content
Back to search

home-design-toolkit

MarketplaceWorks with Claude CodeGitHubIncomplete

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/gitkvash--home-design-toolkit/badge.svg)](/listings/gitkvash--home-design-toolkit)

HTML

<a href="/listings/gitkvash--home-design-toolkit"><img src="/api/listings/gitkvash--home-design-toolkit/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

/plugin marketplace add gitkvash/home-design-toolkit
/plugin install home-design@home-design-toolkit

Then run `/home-design:start` in an empty folder. It interviews you, creates a master plan, a brief, a decision log and a `plan.json`, and tells you the five measurements that would improve accuracy most.

Other assistants (Cursor, Codex, Gemini CLI, ChatGPT projects): the skills are plain Markdown with a short front-matter. Paste any `SKILL.md` into the agent's instruction files.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 11 lines
  1. {
  2. "name": "home-design-toolkit",
  3. "owner": { "name": "gitkvash" },
  4. "plugins": [
  5. {
  6. "name": "home-design",
  7. "source": "./",
  8. "description": "11 skills, 4 agents and 4 tools for planning and renovating a home: survey, layout audit, kitchen, bath, lighting, finishes, 3D viewer."
  9. }
  10. ]
  11. }
README.md · README · 103 lines
  1. # Home Design Toolkit
  2. **Plan your flat or house renovation with an AI assistant, and stop finding the mistakes after the carpenter leaves.**
  3. 11 skills, 4 agents, a `/home-design:start` command and four tested tools for Claude Code (or any agent that reads
  4. Markdown instructions). Everything here comes from a real project: a complete 69 m² flat, from bare shell to bought
  5. finishes, planned room by room with 3D models, layout audits and a lot of corrected assumptions.
  6. Free and open source (MIT). No account, no API key, no installs beyond Node 18+.
  7. [![test](https://github.com/gitkvash/home-design-toolkit/actions/workflows/test.yml/badge.svg)](https://github.com/gitkvash/home-design-toolkit/actions/workflows/test.yml)
  8. ![license: MIT](https://img.shields.io/badge/license-MIT-green)
  9. ![The 69 m² flat this toolkit was built on, modelled in three.js](docs/home-3d.jpg)
  10. | Living room and kitchen island | Plan view |
  11. |---|---|
  12. | ![Living room with kitchen island](docs/home-living.jpg) | ![Top-down plan of the flat](docs/home-plan.jpg) |
  13. *The real flat behind this toolkit: measured, laid out, audited and furnished with these skills, then built as a
  14. three.js model (see the `build-3d-room-model` skill and `tools/room-viewer`).*
  15. ## What it catches
  16. ```
  17. $ node tools/clash-audit/audit.mjs examples/example-flat/plan.json
  18. # living clear floor 16.67 m2
  19. out ok []
  20. ovl ok []
  21. swing ok []
  22. route NARROW window: 68 cm (min 75)
  23. route NARROW kitchen end: 60 cm (min 75)
  24. ```
  25. The example flat looks fine on a picture. The audit says you cannot comfortably walk to the window or to the end of
  26. the kitchen.
  27. A door that hits the sofa, a dishwasher you cannot open with the oven door down, wallpaper ordered without the
  28. pattern repeat, a pendant that does not fit the ceiling gap. These are the mistakes that cost money. The toolkit turns
  29. them into checks.
  30. ## Install in Claude Code
  31. ```
  32. /plugin marketplace add gitkvash/home-design-toolkit
  33. /plugin install home-design@home-design-toolkit
  34. ```
  35. Then run `/home-design:start` in an empty folder. It interviews you, creates a master plan, a brief, a decision log
  36. and a `plan.json`, and tells you the five measurements that would improve accuracy most.
  37. Other assistants (Cursor, Codex, Gemini CLI, ChatGPT projects): the skills are plain Markdown with a short
  38. front-matter. Paste any `SKILL.md` into the agent's instruction files.
  39. ## What is inside
  40. | | |
  41. |---|---|
  42. | **Skills** | `home-design-guide` (where to start, the order of work) · `home-survey` (plan screenshot + photos + tape → a plan you can trust) · `layout-clearances` (door swings, routes, clearances) · `interior-schemes` (comparable variants with a plain baseline) · `kitchen-planning` (appliances, sockets, circuits, gas, tile cuts, carpenter list) · `bathroom-planning` · `lighting-planning` (lux, zones, ceiling-gap fit) · `finishes-and-quantities` (floor, tile, wallpaper repeat and reserve, paint, radiators) · `product-research` (compare shops by price per m²) · `renovation-decisions` (append-only decision log, budget, order of works) · `build-3d-room-model` |
  43. | **Agents** | `interior-designer` · `layout-auditor` (runs the audit, explains each fault, proposes the smallest fix) · `product-scout` · `renovation-planner` |
  44. | **Command** | `/home-design:start`: interview and project setup |
  45. | **Tools** | `clash-audit` (furniture through walls, overlaps, blocked door swings, narrow routes) · `quantities` (area, tiles, wallpaper rolls, paint, radiator watts, circuit load, lux) · `room-viewer` (one-file three.js 3D viewer with opening doors) · `product-research` (price normalisation, dedupe, polite scraper starter) |
  46. | **Examples** | `examples/example-flat/`: an invented 2-room flat (`plan.json`) and a sample decision log |
  47. | **Docs** | `docs/lessons-learned.md`: what went wrong and what we would do differently |
  48. ## Try the tools without an AI
  49. ```
  50. node tools/clash-audit/audit.mjs examples/example-flat/plan.json
  51. node tools/quantities/calc.mjs help
  52. python -m http.server # then open http://localhost:8000/tools/room-viewer/index.html
  53. npm test
  54. ```
  55. Plans are checked against [`tools/clash-audit/plan.schema.json`](tools/clash-audit/plan.schema.json) before the audit
  56. runs. A malformed plan, or one written in centimetres instead of metres, exits with code 3 and a list of what is wrong.
  57. Add `"$schema": "<path to plan.schema.json>"` to a plan to get the same checks in your editor.
  58. ## The method in eight lines
  59. 1. Measure before designing; every number gets a source and a tolerance.
  60. 2. Write the brief as rules the layout can be checked against.
  61. 3. Make several comparable schemes per room, always one plain baseline.
  62. 4. Audit geometry (doors, routes, walls), not impressions.
  63. 5. Plan kitchen, bath and lighting from services and rules, not pictures.
  64. 6. Choose finishes once for the whole home; compare products by price per m² with a reserve.
  65. 7. Keep an append-only decision log; after a purchase, freeze that category.
  66. 8. Hand each trade a drawing, not a render.
  67. ## Honest limits
  68. These are planning aids, not structural, electrical, gas or waterproofing engineering. Confirm with licensed
  69. professionals and local code. Photo-derived dimensions are ±5-10 cm; a tape measure beats everything here.
  70. ## Contributing
  71. Issues and pull requests are welcome: local building rules from your country, new checks for the audit, better
  72. defaults for the calculators, translations. See [CONTRIBUTING.md](CONTRIBUTING.md). If the toolkit saved you a
  73. mistake, a ⭐ helps other people find it.
  74. ## License
  75. MIT, see [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.