SuperAPI AI Directory

furniture-planner

General & other

View repository

Updated 10-16 06:14

About this skill

Furniture Planner

Design custom furniture based on the measurements of the available space. Generate an interactive HTML technical drawing with SVG views, BOM, optimized cut list, hardware and assembly sequence.

Workflow

Phase 1: Space

Obtain the dimensions of the room where the furniture will go, in this order:

  1. Existing JSON plan: try to read ~/Casa/datos/plano.json (generated by the mi-casa skill).
  2. Architectural plan: if the user provides an image or PDF, consult references/lectura-planos.md to interpret dimensions, walls and openings.
  3. Manual: if none of the above is available, ask the user for:
  • Dimensions of the space: available width, height, depth (mm)
  • Obstacles: outlets (position from floor and from the side), pipes, windows, baseboards (height in mm), unevenness
  • Access: how the furniture gets in (doors, hallways — relevant for large furniture)

Confirm measurements with the user before moving forward.

Phase 2: Type of furniture

Classify according to construction method:

Box furniture (combinable modules): base cabinet, wall cabinet, wardrobe, bookcase, TV stand, vanity, shelving

Structure furniture (legs + top): table, desk, bench, coffee table, kitchen island

Complex furniture (structure + special joints): chair, stool — require more detail on joints and angles

Apply standard dimensions as defaults according to type. Consult references/dimensiones-estandar.md for values per type of furniture. Present the defaults to the user and let them adjust.

Phase 3: Material

Consult references/materiales.md for available options. Ask:

  1. Base material: 18mm phenolic pine plywood (2440x1220), 18mm melamine (2750x1830), 18mm MDF (2750x1830), or other
  2. Finish: comes with melamine, paint/lacquer, varnish, formica/HPL
  3. Edge banding: 2mm PVC (visible edges), 1mm PVC (semi-visible), 0.4mm melamine (hidden)
  4. Supplier: ask if they have a supplier or their own quote
    • If they do → use those prices directly
    • If they don't → the skill looks for prices in Phase 5 (Quote)
  5. Country/region: ask where they buy the materials (e.g. Argentina, Uruguay, Chile)
    • It is used in Phase 5 to load local suppliers if they exist

Phase 4: Composition

Depends on the type of furniture:

For box furniture → Consult references/modulos.md for the catalog of available modules (drawers, doors, open, doors+shelves, corner unit). Choose the composition according to the Design maximums (section below).

Validate that the sum of module widths does not exceed the available space. If there is leftover space, offer fillers.

For structure furniture → Consult references/modulos.md the "Structure templates" section. Define dimensions of top, legs, aprons.

For complex furniture → Consult references/modulos.md the "Complex templates" section. Guide with angles and joints.

Phase 5: Quotation

With the complete BOM (Phase 4 parts + hardware from references/herrajes.md + screws), quote all items.

If the user has a supplier/quote → use those prices, skip to Phase 6.

If they don't have one → search for each item with WebSearch/WebFetch:

  1. Build complete BOM: list boards (qty, material, size), hardware (type, model, qty), edge banding, screws
  2. Load suppliers: search references/proveedores-{país}.md (e.g.: proveedores-ar.md for Argentina). If it exists, use the supplier list by material type with URLs and search tips. If it doesn't exist, search generically with WebSearch in local stores of the indicated country
  3. Validate alternatives: if the exact product is not found, search for the closest match. Compare technical specs (load, size, mounting type) against what the furniture needs. If it is not technically suitable, explain why and search for another option
  4. Compare between suppliers: for each item, record the price at all suppliers where it was found
  5. Optimize by supplier: group the shopping list by supplier so that the total is as low as possible, prioritizing good quality over minimum price. Consider that buying several items from the same supplier may be worthwhile for shipping/travel

Output: shopping list grouped by supplier with price per item and total per supplier.

Phase 6: Generation

