juanmhidalgo/claude-plugins
18 skills
$npx skills add juanmhidalgo/claude-pluginsSkillInstalls
api-change-documentationUse when generating cross-team API handoff prompts to communicate changes between frontend and backend teams.api-designUse when designing new API endpoints, defining module boundaries, or establishing contracts between teams.branch-reviewUse when reviewing branch changes or PRs for merge readiness with severity classification. Do NOT use for general code quality advice — use dedicated linters.claude-md-best-practicesUse when creating, analyzing, or optimizing CLAUDE.md files for Claude Code projects. Do NOT use for general prompt engineering or non-CLAUDE.md configuration.coverage-gateUse when checking code coverage against CI-configured thresholds before pushing or during pipeline execution.debugging-strategiesUse when tests fail, builds break, or behavior doesn't match expectations. Covers triage methodology and regression guards.fixUse when the user provides a GitHub Issue URL and wants it fixed in the current repo.incident-responseUse to run an incident response workflow — initial triage, status updates during, blameless postmortem after.performance-optimizationUse when performance requirements exist, profiling reveals bottlenecks, or Core Web Vitals need improvement.prd-best-practicesUse when writing PRDs, defining acceptance criteria, or structuring product requirements with observable-behavior focus.receiving-code-reviewUse when receiving code review feedback to verify suggestions before accepting or pushing back.review-fixes-planUse when generating or managing a REVIEW_FIXES.md tracking document after a code review session.second-opinionUse when the user wants a second opinion from another AI (Codex, Gemini, Copilot, Claude) on code or architecture. Read-only consultation — does not write code.security-hardeningUse when writing code that handles user input, auth, sessions, or external data. Covers OWASP prevention patterns.shipUse when ready to ship code to remote — handles direct push to main and PR-based feature branch flows.spec-driven-developmentUse when starting a new feature or significant change with no spec yet. Covers single-repo and multi-repo features.tdd-patternsUse when executing TDD cycles with coverage gates and quality checks. Do NOT use for general testing advice or test writing without the full TDD cycle.technical-decisionsUse when multiple implementation approaches exist during code review and a decision must be made.