Loading...
Loading...
Found 372 Skills
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
Use this skill when planning user research, conducting usability tests, creating journey maps, or designing A/B experiments. Triggers on user interviews, usability testing, user journey maps, A/B test design, survey design, persona creation, card sorting, tree testing, and any task requiring user experience research methodology or analysis.
Expert methodology for analyzing and summarizing research papers, extracting key contributions, methodological details, and contextualizing findings. Use when reading papers from PDFs, DOIs, or URLs to create structured summaries for researchers.
You must use this when producing any research prose — literature reviews, syntheses, analyses, methodology descriptions, discussion sections, abstracts, or any written output intended for an academic audience.
Activates 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
Parent skill. Focuses on researching personal judgment, methodology, system capability and brand equity building in the AI era. Responsible for overall positioning control and task distribution.
Competitor comparison and alternative page creation for SEO and sales enablement. Covers 4 page formats (singular alternative, plural alternatives, vs pages, competitor vs competitor), content architecture, research methodology, and centralized competitor data management.
Apply TRIZ (Theory of Inventive Problem Solving) methodology to resolve technical contradictions and find innovative solutions. Use for engineering design, breaking through impossible constraints, and systematic innovation.
Triggered automatically at the start of each new top-level conversation to establish the general principle of "seeking truth from facts", and select downstream skills for subsequent tasks only when clearly applicable. Skip this skill if you are a delegated sub-agent performing a single specific task. English: Trigger at the start of each new top-level conversation to establish the core methodology and select downstream skills only when clearly useful. Skip this skill when you are a delegated sub-agent handling a narrow, concrete task.
Critical analysis of research papers, academic manuscripts, preprints, and technical studies — evaluating methodology, claims-evidence alignment, contribution significance, and intellectual honesty. Produces coherent analytical responses (not checklists) that distinguish genuine weaknesses from standard field limitations. Governs intellectual posture: collegial reader, not adversarial reviewer. Triggers on: "critique this paper", "review this research", "what do you think of this paper", "analyze this study", "evaluate the methodology", "is this paper sound", "assess this research", "strengths and weaknesses of this paper", "does the evidence support the claims". Use this skill when the user provides a research paper, preprint, or technical study and asks for critical evaluation of its scientific merit, methodology, or contribution — not formatting, citation hygiene, or submission readiness (use manuscript-review for those).
Design-driven development methodology. The design/ directory is the single source of architectural truth — read it before coding, stay within its boundaries, and when the system's shape needs to change, update the design first. Use this skill whenever starting any development work on this project. Also use when the user asks to: create or update architecture docs, add a new module or feature that might cross existing boundaries, refactor system structure, or understand the codebase architecture. Trigger on phrases like "design first", "update the design", "does this change the architecture", "write a design for", "what's the current design", or when onboarding to understand a codebase's shape. Supports arguments: `/design-driven init` to configure a project for design-driven development, `/design-driven bootstrap` to generate design from an existing codebase.
Design and analyze A/B tests with proper statistical methodology including sample size calculation, randomization, frequentist and Bayesian approaches, and sequential testing. Use this skill when the user needs to set up an experiment, calculate required sample size, interpret test results, or decide between testing methodologies — even if they say 'should we A/B test this', 'how many users do we need', 'is the test result conclusive', or 'can we stop the test early'.