GitHub
husky
Generates Husky Git hooks configuration with pre-commit checks. Creates .husky/pre-commit file for running linting, testing, and formatting before commits.
☆ 0View skill
DevOps AI Skills
Discover DevOps skills, compare source repositories and read the instructions for each workflow.
Categories: DevOps
DevOps Clear filters
Browse skills
GitHub
theme
Generates SCSS theme files in src/theme/ including vars.scss, shadow.scss, and index.scss with sample variables and mixins for styling.
☆ 0View skill
GitHub
debug-standard
Systematic root cause analysis for reproducible bugs. Use when you have a bug that can be reproduced.
☆ 0View skill
GitHub
audit-docs
Documentation drift detection and knowledge-base hygiene. Use to ensure docs match implementation.
☆ 0View skill
GitHub
implement-feature
Full feature implementation from an approved plan. Use when you have an implementation_plan.md and are ready to build.
☆ 0View skill
GitHub
research-deep
Conduct deep research on a topic using web search and analysis. Use when you need comprehensive understanding of a topic.
☆ 0View skill
GitHub
explore-ui-design
Visual design exploration (layout, color, typography, component composition). Use when exploring "how should this look?" or "what visual treatment should we use?"
☆ 0View skill
GitHub
audit-accessibility
WCAG 2.1 AA accessibility audit. Use to ensure the application is accessible to all users.
☆ 0View skill
GitHub
implement-refactor
Code restructuring without behavior change. Use when improving code organization while preserving functionality.
☆ 0View skill
GitHub
plan-prd
Create a Product Requirements Document (PRD) with user stories, state matrix, and accessibility requirements. Use for large features requiring full UX specification.
☆ 0View skill
GitHub
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?"
☆ 0View skill
GitHub
plan-feature
Create a lightweight implementation plan for medium-scope features (1-5 files). Use when you need a plan but not a full PRD.
☆ 0View skill
GitHub
audit-design-system
Review adherence to design system (tokens, components, theming). Use to ensure consistency with SPEC files.
☆ 0View skill
GitHub
implement-quick-fix
Atomic code changes for small fixes (≤30 lines, ≤5 files). Use for bug fixes, minor tweaks, and small improvements.
☆ 0View skill
GitHub
audit-code
Technical code review (architecture, type safety, patterns). Use for pre-merge review or general code quality audit.
☆ 0View skill
GitHub
research-synthesize
Apply external research findings to project context. Use when you have research documents and need to map them to actionable recommendations.
☆ 0View skill
GitHub
explore-concept
Broad ideation and problem definition using Socratic questioning. Use for early-stage exploration when the problem isn't well-defined.
☆ 0View skill
GitHub
audit-layout
Review layout consistency (spacing, alignment, grid usage). Use to ensure visual consistency across components.
☆ 0View skill
GitHub
audit-performance
Performance analysis and optimization opportunities. Use when application feels slow or before optimization work.
☆ 0View skill
GitHub
debug-deep
Tree-of-thoughts reasoning for elusive, intermittent bugs. Use when standard debugging fails or the bug is hard to reproduce.
☆ 0View skill
GitHub
audit-refactor-opportunities
Identify code smells and refactoring opportunities without fixing. Use for tech debt assessment.
☆ 0View skill
GitHub
plan-architecture
Create technical architecture specification with data models, component hierarchy, and risk analysis. Use after PRD approval for large features.
☆ 0View skill
GitHub
explore-tech
Evaluate technical options (libraries, architecture patterns, performance tradeoffs). Use when exploring "how should we build this?" or "what library/approach should we use?"
☆ 0View skill
GitHub
audit-typography
Review typography consistency and usability. Use to ensure readable, consistent text styling.
☆ 0View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.