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

Add ui/designs/ collection to wiggleverse-ecomm-content; standardize alongside specs/ and plans/ for all *-content repos #8

New Issue
Closed
opened 2026-06-11 03:20:19 +00:00 by ben.stull · 1 comment
ben.stull commented 2026-06-11 03:20:19 +00:00
Owner
Copy Link
Copy Source

Operator request (session ecomm-0023, 2026-06-10): UI designs need a standard home in content repos. Path fixed by operator: ui/designs/ (a ui/ namespace with designs/ under it).

Scope:

  1. wiggleverse-ecomm-content: add a ui/designs/ collection directory (with a short collection README) and document it in the repo's top-level README.md layout table alongside specs/ and plans/.
  2. Graduate the convention centrally (engineering repo): the content-repo collection convention currently names only specs/ and plans/ (schemas/README.md changelog 1.2, content descriptor description strings in schemas/app.schema.json). Extend those docs so ui/designs/ is a standard collection for all *-content repos.

Context: UI-design artifacts (e.g. Claude Design exports/decisions per solution-design/claude-design-vs-code.md) currently have no standard landing place in content repos.

Operator request (session ecomm-0023, 2026-06-10): UI designs need a standard home in content repos. Path fixed by operator: **`ui/designs/`** (a `ui/` namespace with `designs/` under it). **Scope:** 1. `wiggleverse-ecomm-content`: add a `ui/designs/` collection directory (with a short collection README) and document it in the repo's top-level `README.md` layout table alongside `specs/` and `plans/`. 2. Graduate the convention centrally (engineering repo): the content-repo collection convention currently names only `specs/` and `plans/` (schemas/README.md changelog 1.2, `content` descriptor description strings in `schemas/app.schema.json`). Extend those docs so `ui/designs/` is a standard collection for **all** `*-content` repos. **Context:** UI-design artifacts (e.g. Claude Design exports/decisions per solution-design/claude-design-vs-code.md) currently have no standard landing place in content repos.
ben.stull added the type/taskpriority/P2 labels 2026-06-11 03:20:19 +00:00
ben.stull changed title from Add ui-designs/ collection to wiggleverse-ecomm-content; standardize alongside specs/ and plans/ for all *-content repos to Add ui/designs/ collection to wiggleverse-ecomm-content; standardize alongside specs/ and plans/ for all *-content repos 2026-06-11 03:21:56 +00:00
ben.stull commented 2026-06-11 03:26:22 +00:00
Author
Owner
Copy Link
Copy Source

Done — ui/designs/ is live and standardized:

  1. wiggleverse/wiggleverse-ecomm-content#2 (merged @ b78453c): ui/designs/ collection + README row in wiggleverse-ecomm-content.
  2. wiggleverse/engineering#40 (merged @ 721538d): schemas docs 1.3 — the convention now names ui/designs/ for all *-content repos (docs-only, no validation change).

Spec-linkage gate + backfill gesture continue in wiggleverse/wiggleverse-dev-claude-plugin#93. Session: ecomm-0023.

Done — `ui/designs/` is live and standardized: 1. https://git.wiggleverse.org/wiggleverse/wiggleverse-ecomm-content/pulls/2 (merged @ b78453c): `ui/designs/` collection + README row in wiggleverse-ecomm-content. 2. https://git.wiggleverse.org/wiggleverse/engineering/pulls/40 (merged @ 721538d): schemas docs 1.3 — the convention now names `ui/designs/` for all `*-content` repos (docs-only, no validation change). Spec-linkage gate + backfill gesture continue in wiggleverse/wiggleverse-dev-claude-plugin#93. Session: ecomm-0023.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
priority/P0
Priority: highest — drop everything
 priority/P1
Priority: high
 priority/P2
Priority: medium
 priority/P3
Priority: low / someday
 type/bug
Type: a defect in shipped behaviour — small leaf work, straight to a plan
 type/epic
Type: a large body of work spanning many features
 type/feature
Type: a deliverable capability under an epic
 type/story
Type: a user story — the smallest valuable increment
 type/task
Type: a concrete unit of work under a story
No Label priority/P2 type/task
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ben.stull (Ben Stull) ohm-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wiggleverse/wiggleverse-ecomm#8
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?