Consult references/metodos-construccion.md for assembly rules and references/herrajes.md for hardware selection.

  1. Calculate BOM: list each part with thickness x width x length, grain direction, edge banding per side using the F/B/L/R convention (Front/Back/Left/Right — see glossary in references/modulos.md)

  2. Optimize cuts: group parts by thickness, calculate how many boards are needed (saw kerf: 3mm, add 10% waste)

  3. List hardware: hinges, slides, supports, screws, handles — with quantities

  4. Assembly sequence: logical step-by-step order

  5. Total cost: use prices from Phase 5, broken down by supplier

  6. Generate HTML: read references/html-template.md for the output scaffold. Generate the HTML with:

    • SVG views: front, side (section), plan
    • Complete BOM table
    • Cut list with number of boards
    • Hardware list
    • Numbered assembly sequence
    • Shopping list by supplier (supplier → items → price → total)
    • Total project cost

    Create directory ~/Casa/muebles/ if it doesn't exist. Save as ~/Casa/muebles/{nombre}-plano.html.

  7. Export CorteCloud (optional): if the user uses a cutting service or asks to export for CorteCloud, check references/cortecloud-excel.md for format and mapping rules. Generate Excel with skill document-skills:xlsx. Group pieces by Material+Thickness (one file per group, exclude 3mm hardboard backs unless the user asks). Save as ~/Casa/muebles/{nombre}-cortecloud.xlsx (or {nombre}-cortecloud-{material}.xlsx if there are multiple materials).

Phase 7: Prompt for render (optional)

After generating the HTML, offer: "Do you want me to put together the prompt to generate a render of the furniture?"

If the user accepts, build the prompt and return it as chat output (do not run any image generation here). The user will then pass it to skill nano-banana when they want the render.

Build the prompt according to references/render-prompts.md:

  • Structure: [composition] [subject] in [style] with [lighting], featuring [details]
  • Choose the template according to the furniture type (kitchen, closet, table, bookcase, TV rack)
  • Apply texture keywords according to the material chosen in Phase 3
  • Add "no people, no text" for a cleaner result
  • Suggest aspect ratio according to the furniture's orientation

Output: the prompt in a copyable code block, ready to paste into nano-banana. It is not a replacement for the technical SVG plans — it is a complementary visualization.

Design maxims

Hard rules when choosing composition and modules. Always apply unless the user explicitly requests otherwise. Each rule includes its "why" so that exceptions can be judged.

Low furniture (waist height or below, ~900mm high or less)

  • Prefer drawers over doors. With doors you have to bend down and feel around for the back of the module; with drawers all the contents are visible when you open them. Exception: under-counter with sink, gas/water connections, or pipes that force a door.
  • Drawer modules: no back panel on the module. The back panel of the module (not of the drawer — the drawer always has its 5 sides) is never seen: it sits against the wall and the drawers cover it. Removing it saves considerable material and the lateral telescopic slides already provide rigidity to the carcass. Reflect the omission in the Phase 6 BOM. Exceptions: (a) freestanding furniture visible from behind → keep the panel; (b) concealed slides such as Blum Tandembox/Hafele that require a screwed-on bracket → keep the panel for anchoring.

Tall furniture (wall cabinets, hanging units, above the line of sight)

  • Prefer doors over drawers. At that height drawers are above the line of sight and are awkward to operate (you can't see inside when you open them).
  • Door width ≤ 450mm. Two reasons: (1) a wider door, when opened, projects far from the front of the cabinet and can hit the face of the person operating it; (2) standard cup hinges lose structural stability and soft-close above that width. If the module exceeds 450mm in width, split it into two doors.
  • Door front 20–30mm shorter than the height of the module body (when it has under-cabinet LED). "Module body" = height of the side panel (vertical piece). The lower edge of the door sits higher than the base of the cabinet, leaving a concealed edge where the LED strip is housed. This illuminates the countertop without the light source being exposed at the eye level of a seated person — which is typically at the height of the lower edge of the upper cabinet. If the wall cabinet does not have LED, the front sits flush with the body. By default, assume it has LED in kitchens and ask the user.

Technical details

See references/metodos-construccion.md for rules on materials, joints, edge banding, ergonomics, and other construction details.