debug-standard
Systematic root cause analysis for reproducible bugs. Use when you have a bug that can be reproduced.
Explorez les skills IA publiés de dthompson-jti et consultez leurs instructions source.
Skills indexés
22Étoiles des dépôts des skills indexés
0Forks du dépôt
0Moyenne des étoiles par skill indexé
0Les étoiles d’un dépôt peuvent se répéter entre ses skills.
Systematic root cause analysis for reproducible bugs. Use when you have a bug that can be reproduced.
Documentation drift detection and knowledge-base hygiene. Use to ensure docs match implementation.
Full feature implementation from an approved plan. Use when you have an implementation_plan.md and are ready to build.
Conduct deep research on a topic using web search and analysis. Use when you need comprehensive understanding of a topic.
Visual design exploration (layout, color, typography, component composition). Use when exploring "how should this look?" or "what visual treatment should we use?"
WCAG 2.1 AA accessibility audit. Use to ensure the application is accessible to all users.
Code restructuring without behavior change. Use when improving code organization while preserving functionality.
Create a Product Requirements Document (PRD) with user stories, state matrix, and accessibility requirements. Use for large features requiring full UX specification.
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?"
Create a lightweight implementation plan for medium-scope features (1-5 files). Use when you need a plan but not a full PRD.
Review adherence to design system (tokens, components, theming). Use to ensure consistency with SPEC files.
Atomic code changes for small fixes (≤30 lines, ≤5 files). Use for bug fixes, minor tweaks, and small improvements.
Technical code review (architecture, type safety, patterns). Use for pre-merge review or general code quality audit.
Apply external research findings to project context. Use when you have research documents and need to map them to actionable recommendations.
Broad ideation and problem definition using Socratic questioning. Use for early-stage exploration when the problem isn't well-defined.
Review layout consistency (spacing, alignment, grid usage). Use to ensure visual consistency across components.
Performance analysis and optimization opportunities. Use when application feels slow or before optimization work.
Tree-of-thoughts reasoning for elusive, intermittent bugs. Use when standard debugging fails or the bug is hard to reproduce.
Identify code smells and refactoring opportunities without fixing. Use for tech debt assessment.
Create technical architecture specification with data models, component hierarchy, and risk analysis. Use after PRD approval for large features.
Evaluate technical options (libraries, architecture patterns, performance tradeoffs). Use when exploring "how should we build this?" or "what library/approach should we use?"
Review typography consistency and usability. Use to ensure readable, consistent text styling.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.