Loading...
Loading...
Found 344 Skills
Design Sprint methodology based on Jake Knapp's "Sprint" (Google Ventures). Use when you need to: (1) validate product ideas in 5 days instead of months, (2) rapidly prototype and test solutions, (3) answer critical business questions quickly, (4) align teams on product direction, (5) de-risk product development before building, (6) test multiple concepts with real users, (7) make fast strategic decisions through structured process.
Lean Startup methodology based on Eric Ries' "The Lean Startup". Use when you need to: (1) design MVP scope for new product ideas, (2) define validated learning experiments, (3) create innovation accounting frameworks, (4) decide when to pivot vs. persevere, (5) set up metrics that matter vs. vanity metrics, (6) reduce product development waste, (7) apply scientific method to entrepreneurship, (8) test business model assumptions quickly.
Senior-level UI/UX design skill with data-driven architecture for building premium, production-grade interfaces. Includes: BM25 search engine over 1,875+ data rows across 27 CSV databases, 8 Python scripts (search, contrast checker, palette/token/typography generators, design system generator, UI auditor), 16 tech stack guides, 11 reference documents, and 331 lines of intent-first design methodology. Covers: design token architecture, oklch color systems, typography hierarchies, spacing grids, depth strategies, component patterns, animation timing, WCAG 2.2 accessibility, cognitive science principles, and industry-specific reasoning for 30+ industries.
Official Feature-Sliced Design (FSD) v2.1 skill for applying the methodology to frontend projects. Use when the task involves organizing project structure with FSD layers, deciding where code belongs, defining public APIs and import boundaries, resolving cross-imports or evaluating the @x pattern, deciding whether logic should remain local or be extracted, migrating from FSD v2.0 or a non-FSD codebase, integrating FSD with frameworks, or implementing common patterns such as auth, API handling, Redux, and React Query within FSD.
PluginEval quality methodology — dimensions, rubrics, statistical methods, and scoring formulas. Use this skill when understanding how plugin quality is measured, when interpreting a low score on a specific dimension, when deciding how to improve a skill's triggering accuracy or orchestration fitness, when calibrating scoring thresholds for your marketplace, or when explaining quality badges to external partners like Neon.
Read production traces, identify what's failing, and build failure taxonomies using open coding and axial coding methodology. Use when debugging agent or pipeline quality, investigating "why are my outputs bad?", or before building any evaluator — error analysis must come first. Do NOT use when you already have identified failure modes and need evaluators (use build-evaluator) or datasets (use generate-synthetic-dataset).
Iterative UI/UX polishing workflow for web applications. The exact prompt and methodology for achieving Stripe-level visual polish through multiple passes.
Jeffrey Emanuel's comprehensive markdown planning methodology for software projects. The 85%+ time-on-planning approach that makes agentic coding work at scale. Includes exact prompts used.
Lead generation system using quiz/assessment funnels (Scorecard Marketing). Use when creating landing pages for lead generation, quiz funnels, online assessments, questionnaires that qualify leads, or any "lead magnet" that collects data while providing value. Based on Daniel Priestley's methodology that converts 30-50% vs 3-10% for traditional PDF lead magnets.
Expert translation methodology and best practices for English-Japanese-Chinese (Traditional) trilingual translation. Use when translating any content between these languages, including handling idioms, cultural nuances, and language-specific expressions. Provides translation workflows and quality assurance methods.
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Activated when users start a new novel project - Guides them through the seven-step methodology (constitution → specify → clarify → plan → tasks → write → analyze) with gentle prompts and explanations