ring:validating-ux-completeness
Validating that UX specifications are complete before technical design: a read-only checklist over wireframes, states, responsive behavior, accessibility, and component-library alignment, emitting a DESIGN VALIDATED / NEEDS REVISION verdict. Gate 1.5/2.5, runs after ring:writing-prds or ring:mapping-feature-relationships, before ring:writing-trds. Use to check UI design completeness. Skip for backend-only, API-only, or no-UI work.
What this skill does
# Design Validation Gate
## When to use
- After PRD + UX criteria created (Gate 1)
- After Feature Map + UX Design created (Gate 2, Large track)
- Before starting TRD (Gate 3)
- User asks to "validate design" or "check if design is complete"
## Skip when
- Feature is backend-only with no UI
- Pure API/infrastructure task
- Bug fix with no UX changes
## Sequence
**Runs before:** ring:writing-trds
**Runs after:** ring:writing-prds, ring:mapping-feature-relationships
Verifies that UX specifications are COMPLETE before investing in technical architecture. This is a VALIDATION gate — it checks existing artifacts, does not create new ones.
TRD will STOP if this file is missing or verdict is not "DESIGN VALIDATED" for UI features.
## Gate Entry Criteria
| Artifact | Location | Required For |
|----------|----------|--------------|
| `prd.md` | `docs/pre-dev/{feature}/` | all features |
| `ux-criteria.md` | `docs/pre-dev/{feature}/` | all features with UI |
| `wireframes/` | `docs/pre-dev/{feature}/wireframes/` | all features with UI |
| `user-flows.md` | `docs/pre-dev/{feature}/wireframes/` | all features with UI |
| `feature-map.md` | `docs/pre-dev/{feature}/` | Large track only |
If artifacts do not exist → STOP. Return to previous gate.
**If feature has NO UI** → Skip this gate, proceed to TRD. Feature has UI if PRD contains: user stories with "see", "view", "click", "navigate", "page", "screen", "button", "form", or features involving login, dashboard, settings, profile, reports, notifications.
## Validation Checklist
### Section 1: Screen Completeness (CRITICAL — failure = HARD STOP)
- [ ] All screens from user stories have wireframes
- [ ] Each wireframe has all required UI elements
- [ ] Interactive elements identified (buttons, forms, links)
- [ ] Navigation flows between screens defined
- [ ] No screen in user stories is missing a wireframe
### Section 2: State Coverage (CRITICAL — failure = HARD STOP)
- [ ] Empty states designed (no data scenarios)
- [ ] Loading states shown
- [ ] Error states for each failure scenario
- [ ] Success states for key actions
- [ ] Edge cases with extreme content (long text, many items)
### Section 3: Responsive Behavior
- [ ] Desktop layout defined
- [ ] Mobile layout defined (or explicit "mobile not required" statement)
- [ ] Tablet behavior specified or derived from desktop/mobile
- [ ] Breakpoints documented
### Section 4: Accessibility
- [ ] Color contrast documented (AA minimum)
- [ ] Focus order for keyboard navigation specified
- [ ] ARIA labels for non-text elements
- [ ] Screen reader behavior documented for dynamic content
### Section 5: Interaction Details
- [ ] Form validation feedback shown (inline errors)
- [ ] Confirmation dialogs for destructive actions
- [ ] Feedback for async operations (loading, success, error)
- [ ] Tooltips and help text defined
### Section 6: Data Display
- [ ] Pagination or infinite scroll for lists
- [ ] Sort and filter behavior defined (if applicable)
- [ ] Data formatting (dates, numbers, currency)
- [ ] Truncation behavior for long content
### Section 7: Component Consistency
- [ ] Reuse of existing components documented
- [ ] New components needed identified
- [ ] Variants used consistently (button types, input states)
- [ ] Spacing and layout grid consistent
### Section 8: Component Library Alignment (if UI library configured)
- [ ] Components needed exist in chosen library
- [ ] Correct variant names used (not invented variants)
- [ ] Missing components identified for custom implementation
## Verdict
**DESIGN VALIDATED:** All Section 1-2 items pass AND ≥80% of Sections 3-8 pass.
**DESIGN NEEDS REVISION:** Any Section 1-2 item fails → list specific gaps → return to product-designer.
**File output:** `docs/pre-dev/{feature}/design-validation.md`
```markdown
# Design Validation Report
**Feature:** {feature-name}
**Date:** {YYYY-MM-DD}
**Track:** Small | Large
**Verdict:** DESIGN VALIDATED | DESIGN NEEDS REVISION
## Results
| Section | Status | Notes |
|---------|--------|-------|
| 1. Screen Completeness | ✅ PASS / ❌ FAIL | ... |
| 2. State Coverage | ✅ PASS / ❌ FAIL | ... |
| 3. Responsive Behavior | ✅ PASS / ⚠️ PARTIAL | ... |
...
## Gaps Found (if REVISION needed)
- [Specific gap 1]
- [Specific gap 2]
## Next Step
VALIDATED → Proceed to ring:writing-trds
REVISION → Return to product-designer with gap list
```
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.