product-frameworks
Comprehensive product design and management frameworks including UX heuristics (Hick's Law, Fitts's Law), design processes (Double Diamond, Lean UX, Agile, User-Centered Design), prioritization methods (RICE, MoSCoW, Kano Model, Pareto Principle), product lifecycle guidance, PRD templates, user story formats, design critique guidelines, and usability testing checklists. Use when analyzing features, creating product documentation, facilitating design reviews, planning user research, applying UX principles to interfaces, or making product decisions that require framework-based guidance.
What this skill does
# Product Frameworks ## Overview Comprehensive product design and management frameworks to guide strategic decisions, improve user experience, and structure product workflows. **Reference Files:** - [references/design-principles.md](references/design-principles.md) — Hick's Law, Fitts's Law, affordances, feedback - [references/design-processes.md](references/design-processes.md) — Double Diamond, Agile, Lean UX, User-Centered Design - [references/prioritization-frameworks.md](references/prioritization-frameworks.md) — RICE, MoSCoW, Kano Model, Pareto Principle - [references/lifecycle-guidance.md](references/lifecycle-guidance.md) — Product stage strategies - [references/requirements.md](references/requirements.md) — PRD templates, user stories, acceptance criteria - [references/critique-guidelines.md](references/critique-guidelines.md) — Design review facilitation - [references/usability-testing.md](references/usability-testing.md) — Test planning and analysis ## Quick Start 1. **Identify the domain** — Determine which area of product/design work you're addressing 2. **Load the relevant reference** — Read the specific reference file for that domain 3. **Apply the frameworks** — Use the guidance to inform decisions or structure workflows ## When to Use | Need | Reference File | |------|----------------| | UI/UX decisions | `design-principles.md` | | Planning discovery work | `design-processes.md` | | Evaluating features | `prioritization-frameworks.md` | | Product stage strategy | `lifecycle-guidance.md` | | Creating PRDs or user stories | `requirements.md` | | Running design reviews | `critique-guidelines.md` | | Planning user research | `usability-testing.md` | ## Example Workflows **Feature Evaluation:** 1. Load `prioritization-frameworks.md` for RICE and Kano Model 2. Load `lifecycle-guidance.md` for stage-specific priorities 3. Apply both for informed prioritization **Interface Design Feedback:** 1. Load `design-principles.md` for Hick's Law and Fitts's Law 2. Evaluate design against heuristics 3. Load `critique-guidelines.md` to structure feedback **Discovery Phase Planning:** 1. Load `design-processes.md` for Double Diamond 2. Load `usability-testing.md` for research planning 3. Structure discovery using both ## Framework Summaries **Design Principles:** Hick's Law (choice overload), Fitts's Law (target sizing), affordances, feedback loops, system status visibility **Design Processes:** Double Diamond (Discover→Define→Develop→Deliver), Agile, Lean UX, User-Centered Design **Prioritization:** RICE Scoring, MoSCoW (Must/Should/Could/Won't), Kano Model, 80/20 Rule **Lifecycle:** Introduction, Growth, Maturity, Decline stage strategies **Documentation:** PRD structure, user story format, acceptance criteria ## Best Practices **Progressive Loading:** Don't load all references at once. Start with the most relevant file, then add others as needed. **Context-Specific Application:** Frameworks are guidance, not rigid rules. Apply with judgment based on your product context. **Complementary Frameworks:** - Kano Model + RICE = comprehensive prioritization - Double Diamond + Lean UX = structured but iterative discovery - User-Centered Design + Usability Testing = validated user focus **Shared Language:** Use framework terminology to align teams and communicate with stakeholders.
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.