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/5-crossref-handoff.md
View on GitHub# /saas-ux-design — Sections 5 and 6: Cross-Reference Check and Handoff
> 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.
## 5. Cross-Reference Check
Before marking the spec as ready for review, run these checks:
**1. PRD requirement coverage**: Does every PRD UI Requirement that references
this screen have a corresponding element in this spec? Present any gaps.
**2. Pattern library alignment**: Are all interaction patterns used in this spec
referenced by name? If a new pattern was invented during this spec session, flag
it for addition to the pattern library:
Use `AskUserQuestion`:
- "This spec uses [pattern name], which isn't in the pattern library yet. What should we do?"
- Options: "Add it to the pattern library now", "Flag it as a gap and continue", "Skip — this pattern is one-off"
**3. Navigation consistency**: Do the entry/exit points in this spec match the
navigation map in any related specs? Flag mismatches.
**4. Accessibility coverage**: Does the spec address the accessibility tier
committed to in `design/accessibility-requirements.md`? If not, flag open questions.
**5. Empty states**: Does every data-dependent element have an empty state defined?
Flag any that don't.
Present the check results:
> **Cross-Reference Check: [Screen Name]**
> - PRD requirements: [N of M covered / all covered]
> - New patterns to add to library: [list or "none"]
> - Navigation mismatches: [list or "none"]
> - Accessibility gaps: [list or "none"]
> - Missing empty states: [list or "none"]
---
## 6. Handoff
When all sections are approved and written:
### 6a: Update Session State
Update `production/session-state/active.md` with:
- Task: [screen-name] UX spec
- Status: Complete (or In Review)
- File: design/ux/[filename].md
- Sections: All written
- Next: [suggestion]
### 6b: Suggest Next Step
Before presenting options, state clearly:
> "This spec should be validated with `/saas-ux-review` before it enters the
> implementation pipeline. The Production gate (`/saas-gate-check production`)
> requires all key screen specs to have passed `/saas-ux-review` at `workflow: full`
> (recommended at `standard`)."
Then use `AskUserQuestion`:
- "Run `/saas-ux-review [filename]` now, or do something else first?"
- Options:
- "Run `/saas-ux-review` now — validate this spec"
- "Design another screen first, then review all specs together"
- "Update the interaction pattern library with new patterns from this spec"
- "Stop here for this session"
If the user picks "Design another screen first", add a note: "Reminder: run
`/saas-ux-review` on all completed specs before running `/saas-gate-check production`."
### 6c: Cross-Link Related Specs
If other UX specs link to or from this screen, note which ones should reference
this spec. Do not edit those files without asking — just name them.
---
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 |