knowledge-base
0
requirements-analysis
Diagnose requirements problems and guide discovery of real needs and constraints
jwynia
documentation
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
knowledge-base
0
curriculum-design
Write measurable learning objectives using Bloom's Taxonomy and design curriculum architecture with scope, sequence, and assessment blueprints. Use when creating learning objectives, designing unit structure, or planning curriculum flow. Activates on "write learning objectives", "design curriculum", "create scope and sequence", or "Bloom's taxonomy objectives".
pauljbernard
documentation
knowledge-base
0
interview
This skill should be used when the user asks to "interview me about the plan", "validate my implementation plan", "review my design decisions", "question my architecture choices", or when finishing plan mode before implementation. Conducts deep technical interviews to validate plans and produce specifications.
VinniZP
documentation
knowledge-base
0
deep-reasoning
This skill should be used when users need to think through a complex analytical decision, asks 'how should I approach this?' or 'help me think through...', is stuck on a difficult coding boundary, needs to plan dimensional analysis, or is building theoretical frameworks in Stage 3.
linxule
documentation
knowledge-base
0
sequential-thinking
Apply structured, reflective problem-solving for complex tasks requiring multi-step analysis, revision capability, and hypothesis verification. Use for complex problem decomposition, adaptive planning, analysis needing course correction, problems with unclear scope, multi-step solutions, and hypothesis-driven work.
untangledfinance
documentation
knowledge-base
0
gioia-methodology
This skill should be used when users are building or refining their Gioia data structure, mentions 'Gioia', 'data structure', 'themes', 'concepts', 'dimensions', '1st-order', '2nd-order', 'aggregate', or needs to validate/export their analytical hierarchy for publication.
linxule
documentation
knowledge-base
0
ultra-think
Advanced analytical framework for deep problem solving and multi-dimensional thinking. Systematically analyzes complex problems from technical, business, user, and system perspectives to generate comprehensive solutions with structured recommendations.
merllinsbeard
documentation
knowledge-base
0
market-researcher
Market research for companies, competitors, contacts, and technologies.
robynnai
documentation
knowledge-base
0
ui-ux-polisher
Systematically audit, analyze, and enhance UI/UX quality with visual analysis, interactive suggestions, and user-approved improvements. Use when user mentions: UI polish, menu alignment, responsiveness, animations, professional look, accessibility fixes, design improvements.
sajid-khan-afridi
documentation
knowledge-base
0
explore-ux
Explore interaction design, user flows, and information architecture. Use when exploring "how should users interact with this?" or "what's the best way to organize this information?"
dthompson-jti
documentation
knowledge-base
0
architecture-designer
Software architect for system design, patterns, and architectural decisions. Invoke for system design, architecture review, design patterns, ADRs, scalability planning. Keywords: architecture, system design, patterns, microservices, scalability.
franroa
documentation
knowledge-base
0
reflective-brainstorming
This skill should be used when the user needs structured thinking frameworks to analyze decisions, problems, or tasks. Apply multiple decision-making methodologies (10/10/10, 5 Whys, Eisenhower Matrix, First Principles, Inversion, Occam's Razor, The One Thing, Opportunity Cost, Pareto, Second-Order Thinking, SWOT, Via Negativa) to ask probing questions and guide deep reflection. Use when the user asks to "think through", "analyze", "evaluate", "reflect on", or "brainstorm" decisions or problems.
Git-Fg
documentation
knowledge-base
0
hypothesis-driven
This skill should be used when refining hypotheses, checking testability, improving specificity, or designing verification strategies. Triggered by requests like "refine hypothesis", "validate hypothesis", "check if testable", or "improve this hypothesis". Used AFTER experiments to refine hypotheses based on results.
dakesan
documentation
knowledge-base
0
001-scope-project
Comprehensive project scoping through iterative discovery. Guides users through structured questioning phases to capture every detail needed for software work — whether building new products, adding features, auditing security, optimizing performance, fixing bugs, or migrating systems. Use when user wants to plan any software project or needs help structuring requirements before implementation.
PaulCrossland1
documentation
knowledge-base
0
specification-phase
Provides standard operating procedures for the /specify phase including feature classification (HAS_UI, IS_IMPROVEMENT, HAS_METRICS, HAS_DEPLOYMENT_IMPACT), research depth determination, clarification strategy (max 3, informed guesses for defaults), and roadmap integration. Use when executing /specify command, classifying features, generating structured specs, or determining research depth for planning phase. (project)
Sjdjdiejdrirhdkjej
documentation
knowledge-base
0
mental-models
Load when user says "mental model", "think through this", "structured thinking", "help me decide", "analyze this problem", "first principles", "pre-mortem", "stakeholder mapping", "what framework should I use", or any specific model name. Provides 59 thinking frameworks for decision-making, problem decomposition, and strategic analysis.
abdullahbeam
documentation
knowledge-base
0
reasoning-first-principles
First principles reasoning and optimization methodology. Applies the Idiot Index, requirement questioning, and 5-step optimization process (question, delete, simplify, accelerate, automate). Triggers on problem-solving, decision-making, evaluating requirements, planning features, how should we approach, help me think through, what is the best way to.
Dispo-Genius
documentation
knowledge-base
0
system-reviewer
Review the skill development ecosystem itself - assess ecosystem health, identify systemic issues, evaluate toolkit effectiveness, and recommend system-level improvements. Task-based operations for ecosystem assessment, toolkit evaluation, process review, and system optimization. Use when evaluating ecosystem health, identifying systemic improvements, optimizing the toolkit itself, or conducting meta-level ecosystem reviews.
adaptationio
documentation