content: ui/designs is per Solution Design, not per slice (ecomm#8)

Operator correction: designs live at the Solution-Design level — one subfolder per spec (ui/designs/SD-0001/), not per slice. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Merge pull request 'content: add ui/designs/ collection (ecomm#8)' (#2 ) from ui-designs-collection into main
2026-06-10 21:30:29 -07:00 · 2026-06-11 03:24:35 +00:00 · 2026-06-10 20:24:11 -07:00
2 changed files with 12 additions and 0 deletions
@@ -11,6 +11,7 @@ repo.
 | --- | --- |
 | `specs/` | reviewed Solution-Design specs (submitted at session finalize) |
 | `plans/` | archived implementation plans |
 | `ui/designs/` | UI-design artifacts (Claude Design outputs), referenced from specs |
 Roadmap and the deployment version `pin` will be added as the build gets underway.
@@ -0,0 +1,11 @@
 # ui/designs — UI-design artifacts
 Standard content-repo collection (alongside `specs/` and `plans/`) holding this
 app's UI-design artifacts — primarily Claude Design outputs generated from a
 Solution Design (rubric: `engineering/solution-design/claude-design-vs-code.md`).
 Designs are kept at the **Solution-Design level** (one design per spec, not per
 slice): one subfolder per Solution Design, e.g. `ui/designs/SD-0001/`. The spec
 references its design artifact here by path; the spec-linkage gate and the
 backfill gesture for adding that reference once a design exists are tracked in
 [wiggleverse-dev-claude-plugin#93](https://git.wiggleverse.org/wiggleverse/wiggleverse-dev-claude-plugin/issues/93).