Tasks: UI/UX design artifacts in the design phase
Derived from the approved
design.md. Docs/plugin-content change — the "tests" are the config validator and markdownlint (see design → Testing strategy).
Task list
- [x] 1. Add
design.uiArtifactsconfigconfig.schema.json(newdesignsection),config.yaml,templates/config.yaml.- Depends on: none
- Requirements: R2
- Test:
python scripts/validate_config.pyexits 0
- [x] 2. Track the
design/artifact in the manifest- New optional
spec-design-artifactswork-item artifact (phasedesign). - Depends on: none
- Requirements: R1
- Test:
markdownlint/inspection; validator green
- New optional
- [x] 3. Add the UI/UX design section to the design template
.the-loop/templates/design.md— inventory table + flows/tokens/a11y/evidence.- Depends on: 1
- Requirements: R1
- Test:
markdownlintpasses on the template
- [x] 4. Write the
design-artifacts.mdreference (the designer iteration loop)- New
skills/the-loop/reference/design-artifacts.md; self-contained rule; Figma↔code; evidence & hand-off. - Depends on: none
- Requirements: R3, R4
- Test:
markdownlintpasses
- New
- [x] 5. Wire commands + skill + README
create-design.md,work-on.md,SKILL.md,reference/workflow.md,reference/collaboration.md,README.mdreference the convention and the new doc.- Depends on: 3, 4
- Requirements: R5
- Test:
markdownlintpasses on all changed docs
- [x] 6. Record the decision
docs/decisions/decision-018.md+ decisions index.- Depends on: 1–5
- Requirements: R1–R5 (rationale)
- Test:
markdownlintpasses
- [x] 7. Dogfood: write the issue-18 spec + illustrative artifact
docs/specs/issue-18/{requirements,design,tasks,execution-log}.mdand a self-containeddesign/design-phase-artifacts.html.- Depends on: 1–6
- Requirements: R1–R5 (demonstration)
- Test:
markdownlintpasses; validator still green; the HTML has no external deps
Dependency graph (DAG)
1 → 3 → 5
4 → 5
{1,3,4,5} → 6 → 7
2 → 7Checkpoints
After task 1 and again after task 7: run python scripts/validate_config.py and pre-commit run --all-files (ruff/pyright/markdownlint/schema) — record the outcome in execution-log.md.