Capabilities
Each page below is the behavioural source of truth for one area of the product: what it must do, stated as requirements with concrete scenarios. They are written before the code and reviewed alongside it, so they describe what Tinkerspace does today rather than what was planned.
Tinkerspace’s AI surfaces let a designer work faster inside a project without leaving the 3D editor: rooms are labeled automatically from geometry, a chatbot co-designer edits the scene on request, a moodboard is distilled into a style brief that steers the chatbot, and a walkthrough snapshot can be restyled through an image-to-image pipeline. A broader “generate variants, then round-trip the pick into scene edits” flow is planned but not yet built — only the restyle substrate it would sit on exists today.
How a signed-in user moves around Tinkerspace: the destinations the shell offers, what it reports while a navigation is in flight, and what remains visible when a surface takes over the whole screen.
Covers the left rail, the position trail (breadcrumbs), the route-progress indicator, and the ⌘K jump
palette — on shell pages and on the full-screen editor and walkthrough, which sit outside
AppShell and would otherwise each invent their own way back.
Integrating without duplicating:
- Which destinations a user may reach is decided in one place —
apps/web/lib/nav/destinations.ts. The rail and the palette both read it. Adding a destination means adding it there, not in a component. Do not restate theadmin/salesrules anywhere else: who may see a destination isauth-orgs-admin’s requirement, and this capability only consumes it. - The trail is derived, not stored —
apps/web/lib/nav/crumbs.tsmaps a pathname plus whatever context the caller already has (org name, project name) to the crumb list. A new route that should appear in the trail is an entry in that map. - Motion is gated in one stylesheet —
apps/web/app/_components/nav/nav-chrome.ts. Both the reduced-motion rule and the “yield to the 3D canvas” rule live there. New navigation chrome should take anash-*class rather than inline its own transitions, or it will silently escape both gates. - Not in scope here: the editor’s own toolbar chrome (
floorplan-editor,modeling-tools), the walkthrough’s in-scene HUD (walkthrough), and authentication or role assignment (auth-orgs-admin).
Authentication, multi-tenancy, and platform administration for Tinkerspace. Every signed-up user is authenticated by email + password with mandatory email verification, is auto-provisioned a personal organization to scope their data, and may hold one of two elevated platform roles (admin super-admin, sales invoice-only) layered on top of per-organization membership roles.
Provide Stripe-backed monetization for Tinkerspace: one-off AI-credit purchases, a recurring vendor catalogue subscription, vendor ad-wallet top-ups, and ad-hoc sales invoices — all fulfilled through a single Stripe webhook so that payment confirmation is idempotent and centrally auditable.
The catalog is Tinkerspace’s library of placeable 3D content (furniture, fixtures, lighting, decor) and texture-backed materials that designers use in floorplan scenes. It guarantees that assets arriving through any acquisition path (AI generation, direct upload, craft composition, or admin batch import) converge on the same canonical, optimized, org-scoped, real-world-scaled representation before a client can load them.
@ideight/domain is the single source of truth for every persisted data shape in Tinkerspace: the floorplan document (walls, openings, placed furniture, cladding, MEP) and the catalog asset row. It guarantees that one zod schema per entity is both the runtime validator and the compile-time type, and that this schema is what every downstream layer (engine Y.Doc, API JSONB columns, web editor) ultimately validates against or is type-checked from.
The engine (@ideight/engine) is the single headless model of a floorplan that every editor surface — 2D plan, 3D orbit, walkthrough — renders from and mutates through. It guarantees that all surfaces, and all collaborators editing at once, stay consistent by construction: one shared document, one mutation path, one room-detection algorithm, one unit-conversion boundary.
The floorplan editor is the main design surface at /projects/[id]: a full-screen 3D canvas where a designer draws walls, cuts openings, places catalog furniture, builds carpentry, and walks through the unit in first person. It exists to let one or more collaborators edit a project’s floorplan in real time with every change automatically synced and undoable, across desktop pointer input and touch/iPad gestures.
Tinkerspace renders floorplan scenes across several contexts (editor, walkthrough, catalog thumbnails, vendor/staging views), each needing correctly-lit, PBR-plausible output without every view reimplementing a rig. This capability defines the lighting behavior guaranteed in each context: a legacy fixed rig as the universal default, an opt-in physically-based day/night rig driven by real sun/moon positions, a self-contained thumbnail rig for consistent catalog imagery, and per-asset lamp emission.
Modeling tools are the “custom build” layer of the floorplan editor — everything a designer models in place rather than picks from the catalog: parametric carpentry, cladding cover-ups (box covers, panels, false ceilings, curved walls), SketchUp-style free-form solid editing, Craft composite assets, stacking of items on surfaces, and parametric MEP (plug points, switches, pipes, wiring). All of it is Yjs-backed via the Floorplan facade, so every gesture is collaborative and a single undo step.
Every project’s design state (floorplan, scene items, notes, vendor scenes) is shared through a single live document rather than owned by one client. This capability keeps all peers viewing the same project converged on the same state in real time, while keeping transient UI state (selection, hover, tool mode, cursors) local to each peer instead of polluting the shared project.
The admin surface for room furnishing recipes: authoring one, seeing which positions in a room its stations actually reach, checking each station against the live catalogue, and dry-running the result against a real traced HDB unit before any of it ships. It exists so a recipe defect is found while the recipe is being written rather than after a branch, a CI run and a deploy.
The catalogue of HDB units a homeowner can start a project from — what is known about each one, which of them can actually be furnished, and how someone asks for a unit that has not been traced yet.
/walkthrough/[id] lets an invited client explore a project’s live 3D scene in first person, measure spaces, make light edits, and request a photorealistic restyle of any view via ComfyCloud — giving designers a client-review surface that reflects the real, editable scene rather than a static export.