wiggleverse/wiggleverse-ecomm-content
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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>
This commit is contained in:
Ben Stull
2026-06-10 21:30:29 -07:00
parent b78453c0f6
commit 2843587ded
1 changed files with 4 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ui/designs/README.md
+4 -6
View File
@@ -4,10 +4,8 @@ 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
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).
Suggested layout: one subfolder per design, named for the spec/slice it serves,
e.g. `ui/designs/SD-0001-slice-3-storefront/`.