Loading...
Loading...
Found 256 Skills
Use this methodology when collaboratively shaping a solution with the user - iterating on problem definition (requirements) and solution options (shapes).
Expert-level research methodology, academic writing, statistical analysis, and scientific investigation
Provides visual identity direction and creative briefing frameworks including Alina Wheeler's five-phase process, strategy-to-visual translation method, mood board methodology, logo brief structure, photography style frameworks, and typography/color direction. Auto-activates during visual direction, creative briefing, mood board creation, logo brief writing, and visual identity system work. Use when discussing visual direction, creative briefs, mood boards, logo briefs, photography style, visual identity, visual strategy, visual translation, visual expression, design direction, or visual language.
Create Product Requirements Documents (PRD) following SDD methodology - Layer 2 artifact defining product features and user needs
Systematic debugging methodology with root cause analysis. Phases: investigate, hypothesize, validate, verify. Capabilities: backward call stack tracing, multi-layer validation, verification protocols, symptom analysis, regression prevention. Actions: debug, investigate, trace, analyze, validate, verify bugs. Keywords: debugging, root cause, bug fix, stack trace, error investigation, test failure, exception handling, breakpoint, logging, reproduce, isolate, regression, call stack, symptom vs cause, hypothesis testing, validation, verification protocol. Use when: encountering bugs, analyzing test failures, tracing unexpected behavior, investigating performance issues, preventing regressions, validating fixes before completion claims.
Convert text with private context or internal dependencies into generic, unbiased expressions. Use for project decontextualization (handoff, open-source prep), methodology abstraction, cross-team sharing, anonymization. Includes path strings and file/folder names as they appear in text.
Transform clichéd story elements by pushing along the emotional vector toward statistical edges. Use when first instincts are too predictable, when elements feel generic, or when you need the core methodology for avoiding statistical-center defaults.
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.
Use when formulating clinical research questions (PICOT framework), evaluating health evidence quality (study design hierarchy, bias assessment, GRADE), prioritizing patient-important outcomes, conducting systematic reviews or meta-analyses, creating evidence summaries for guidelines, assessing regulatory evidence, or when user mentions clinical trials, evidence-based medicine, health research methodology, systematic reviews, research protocols, or study quality assessment.
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.
Create high-quality ToolUniverse skills following test-driven, implementation-agnostic methodology. Integrates tools from ToolUniverse's 1,264+ tool library, creates missing tools when needed using devtu-create-tool, tests thoroughly, and produces skills with Python SDK + MCP support. Use when asked to create new ToolUniverse skills, build research workflows, or develop domain-specific analysis capabilities for biology, chemistry, or medicine.
Use when the user asks to implement FSD, use Feature-Sliced Design, organize architecture, structure project folders, set up FSD layers, create feature slices, refactor to FSD, or mentions feature slices, layered architecture, FSD methodology, views layer, entities layer, shared layer, Next.js with FSD. Provides comprehensive guidance for implementing Feature-Sliced Design (FSD v2.1) in Next.js applications. Optional monorepo (Turborepo) support - see references/monorepo.md.