Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-ux-design
saas-ux-design
UnverifiedAuthor UX specs for App Shell, core screens, interaction patterns, and WCAG accessibility.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.1 KB |
| references/2-gather-context.md | markdown | 8.5 KB |
| references/3-file-skeleton.md | markdown | 5.1 KB |
| references/4-authoring.md | markdown | 1.6 KB |
| references/5-crossref-handoff.md | markdown | 2.9 KB |
| references/sections-app-shell.md | markdown | 7.7 KB |
| references/sections-patterns.md | markdown | 2.0 KB |
| references/sections-ux-spec.md | markdown | 12.0 KB |
references/4-authoring.md
View on GitHub# /saas-ux-design — Section 4: Section-by-Section Authoring
> Part of `/saas-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`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |