From 2843587dedc642353a612dc22f8c351c24cca5a6 Mon Sep 17 00:00:00 2001 From: Ben Stull Date: Wed, 10 Jun 2026 21:30:29 -0700 Subject: [PATCH] content: ui/designs is per Solution Design, not per slice (ecomm#8) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- ui/designs/README.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/ui/designs/README.md b/ui/designs/README.md index e8b20ee..5a40764 100644 --- a/ui/designs/README.md +++ b/ui/designs/README.md @@ -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/`. -- 2.52.0