Discover Databases skills, compare source repositories and read the instructions for each workflow.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context. Use this when design is complete and you need detailed implementation tasks for engineers with zero codebase...
Create isolated git worktrees at bare repo root level
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check...
Use this skill to determine the correct data-testid selector for Playwright or end-to-end tests.
Use this skill every user want to create test plan.
Use this skill every user want to create test file.
Autonomous debugging workflow mirroring Cursor IDE's debug mode. Triggers on "debug mode", "help me debug", error messages, stack traces, or debugging loops. Generates 5-7 hypotheses, narrows to top 2, adds str...
Build and deploy this Next.js LangChain retrieval agent application with Supabase vector store. Use when building, deploying, setting up vector store, or preparing the project for production.
Build and deploy this Next.js LangChain agent application. Use when building, deploying, or preparing the project for production.
Know any codebase in 10 seconds. Scripts, tech stack, structure.
Task board for agents. Track work, manage cards across lists.
Edits that never fail. Find functions by name, not text matching.
See what breaks BEFORE you edit. Type errors, affected callers, required tests.
Understand code in one call. Structure, relationships, history - all at once.
Builds that don't die after 2 minutes. Tasks survive restarts.
Fast type checking for single files. Never hangs, always answers in
Know exactly what failed, where, and why. No output parsing.
Use when restoring previous file versions, querying file modification history, recovering from accidental edits, or understanding how blackbox flight recorder works for file snapshots and disaster recovery
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validatio...
Use when invalid data causes failures deep in execution, bypassing initial checks - adds validation at entry, business logic, and environment layers to make bugs structurally impossible
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
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure fir...
Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Skill tool before announcing usage, following brainstorming before coding, and creating TodoWri...
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.