Files
Claude-Code-Game-Studios/.claude/skills/ux-design/references/4-authoring.md
T
DonchitosandClaude Opus 5.5 be8993bbc5 Release 1.1.3 — long skills keep their later steps
Fix release for 1.1.2: the 14 longest skills keep their later phases
after a compaction, a question nobody answered is never taken as an
answer, settings read the same from a subfolder, the commit check works
for a project in a subfolder of a larger repository, every skill opens
with a title, and the shipped allow rules no longer approve deleting a
branch or writing files without asking. Details in CHANGELOG.md; upgrade
steps in UPGRADING.md (v1.1.2 → v1.1.3).

Refs #83
Refs #133

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0185en4t76fPn7315q4c3nko
2026-10-08 17:52:48 +11:00

1.6 KiB

/ux-design — Section 4: Section-by-Section Authoring

Part of /ux-design. SKILL.md names when to read this file; the settings it resolved and the rules under its later headings still apply here.

4. Section-by-Section Authoring

Walk through each section in order. For each section, follow this cycle:

Context  ->  Questions  ->  Options  ->  Decision  ->  Draft  ->  Approval  ->  Write
  1. Context: State what this section needs to contain and surface any relevant constraints from context gathered in Phase 2.
  2. Questions: Ask what is needed to draft this section. Use AskUserQuestion for constrained choices, conversational text for open-ended exploration.
  3. Options: Where design choices exist, present 2-4 approaches with pros/cons. Explain reasoning in conversation, then use AskUserQuestion to capture the decision.
  4. Decision: User picks an approach or provides custom direction.
  5. Draft: Write the section content in conversation for review. Flag provisional assumptions explicitly.
  6. Approval: Use AskUserQuestion:
    • "Does this capture the [section name] correctly?"
    • Options: "Yes — write it to the file", "Small changes needed (describe below)", "Major rethink needed" Do not proceed to step 7 until the user selects "Yes".
  7. Write: Use AskUserQuestion: "May I write the [section name] section to [filepath]?"
    • Options: "Yes, write it", "Wait — one more change" Once confirmed, use Edit to replace the [To be designed] placeholder with approved content.

After writing each section, update production/session-state/active.md.