Loading...
Loading...
Found 377 Skills
Expert system designer for tabletop roleplaying games covering dice mechanics, character creation, combat systems, narrative frameworks, GM tools, and playtesting methodologyUse when "tabletop rpg, ttrpg design, dice mechanics, character creation system, combat system design, gm tools, pbta, powered by the apocalypse, forged in the dark, blades in the dark, osr design, old school renaissance, narrative rpg, rules-light rpg, crunchy system, session zero, safety tools, x-card, fail forward, fiction first, player-facing rolls, advantage disadvantage, target number, dice pool, tabletop, rpg, game-design, dice-mechanics, pbta, osr, narrative-games, ttrpg, gm-tools, character-creation, blades-in-the-dark, forged-in-the-dark" mentioned.
Systematic implementation using APEX methodology (Analyze-Plan-Execute-eXamine) with parallel agents, self-validation, and optional adversarial review. Use when implementing features, fixing bugs, or making code changes that benefit from structured workflow.
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
Orchestrate the full one-person company workflow across all OPC skills. It is used when Codex needs to start, continue, or review the complete One Person Company (OPC) methodology process, read prior outputs from `opc-doc/`, determine the user's familiarity with relevant concepts and preferred interaction mode, explain terms when needed, ask one question at a time, offer user-selectable options, and summarize the next concrete action for Chinese-speaking users.
ChurnZero platform help — Health Scores, Plays & Automation, Journeys, Renewal Forecasting, In-App WalkThroughs, Surveys (NPS/CSAT/CES), AI Agents, REST API (OData v4). Use when health scores aren't predicting churn accurately, plays automation isn't triggering, Salesforce or HubSpot sync is broken, reporting dashboards feel inflexible, in-app WalkThroughs aren't reaching users, renewal forecasting numbers don't match CRM, or the ChurnZero API returns unexpected errors. Do NOT use for general customer success strategy (use /sales-customer-success) or NPS/CSAT survey methodology (use /sales-customer-feedback).
Test-Driven Development methodology and red-green-refactor workflow (formerly test-tdd). This skill should be used when practicing TDD, writing tests first, designing tests before implementation, or reviewing test-first approaches. Triggers on "write tests first", "test before code", "red green refactor", "test driven development". This skill does NOT cover Vitest framework specifics (use vitest skill) or API mocking with MSW (use msw skill).
Builds feedback collection systems using Superhuman's PMF framework and YC's "talk to users" methodology. Use when implementing NPS surveys, scheduling user interviews, or measuring product-market fit.
Set and track goals for a solopreneur business using OKRs (Objectives and Key Results) and related frameworks. Use when defining business goals, creating quarterly or annual targets, building KPIs, tracking progress, or aligning daily work with strategic direction. Covers OKR methodology adapted for solo operators, goal hierarchy (vision → annual → quarterly → weekly), and review cadences. Trigger on "set goals", "OKRs", "business goals", "quarterly goals", "KPIs", "goal setting", "how to track progress", "annual goals", "prioritize my work", "what should I focus on".
Core rules for bkit plugin. PDCA methodology, level detection, agent auto-triggering, and code quality standards. These rules are automatically applied to ensure consistent AI-native development. Use proactively when user requests feature development, code changes, or implementation tasks. Triggers: bkit, PDCA, develop, implement, feature, bug, code, design, document, 개발, 기능, 버그, 코드, 설계, 문서, 開発, 機能, バグ, 开发, 功能, 代码, desarrollar, función, error, código, diseño, documento, développer, fonctionnalité, bogue, code, conception, document, entwickeln, Funktion, Fehler, Code, Design, Dokument, sviluppare, funzionalità, bug, codice, design, documento Do NOT use for: documentation-only tasks, research, or exploration without code changes.
Help users apply the working backwards methodology. Use when someone is defining a new product, writing a PR/FAQ, planning from a future state, or trying to clarify a product's value proposition before building.
Systematic framework for evaluating scholarly and research work based on the ScholarEval methodology. This skill should be used when assessing research papers, evaluating literature reviews, scoring research methodologies, analyzing scientific writing quality, or applying structured evaluation criteria to academic work. Provides comprehensive assessment across multiple dimensions including problem formulation, literature review, methodology, data collection, analysis, results interpretation, and scholarly writing quality.
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.