Menu
SkillsMP a collecté 19 skills depuis derHaken/SuperAntigravity. Ouvrez un skill pour examiner sa source et ses détails.
Affichage de 19 skills collectés sur 19.
Use when adding new dependencies, deciding whether to update packages, running security audits on dependencies, evaluating library alternatives, or encountering outdated or vulnerable packages
Langue du texte source : anglais
Use when starting any conversation — establishes how to find and use skills, requiring skill check before ANY response including clarifying questions
Langue du texte source : anglais
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Langue du texte source : anglais
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Langue du texte source : anglais
Use when you have a spec or requirements for a multi-step task, before touching code
Langue du texte source : anglais
Use when a task requires interacting with a web browser — testing UI flows, verifying web app behavior, clicking through screens, reading live web content, or automating browser workflows in Google Antigravity
Langue du texte source : anglais
Use when executing implementation plans with independent tasks in the current session
Langue du texte source : anglais
Use when designing new systems or significant features, evaluating architectural trade-offs, choosing between structural approaches, or when a task requires understanding system-wide design before writing code
Langue du texte source : anglais
Use before implementing a feature or making significant changes to verify you have enough context and understanding to proceed — prevents wasted effort from proceeding with wrong assumptions
Langue du texte source : anglais
Use when a task requires gathering information from external sources, researching unfamiliar technologies, validating technical approaches, or answering questions that need current web knowledge before implementation
Langue du texte source : anglais
Use when reviewing code for vulnerabilities, implementing authentication or authorization, handling user input, storing sensitive data, or before any feature that touches security boundaries goes to production
Langue du texte source : anglais
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Langue du texte source : anglais
Use when implementing any feature or bugfix, before writing implementation code
Langue du texte source : anglais
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Langue du texte source : anglais
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Langue du texte source : anglais
Use when code is slow, resource-heavy, or needs optimization — before making any changes, after profiling reveals bottlenecks, or when designing performance-sensitive systems
Langue du texte source : anglais
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Langue du texte source : anglais
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Langue du texte source : anglais
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Langue du texte source : anglais