ux-breakdown
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-06-13
- Stars
- ★ 3
- Forks
- 1
03 SKILL.md 正文
UX Breakdown Skill
Parse .stitch/UX.md and extract structured screen definitions with Flutter navigation architecture.
Inputs
.stitch/UX.md— UX specification
Outputs
.stitch/SITE.md— Human-readable navigation map.stitch/screens.json— Machine-readable screen definitions
Procedure
- Read
.stitch/UX.mdand identify all screens described - For each screen, extract: id, title, route, description, features, priority
- Map the navigation architecture: bottom nav tabs, push routes, modal overlays
- Write
.stitch/SITE.mdas a navigational hierarchy - Write
.stitch/screens.jsonas a JSON array
SITE.md Format
# {App Name} — Navigation Map
## Bottom Navigation (ShellRoute)
- Home (/) — Main feed [tab: home icon]
- Browse (/browse) — Discovery and search [tab: search icon]
- Library (/library) — Personal bookshelf [tab: bookmark icon]
- Profile (/profile) — Settings and stats [tab: person icon]
## Push Routes (detail screens)
- Novel Detail (/novel/:id) <- tap card from Home, Browse, Library
- Chapter Reader (/novel/:id/chapter/:chapterId) <- tap chapter from Novel Detail
## Modal Overlays (bottom sheets & dialogs)
- Audio Player (overlay:audio-player) — Persistent mini player, expands to full sheet
- Sort Options (overlay:sort-options) — Bottom sheet with sort/filter controls
screens.json Schema
[
{
"id": "home-feed",
"title": "Home Feed",
"route": "/",
"description": "Personalized home feed with continue reading and trending",
"features": ["hero-card", "horizontal-scroll", "section-list", "pull-to-refresh"],
"navType": "tab",
"priority": 1
},
{
"id": "novel-detail",
"title": "Novel Detail",
"route": "/novel/:id",
"description": "Full novel info with chapter list and reading progress",
"features": ["sliver-app-bar", "hero-transition", "sticky-bottom-bar"],
"navType": "push",
"priority": 1
},
{
"id": "audio-player",
"title": "Audio Player",
"route": "overlay:audio-player",
"description": "Persistent mini player that expands to full bottom sheet",
"features": ["draggable-sheet", "playback-controls", "progress-slider"],
"navType": "overlay",
"priority": 2
}
]
Navigation Rules
GoRouter Structure
- ShellRoute wraps bottom navigation tabs — preserves tab state across switches
- GoRoute children of ShellRoute for each tab destination
- Nested GoRoute for detail screens pushed within a tab's navigation stack
Route Types
- Tab routes (
navType: "tab") — top-level routes under ShellRoute (/,/browse,/library,/profile) - Push routes (
navType: "push") — detail screens pushed onto the stack (/novel/:id,/novel/:id/chapter/:chapterId) - Overlay routes (
navType: "overlay") — bottom sheets and dialogs,overlay:prefix
Screen ID Rules
- Screen
idmust be unique, kebab-case - Routes use GoRouter format:
/path/:param - Tab screens: top-level routes under ShellRoute
- Detail screens: nested routes with path parameters
- Overlays:
overlay:prefix (overlay:audio-player) - Priority: 1 = critical, 2 = important, 3 = nice-to-have
04 同仓库更多 Skills
hello-checker
Use this skill when asked to "verify", "check", or "validate" a file's existence and content. It provides a reliable workflow for confirming files meet their spec.
ask-skill
暂无简介
html-review-artifact
Framework-wide guidance for crafting polished human-review artifacts as markdown or HTML
converge-planning
Design a Converge playbook end-to-end. Use when the user says "plan a project", "design a playbook", "decompose into tasks", "scaffold a Converge workflow", "onboard to Converge", or asks how to write TASK.md / playbook.yml. Two entry points: plan a new playbook or update an existing one. Hand off to `/converge-control` after producing the playbook structure.
converge-control
Operate a Converge playbook end-to-end — start runs, monitor progress, narrow failures with `--select`, inspect runtime state, validate definitions, surgically reset subtrees, and stop stuck or orphaned runs. Use this skill whenever the user says "run my playbook", "execute this", "monitor the run", "converge failed", "the run is stuck", "retry failures", "babysit this playbook", "what's the status?", "show me the gantt", or asks how to use `converge run` / `--select` / `inspect` / `doctor` / `clean` / `stop`. Also use it for `HTTP 401` / `Invalid API key` failures on the first task — those are environment-not-playbook problems — and for any post-run cleanup work. Hand off to `converge-planning` if the user wants to design or restructure the playbook itself.
repair-taskts
Fix task.ts definition issues — Seed syntax, missing .build(), empty checks, import errors, TypeScript errors