Explorar skills

Defines context handover format when workers hit turn limit. Posts structured handover to GitHub issue comments enabling replacement workers to continue seamlessly.

Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification

Use before code review - determine if change is minor (review new code only) or major (review impacted code too)

Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language

PR validity analysis: fetch PR diff, extract new code additions, search existing codebase for duplicate or overlapping implementations, classify changes, and create a structured GitHub issue.

Use when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full issue-driven-development process

Security scan: dependency audits, SAST analysis, and secret detection. Detects project type, runs available security tools, classifies findings by severity, and creates a structured GitHub issue.

Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary

Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base

Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields