content: add ui/designs/ collection (ecomm#8) #2

Merged
ben.stull merged 1 commits from ui-designs-collection into main 2026-06-11 03:24:35 +00:00
2 changed files with 14 additions and 0 deletions
+1
View File
@@ -11,6 +11,7 @@ repo.
| --- | --- | | --- | --- |
| `specs/` | reviewed Solution-Design specs (submitted at session finalize) | | `specs/` | reviewed Solution-Design specs (submitted at session finalize) |
| `plans/` | archived implementation plans | | `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. Roadmap and the deployment version `pin` will be added as the build gets underway.
+13
View File
@@ -0,0 +1,13 @@
# 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`).
A Solution Design with a UX-involving slice 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).
Suggested layout: one subfolder per design, named for the spec/slice it serves,
e.g. `ui/designs/SD-0001-slice-3-storefront/`.