Files
pbakaus_impeccable/docs/design-context-categorization
Abdul WahabandCursor bf8e3ee0c2 Add standalone design context prototype and WHAT spec.
Ship the browsable mosaic document as an isolated HTML file and document the build intent in WHAT.md so the categorization work has a concrete UI target.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-09-01 10:02:40 +05:00
..
2026-09-01 10:02:40 +05:00
2026-09-01 10:02:40 +05:00
2026-09-01 10:02:40 +05:00
2026-09-01 10:02:40 +05:00
2026-09-01 10:02:40 +05:00
2026-09-01 10:02:40 +05:00

Design Context Categorization

Analysis of what /impeccable init + /impeccable document currently produce (PRODUCT.md, DESIGN.md, .impeccable/design.json) against a proposed 8-category design context doc: Audience, Product, Brand, Color, Typography, Iconography, Material, Interface.

Source examples analyzed (local scratch runs, not tracked in this repo):

  • tmp/notes/init-tests/runs/noren-ops-20260708-1832/DESIGN.md + proof/PRODUCT.md + proof/design.json
  • tmp/notes/init-tests/runs/hanazono-atelier-20260708-1832/DESIGN.md + /Users/abdulwahab/hanazono-atelier/PRODUCT.md

Documents

  • WHAT.md — first draft of what we're building: a visual, browsable rendering of this categorization on the live site.
  • CONTENTS.md — what maps where, per category, with gaps and rationale.
  • CONTENTS-TABLE.md — the same mapping as lean per-category Value / Derived from / Source tables, no prose.
  • MISSING.md — content gaps neither example run produces, regardless of category.
  • ORPHANS.md — fields that exist today but don't have a clean home in the 8-category schema, plus open questions.
  • PROVENANCE.md — how the new visual document seed marks which fields are user-answered (resettable) vs. derived from code, and where that's stored.