108+ skills loaded
108+ ready-made SKILL.md files for Claude Code, Codex and other coding agents. Copy, download, ship.
Free forever, no account needed.
/01
Find a SKILL.md that matches your workflow.
/02
Save it to .claude/skills/ or your agent's skills folder.
/03
Your agent follows the instructions automatically.
What is a SKILL.md?
Each skill has a short name and description at the top, followed by instructions. When your agent hits a matching task, it loads the skill and follows the steps — like handing a new teammate your playbook.
Drop a SKILL.md into your agent's skills folder and it works instantly. No setup, no config.
Claude Code, Codex, Cursor, Gemini CLI and more all read the same Markdown format.
Every skill is written as clear, step-by-step instructions agents follow reliably.
Agents only read a skill when the task needs it, so your context stays clean and fast.
It's just Markdown. Tweak any skill to match your team's conventions in seconds.
Copy or download any skill. No account, no paywall, no tracking.
THE TOOLKIT
108 skills available
Review pull requests for bugs, security issues and style.
--- name: pr-reviewer description: Review pull requests for bugs, security issues and style. --- # PR Reviewer ## When to use Review pull requests for bugs, security issues and style. ## Instructions 1. Read the full diff before commenting. 2. Flag security issues first, then logic bugs, then style. 3. Suggest concrete code fixes, not vague advice.
Refactor code without changing behavior.
--- name: refactor-safely description: Refactor code without changing behavior. --- # Refactor Safely ## When to use Refactor code without changing behavior. ## Instructions 1. Ensure tests cover the code first. 2. Make small steps, run tests after each. 3. Never mix refactors with feature changes.
Find and fix performance bottlenecks.
--- name: perf-profiler description: Find and fix performance bottlenecks. --- # Perf Profiler ## When to use Find and fix performance bottlenecks. ## Instructions 1. Measure first: profile before optimizing. 2. Look for N+1 queries and wasted re-renders. 3. Verify the fix with a before/after benchmark.
Build and test regular expressions safely.
--- name: regex-builder description: Build and test regular expressions safely. --- # Regex Builder ## When to use Build and test regular expressions safely. ## Instructions 1. Ask for sample inputs and expected matches. 2. Prefer readable patterns over clever ones. 3. Always test against edge cases and empty input.
Find hardcoded strings and move them to locale files.
--- name: i18n-extractor description: Find hardcoded strings and move them to locale files. --- # i18n Extractor ## When to use Find hardcoded strings and move them to locale files. ## Instructions 1. Scan components for user-facing literals. 2. Use stable, namespaced keys. 3. Keep pluralization and interpolation intact.
Find and safely remove unused code.
--- name: dead-code-hunter description: Find and safely remove unused code. --- # Dead Code Hunter ## When to use Find and safely remove unused code. ## Instructions 1. Search for unreferenced exports and files. 2. Confirm no dynamic imports use the code. 3. Remove in small commits with tests green.
Migrate JavaScript files to TypeScript.
--- name: type-migrator description: Migrate JavaScript files to TypeScript. --- # Type Migrator ## When to use Migrate JavaScript files to TypeScript. ## Instructions 1. Start with leaf modules, then work upward. 2. Prefer inference over explicit any. 3. Fix strict-mode errors one file at a time.
Generate typed API clients from an OpenAPI spec.
--- name: api-client-gen description: Generate typed API clients from an OpenAPI spec. --- # API Client Generator ## When to use Generate typed API clients from an OpenAPI spec. ## Instructions 1. Read the spec and map endpoints to functions. 2. Generate request and response types. 3. Include error handling and retries.
Model complex UI logic as explicit state machines.
--- name: state-machine-designer description: Model complex UI logic as explicit state machines. --- # State Machine Designer ## When to use Model complex UI logic as explicit state machines. ## Instructions 1. List all states and transitions first. 2. Make impossible states unrepresentable. 3. Handle loading, error and empty states explicitly.
Extract reusable React hooks from components.
--- name: hook-extractor description: Extract reusable React hooks from components. --- # Hook Extractor ## When to use Extract reusable React hooks from components. ## Instructions 1. Identify stateful logic repeated across components. 2. Extract into a well-named custom hook. 3. Keep the hook pure and testable.
Add and improve error handling across the app.
--- name: error-boundary-audit description: Add and improve error handling across the app. --- # Error Boundary Audit ## When to use Add and improve error handling across the app. ## Instructions 1. Find unhandled promise rejections. 2. Add error boundaries around risky subtrees. 3. Log errors with useful context.
Upgrade dependencies without breaking the build.
--- name: dependency-upgrader description: Upgrade dependencies without breaking the build. --- # Dependency Upgrader ## When to use Upgrade dependencies without breaking the build. ## Instructions 1. Upgrade one major version at a time. 2. Read changelogs for breaking changes. 3. Run the full test suite after each step.
Split a large codebase into packages.
--- name: monorepo-splitter description: Split a large codebase into packages. --- # Monorepo Splitter ## When to use Split a large codebase into packages. ## Instructions 1. Draw the dependency graph first. 2. Extract leaf packages with no internal deps. 3. Keep a single source of truth for config.
Reduce JavaScript bundle size.
--- name: bundle-shrinker description: Reduce JavaScript bundle size. --- # Bundle Shrinker ## When to use Reduce JavaScript bundle size. ## Instructions 1. Analyze the bundle with a visualizer. 2. Replace heavy deps with lighter alternatives. 3. Code-split routes and lazy-load heavy components.
Modernize legacy CSS to current best practices.
--- name: css-modernizer description: Modernize legacy CSS to current best practices. --- # CSS Modernizer ## When to use Modernize legacy CSS to current best practices. ## Instructions 1. Replace floats with flexbox and grid. 2. Use custom properties for theming. 3. Remove vendor prefixes handled by build tools.
Build robust forms with validation.
--- name: form-builder description: Build robust forms with validation. --- # Form Builder ## When to use Build robust forms with validation. ## Instructions 1. Validate on blur, submit on valid only. 2. Show inline errors next to fields. 3. Handle async submission states.
Build data tables with sorting and filtering.
--- name: table-builder description: Build data tables with sorting and filtering. --- # Table Builder ## When to use Build data tables with sorting and filtering. ## Instructions 1. Keep sorting and filtering server-side when data is large. 2. Make columns resizable and reorderable. 3. Handle empty and loading states.
Build command-line tools with good UX.
--- name: cli-scaffolder description: Build command-line tools with good UX. --- # CLI Scaffolder ## When to use Build command-line tools with good UX. ## Instructions 1. Use clear subcommands and flags. 2. Print helpful errors with suggestions. 3. Support --help and --version.
Implement reliable realtime connections.
--- name: websocket-handler description: Implement reliable realtime connections. --- # WebSocket Handler ## When to use Implement reliable realtime connections. ## Instructions 1. Handle reconnects with backoff. 2. Buffer messages during disconnection. 3. Version your message protocol.
Design caching layers that stay correct.
--- name: cache-strategist description: Design caching layers that stay correct. --- # Cache Strategist ## When to use Design caching layers that stay correct. ## Instructions 1. Define invalidation rules before caching. 2. Cache at the highest layer possible. 3. Add cache headers and ETags.
Write focused unit tests for new or changed code.
--- name: test-writer description: Write focused unit tests for new or changed code. --- # Test Writer ## When to use Write focused unit tests for new or changed code. ## Instructions 1. Find the existing test framework and conventions. 2. Write one test per behavior with real values. 3. Run the tests and fix failures before finishing.
Reproduce and isolate reported bugs.
--- name: bug-triage description: Reproduce and isolate reported bugs. --- # Bug Triage ## When to use Reproduce and isolate reported bugs. ## Instructions 1. Reproduce the bug with minimal steps. 2. Write a failing test that captures it. 3. Fix the root cause, not the symptom.
Audit UI code for accessibility issues.
--- name: a11y-checker description: Audit UI code for accessibility issues. --- # A11y Checker ## When to use Audit UI code for accessibility issues. ## Instructions 1. Check labels, roles and keyboard navigation. 2. Verify color contrast ratios. 3. Test with a screen reader flow in mind.
Design end-to-end test scenarios for user flows.
--- name: e2e-scenarios description: Design end-to-end test scenarios for user flows. --- # E2E Scenarios ## When to use Design end-to-end test scenarios for user flows. ## Instructions 1. Map the happy path first, then failure modes. 2. Write scenarios in Given/When/Then form. 3. Keep each scenario independent and repeatable.
Measure real test quality with mutation testing.
--- name: mutation-tester description: Measure real test quality with mutation testing. --- # Mutation Tester ## When to use Measure real test quality with mutation testing. ## Instructions 1. Run mutation testing on critical modules. 2. Kill surviving mutants with better assertions. 3. Track mutation score over time.
Keep snapshot tests useful instead of noisy.
--- name: snapshot-guardian description: Keep snapshot tests useful instead of noisy. --- # Snapshot Guardian ## When to use Keep snapshot tests useful instead of noisy. ## Instructions 1. Review snapshot diffs like real code. 2. Keep snapshots small and focused. 3. Delete snapshots that never catch bugs.
Find and fix nondeterministic tests.
--- name: flaky-test-fixer description: Find and fix nondeterministic tests. --- # Flaky Test Fixer ## When to use Find and fix nondeterministic tests. ## Instructions 1. Run the suite repeatedly to find flakes. 2. Remove time and order dependencies. 3. Replace sleeps with explicit waits.
Test API contracts between services.
--- name: contract-tester description: Test API contracts between services. --- # Contract Tester ## When to use Test API contracts between services. ## Instructions 1. Define the contract from the provider spec. 2. Verify consumer expectations against it. 3. Fail CI on contract drift.
Design load tests that reflect real traffic.
--- name: load-test-designer description: Design load tests that reflect real traffic. --- # Load Test Designer ## When to use Design load tests that reflect real traffic. ## Instructions 1. Model realistic user journeys. 2. Ramp load gradually and watch error rates. 3. Test at 2x expected peak.
Use coverage data to find untested risk.
--- name: coverage-analyst description: Use coverage data to find untested risk. --- # Coverage Analyst ## When to use Use coverage data to find untested risk. ## Instructions 1. Look at branch coverage, not just lines. 2. Prioritize uncovered critical paths. 3. Never chase 100% for its own sake.
Catch unintended UI changes with screenshots.
--- name: visual-regression description: Catch unintended UI changes with screenshots. --- # Visual Regression ## When to use Catch unintended UI changes with screenshots. ## Instructions 1. Snapshot key pages in stable states. 2. Mask dynamic content like dates. 3. Review diffs before approving.
Fuzz parsers and input handling.
--- name: fuzz-tester description: Fuzz parsers and input handling. --- # Fuzz Tester ## When to use Fuzz parsers and input handling. ## Instructions 1. Generate malformed and boundary inputs. 2. Assert no crashes or hangs. 3. Save crashing inputs as regression tests.
Write clear conventional commit messages.
--- name: commit-messages description: Write clear conventional commit messages. --- # Commit Messages ## When to use Write clear conventional commit messages. ## Instructions 1. Use type(scope): summary under 72 chars. 2. Explain why in the body, not what. 3. Reference issue numbers when present.
Resolve merge conflicts without losing work.
--- name: git-conflict-resolver description: Resolve merge conflicts without losing work. --- # Conflict Resolver ## When to use Resolve merge conflicts without losing work. ## Instructions 1. Understand both sides before editing. 2. Prefer the newer intent, keep both changes when needed. 3. Run tests after resolving.
Design a branching model for the team.
--- name: branch-strategist description: Design a branching model for the team. --- # Branch Strategist ## When to use Design a branching model for the team. ## Instructions 1. Keep main always releasable. 2. Use short-lived feature branches. 3. Automate releases from tags.
Clean up commit history before merging.
--- name: history-rewriter description: Clean up commit history before merging. --- # History Rewriter ## When to use Clean up commit history before merging. ## Instructions 1. Squash fixup commits into logical units. 2. Never rewrite shared history. 3. Keep each commit buildable.
Tag and version releases consistently.
--- name: release-tagger description: Tag and version releases consistently. --- # Release Tagger ## When to use Tag and version releases consistently. ## Instructions 1. Use semantic versioning. 2. Tag from the release commit, not a branch. 3. Generate the changelog from commits.
Find the commit that introduced a bug.
--- name: bisect-detective description: Find the commit that introduced a bug. --- # Bisect Detective ## When to use Find the commit that introduced a bug. ## Instructions 1. Write a script that detects the bug. 2. Run git bisect with the script. 3. Read the offending diff carefully.
Merge repositories while preserving history.
--- name: monorepo-merger description: Merge repositories while preserving history. --- # Monorepo Merger ## When to use Merge repositories while preserving history. ## Instructions 1. Use git subtree or filter-repo. 2. Rewrite paths before merging. 3. Verify CI passes on the merged repo.
Generate Markdown docs for HTTP endpoints.
--- name: api-docs description: Generate Markdown docs for HTTP endpoints. --- # API Docs ## When to use Generate Markdown docs for HTTP endpoints. ## Instructions 1. List method, path, params and response. 2. Include one curl example per endpoint. 3. Document error codes.
Write user-friendly release notes from commits.
--- name: changelog-writer description: Write user-friendly release notes from commits. --- # Changelog Writer ## When to use Write user-friendly release notes from commits. ## Instructions 1. Group changes by Added, Fixed, Changed. 2. Write for users, not developers. 3. Link to relevant pull requests.
Explain unfamiliar code in plain language.
--- name: code-explainer description: Explain unfamiliar code in plain language. --- # Code Explainer ## When to use Explain unfamiliar code in plain language. ## Instructions 1. Start with what the code does, then how. 2. Trace one concrete example through the flow. 3. Call out non-obvious edge cases.
Write READMEs that get people running fast.
--- name: readme-writer description: Write READMEs that get people running fast. --- # README Writer ## When to use Write READMEs that get people running fast. ## Instructions 1. Lead with what the project does. 2. Include a copy-paste quickstart. 3. Document common errors and fixes.
Write architecture decision records.
--- name: adr-writer description: Write architecture decision records. --- # ADR Writer ## When to use Write architecture decision records. ## Instructions 1. State the context and constraints. 2. List alternatives considered. 3. Record the decision and consequences.
Write docs that get new devs productive fast.
--- name: onboarding-guide description: Write docs that get new devs productive fast. --- # Onboarding Guide ## When to use Write docs that get new devs productive fast. ## Instructions 1. List every setup step, tested on a clean machine. 2. Explain the architecture in one diagram. 3. Point to the first good issues.
Write operational runbooks for incidents.
--- name: runbook-writer description: Write operational runbooks for incidents. --- # Runbook Writer ## When to use Write operational runbooks for incidents. ## Instructions 1. Start with symptoms and detection. 2. Give exact commands to diagnose. 3. Include rollback and escalation steps.
Build a shared vocabulary for the codebase.
--- name: glossary-builder description: Build a shared vocabulary for the codebase. --- # Glossary Builder ## When to use Build a shared vocabulary for the codebase. ## Instructions 1. Define domain terms as the team uses them. 2. Link terms to the code that implements them. 3. Keep it short and searchable.
Write step-by-step tutorials that work.
--- name: tutorial-writer description: Write step-by-step tutorials that work. --- # Tutorial Writer ## When to use Write step-by-step tutorials that work. ## Instructions 1. Test every step on a fresh environment. 2. Show expected output after each step. 3. End with a working complete example.
Migrate docs between platforms or formats.
--- name: doc-migrator description: Migrate docs between platforms or formats. --- # Docs Migrator ## When to use Migrate docs between platforms or formats. ## Instructions 1. Inventory all existing pages first. 2. Preserve links with redirects. 3. Verify code samples still run.
Write safe, reversible database migrations.
--- name: sql-migrations description: Write safe, reversible database migrations. --- # SQL Migrations ## When to use Write safe, reversible database migrations. ## Instructions 1. Avoid locking large tables. 2. Add columns as nullable first, backfill, then constrain. 3. Always include a down migration.
Recommend indexes from slow query patterns.
--- name: db-index-advisor description: Recommend indexes from slow query patterns. --- # DB Index Advisor ## When to use Recommend indexes from slow query patterns. ## Instructions 1. Inspect the query plan first. 2. Index columns used in WHERE, JOIN and ORDER BY. 3. Warn about write amplification from too many indexes.
Generate realistic seed data for development.
--- name: seed-data description: Generate realistic seed data for development. --- # Seed Data ## When to use Generate realistic seed data for development. ## Instructions 1. Match the production schema and constraints. 2. Use believable names, dates and values. 3. Include edge cases: empty, long, and unicode values.
Rewrite slow SQL queries for speed.
--- name: query-optimizer description: Rewrite slow SQL queries for speed. --- # Query Optimizer ## When to use Rewrite slow SQL queries for speed. ## Instructions 1. Read the execution plan first. 2. Replace correlated subqueries with joins. 3. Verify results are identical before and after.
Design normalized database schemas.
--- name: schema-designer description: Design normalized database schemas. --- # Schema Designer ## When to use Design normalized database schemas. ## Instructions 1. Model entities and relationships first. 2. Normalize to 3NF, denormalize deliberately. 3. Name tables and columns consistently.
Build reliable data pipelines.
--- name: data-pipeline-builder description: Build reliable data pipelines. --- # Pipeline Builder ## When to use Build reliable data pipelines. ## Instructions 1. Make every step idempotent. 2. Validate data at each stage. 3. Alert on failures with context.
Clean and validate messy CSV imports.
--- name: csv-cleaner description: Clean and validate messy CSV imports. --- # CSV Cleaner ## When to use Clean and validate messy CSV imports. ## Instructions 1. Detect encoding and delimiter issues. 2. Validate types and required columns. 3. Report rejected rows with reasons.
Debug broken data pipelines.
--- name: etl-debugger description: Debug broken data pipelines. --- # ETL Debugger ## When to use Debug broken data pipelines. ## Instructions 1. Find the first stage with bad output. 2. Compare row counts between stages. 3. Check for schema drift upstream.
Verify backups actually restore.
--- name: backup-verifier description: Verify backups actually restore. --- # Backup Verifier ## When to use Verify backups actually restore. ## Instructions 1. Restore to a scratch environment regularly. 2. Verify row counts and checksums. 3. Document the restore procedure.
Anonymize production data for dev use.
--- name: anonymizer description: Anonymize production data for dev use. --- # Data Anonymizer ## When to use Anonymize production data for dev use. ## Instructions 1. Identify all PII columns. 2. Replace with realistic fake values. 3. Keep referential integrity intact.
Run a pre-deploy checklist before shipping.
--- name: deploy-checklist description: Run a pre-deploy checklist before shipping. --- # Deploy Checklist ## When to use Run a pre-deploy checklist before shipping. ## Instructions 1. Confirm CI is green. 2. Check env vars exist in production. 3. Prepare a rollback plan.
Shrink and harden Docker images.
--- name: docker-optimizer description: Shrink and harden Docker images. --- # Docker Optimizer ## When to use Shrink and harden Docker images. ## Instructions 1. Use multi-stage builds and slim base images. 2. Order layers for maximum cache hits. 3. Run as a non-root user.
Diagnose and fix failing CI pipelines.
--- name: ci-fixer description: Diagnose and fix failing CI pipelines. --- # CI Fixer ## When to use Diagnose and fix failing CI pipelines. ## Instructions 1. Read the full failure log before changing anything. 2. Reproduce the failure locally when possible. 3. Fix the cause, not just the red checkmark.
Debug Kubernetes workload issues.
--- name: k8s-troubleshooter description: Debug Kubernetes workload issues. --- # K8s Troubleshooter ## When to use Debug Kubernetes workload issues. ## Instructions 1. Check pod status and events first. 2. Read logs from the failing container. 3. Verify resource limits and probes.
Review infrastructure-as-code changes.
--- name: terraform-reviewer description: Review infrastructure-as-code changes. --- # Terraform Reviewer ## When to use Review infrastructure-as-code changes. ## Instructions 1. Read the plan output, not just the diff. 2. Flag destructive changes loudly. 3. Check state impacts and drift.
Find root causes in application logs.
--- name: log-investigator description: Find root causes in application logs. --- # Log Investigator ## When to use Find root causes in application logs. ## Instructions 1. Start from the error timestamp and work backward. 2. Correlate request IDs across services. 3. Distinguish symptoms from causes.
Rotate credentials without downtime.
--- name: secret-rotator description: Rotate credentials without downtime. --- # Secret Rotator ## When to use Rotate credentials without downtime. ## Instructions 1. Support overlapping old and new credentials. 2. Update consumers before revoking. 3. Audit access after rotation.
Set up monitoring and alerting that matters.
--- name: uptime-monitor description: Set up monitoring and alerting that matters. --- # Uptime Monitor ## When to use Set up monitoring and alerting that matters. ## Instructions 1. Alert on user impact, not noise. 2. Set SLOs before thresholds. 3. Test alerts actually fire.
Respond to production incidents calmly.
--- name: incident-responder description: Respond to production incidents calmly. --- # Incident Responder ## When to use Respond to production incidents calmly. ## Instructions 1. Mitigate first, investigate second. 2. Communicate status early and often. 3. Write a blameless postmortem.
Reduce cloud spend without hurting reliability.
--- name: cost-optimizer description: Reduce cloud spend without hurting reliability. --- # Cloud Cost Optimizer ## When to use Reduce cloud spend without hurting reliability. ## Instructions 1. Find idle and oversized resources. 2. Use spot instances for fault-tolerant work. 3. Set budget alerts per service.
Keep dev, staging and prod in sync.
--- name: env-parity-checker description: Keep dev, staging and prod in sync. --- # Env Parity Checker ## When to use Keep dev, staging and prod in sync. ## Instructions 1. Diff env vars and config across environments. 2. Version infrastructure as code. 3. Fail deploys on missing config.
Plan safe rollbacks for every deploy.
--- name: rollback-planner description: Plan safe rollbacks for every deploy. --- # Rollback Planner ## When to use Plan safe rollbacks for every deploy. ## Instructions 1. Make deploys reversible by default. 2. Keep database changes backward compatible. 3. Practice the rollback before you need it.
Scan code for common vulnerabilities and leaks.
--- name: security-audit description: Scan code for common vulnerabilities and leaks. --- # Security Audit ## When to use Scan code for common vulnerabilities and leaks. ## Instructions 1. Check for hardcoded secrets and tokens. 2. Review auth checks on every route and query. 3. Flag injection, XSS and unsafe deserialization.
Review authentication and session handling.
--- name: auth-reviewer description: Review authentication and session handling. --- # Auth Reviewer ## When to use Review authentication and session handling. ## Instructions 1. Check token storage and expiry. 2. Verify password hashing is modern. 3. Test logout and session invalidation.
Audit dependencies for known vulnerabilities.
--- name: dependency-auditor description: Audit dependencies for known vulnerabilities. --- # Dependency Auditor ## When to use Audit dependencies for known vulnerabilities. ## Instructions 1. Run the package auditor and read each advisory. 2. Upgrade or patch affected packages. 3. Check transitive dependencies too.
Validate all external input at the boundary.
--- name: input-validator description: Validate all external input at the boundary. --- # Input Validator ## When to use Validate all external input at the boundary. ## Instructions 1. Validate type, length and format. 2. Reject unknown fields by default. 3. Never trust client-side validation alone.
Configure CORS without opening holes.
--- name: cors-configurer description: Configure CORS without opening holes. --- # CORS Configurer ## When to use Configure CORS without opening holes. ## Instructions 1. Allow specific origins, never wildcard with credentials. 2. Limit methods and headers. 3. Test preflight behavior.
Add rate limiting to sensitive endpoints.
--- name: rate-limiter description: Add rate limiting to sensitive endpoints. --- # Rate Limiter ## When to use Add rate limiting to sensitive endpoints. ## Instructions 1. Limit by user and by IP. 2. Return clear 429 responses with retry hints. 3. Protect login and signup hardest.
Find leaked secrets in code and history.
--- name: secrets-scanner description: Find leaked secrets in code and history. --- # Secrets Scanner ## When to use Find leaked secrets in code and history. ## Instructions 1. Scan the working tree and git history. 2. Rotate any secret that ever shipped. 3. Add pre-commit scanning.
Set secure HTTP headers everywhere.
--- name: headers-hardening description: Set secure HTTP headers everywhere. --- # Headers Hardening ## When to use Set secure HTTP headers everywhere. ## Instructions 1. Add CSP, HSTS and X-Content-Type-Options. 2. Remove server version headers. 3. Test with a security header scanner.
Find and fix cross-site scripting risks.
--- name: xss-hunter description: Find and fix cross-site scripting risks. --- # XSS Hunter ## When to use Find and fix cross-site scripting risks. ## Instructions 1. Audit every place user input reaches the DOM. 2. Use framework escaping, avoid dangerouslySetInnerHTML. 3. Add a strict Content Security Policy.
Eliminate SQL injection risks.
--- name: sql-injection-guard description: Eliminate SQL injection risks. --- # SQL Injection Guard ## When to use Eliminate SQL injection risks. ## Instructions 1. Use parameterized queries everywhere. 2. Audit raw SQL and string concatenation. 3. Add tests with malicious input.
Write reliable prompts for LLM features.
--- name: prompt-engineer description: Write reliable prompts for LLM features. --- # Prompt Engineer ## When to use Write reliable prompts for LLM features. ## Instructions 1. State the task, constraints and output format. 2. Include few-shot examples for structure. 3. Test with adversarial inputs.
Build retrieval-augmented generation pipelines.
--- name: rag-builder description: Build retrieval-augmented generation pipelines. --- # RAG Builder ## When to use Build retrieval-augmented generation pipelines. ## Instructions 1. Chunk documents with overlap. 2. Embed and index with metadata. 3. Cite sources in every answer.
Design evaluations for AI features.
--- name: eval-designer description: Design evaluations for AI features. --- # Eval Designer ## When to use Design evaluations for AI features. ## Instructions 1. Build a golden dataset from real cases. 2. Measure accuracy, latency and cost. 3. Fail CI on regressions.
Design multi-step agent workflows.
--- name: agent-designer description: Design multi-step agent workflows. --- # Agent Designer ## When to use Design multi-step agent workflows. ## Instructions 1. Give the agent few, sharp tools. 2. Bound loops with step limits. 3. Log every tool call for debugging.
Keep LLM context small and relevant.
--- name: context-optimizer description: Keep LLM context small and relevant. --- # Context Optimizer ## When to use Keep LLM context small and relevant. ## Instructions 1. Send only what the task needs. 2. Summarize long history. 3. Truncate deterministically, not randomly.
Add safety guardrails to AI outputs.
--- name: guardrail-builder description: Add safety guardrails to AI outputs. --- # Guardrail Builder ## When to use Add safety guardrails to AI outputs. ## Instructions 1. Validate output schema before use. 2. Filter PII and unsafe content. 3. Fall back gracefully on refusal.
Build semantic search with embeddings.
--- name: embedding-search description: Build semantic search with embeddings. --- # Embedding Search ## When to use Build semantic search with embeddings. ## Instructions 1. Pick an embedding model for your domain. 2. Normalize and store vectors with metadata. 3. Combine with keyword search for recall.
Track and reduce LLM spending.
--- name: llm-cost-tracker description: Track and reduce LLM spending. --- # LLM Cost Tracker ## When to use Track and reduce LLM spending. ## Instructions 1. Log tokens and cost per request. 2. Cache repeated queries. 3. Route simple tasks to smaller models.
Audit UI for design system consistency.
--- name: design-system-audit description: Audit UI for design system consistency. --- # Design System Audit ## When to use Audit UI for design system consistency. ## Instructions 1. List every color, spacing and font value in use. 2. Map outliers to the nearest token. 3. Flag one-off components for consolidation.
Add dark mode without breaking themes.
--- name: dark-mode-implementer description: Add dark mode without breaking themes. --- # Dark Mode Implementer ## When to use Add dark mode without breaking themes. ## Instructions 1. Use semantic tokens, never hardcoded colors. 2. Test every screen in both modes. 3. Respect the system preference by default.
Add purposeful animation to UI.
--- name: motion-designer description: Add purposeful animation to UI. --- # Motion Designer ## When to use Add purposeful animation to UI. ## Instructions 1. Animate only state changes and attention. 2. Keep durations under 300ms for UI. 3. Respect prefers-reduced-motion.
Fix layouts that break on small screens.
--- name: responsive-fixer description: Fix layouts that break on small screens. --- # Responsive Fixer ## When to use Fix layouts that break on small screens. ## Instructions 1. Test at 320px first. 2. Use fluid type and spacing. 3. Stack before you shrink.
Make icon usage consistent across the app.
--- name: icon-consistency description: Make icon usage consistent across the app. --- # Icon Consistency ## When to use Make icon usage consistent across the app. ## Instructions 1. Pick one icon set and stick to it. 2. Match stroke width and size. 3. Use semantic names for icons.
Design helpful empty and error states.
--- name: empty-state-designer description: Design helpful empty and error states. --- # Empty State Designer ## When to use Design helpful empty and error states. ## Instructions 1. Explain why the state is empty. 2. Offer one clear next action. 3. Keep the tone helpful, not cute.
Write clear feature specifications.
--- name: feature-spec-writer description: Write clear feature specifications. --- # Feature Spec Writer ## When to use Write clear feature specifications. ## Instructions 1. Start with the user problem. 2. Define acceptance criteria. 3. List what is explicitly out of scope.
Break features into user stories.
--- name: user-story-mapper description: Break features into user stories. --- # User Story Mapper ## When to use Break features into user stories. ## Instructions 1. Write stories as user goals. 2. Slice vertically, not by layer. 3. Prioritize by user value.
Define metrics for a feature launch.
--- name: metrics-designer description: Define metrics for a feature launch. --- # Metrics Designer ## When to use Define metrics for a feature launch. ## Instructions 1. Pick one north-star metric. 2. Add guardrail metrics. 3. Instrument before launch.
Turn user feedback into themes.
--- name: feedback-synthesizer description: Turn user feedback into themes. --- # Feedback Synthesizer ## When to use Turn user feedback into themes. ## Instructions 1. Group feedback by underlying need. 2. Count frequency but weight by impact. 3. Quote users verbatim.
Plan a realistic product roadmap.
--- name: roadmap-planner description: Plan a realistic product roadmap. --- # Roadmap Planner ## When to use Plan a realistic product roadmap. ## Instructions 1. Sequence by dependency, not desire. 2. Leave buffer for unknowns. 3. Review and adjust monthly.
Debug React Native issues across platforms.
--- name: rn-debugger description: Debug React Native issues across platforms. --- # RN Debugger ## When to use Debug React Native issues across platforms. ## Instructions 1. Reproduce on both iOS and Android. 2. Check native logs, not just JS console. 3. Isolate bridge vs JS issues.
Prepare an app for store submission.
--- name: app-store-checklist description: Prepare an app for store submission. --- # App Store Checklist ## When to use Prepare an app for store submission. ## Instructions 1. Verify screenshots and metadata. 2. Test on the minimum supported OS. 3. Complete privacy declarations.
Make apps work without a connection.
--- name: offline-first description: Make apps work without a connection. --- # Offline First ## When to use Make apps work without a connection. ## Instructions 1. Queue mutations locally. 2. Sync with conflict resolution. 3. Show connectivity state honestly.
Implement push notifications end to end.
--- name: push-notification-setup description: Implement push notifications end to end. --- # Push Notifications ## When to use Implement push notifications end to end. ## Instructions 1. Request permission at the right moment. 2. Handle tokens and refresh. 3. Deep-link notifications into the app.
Review smart contracts for common bugs.
--- name: contract-reviewer description: Review smart contracts for common bugs. --- # Contract Reviewer ## When to use Review smart contracts for common bugs. ## Instructions 1. Check reentrancy and access control. 2. Verify arithmetic and overflow handling. 3. Review external call ordering.
Reduce smart contract gas costs.
--- name: gas-optimizer description: Reduce smart contract gas costs. --- # Gas Optimizer ## When to use Reduce smart contract gas costs. ## Instructions 1. Pack storage slots. 2. Prefer calldata over memory. 3. Cache storage reads in memory.
Integrate token transfers into an app.
--- name: token-integrator description: Integrate token transfers into an app. --- # Token Integrator ## When to use Integrate token transfers into an app. ## Instructions 1. Handle decimals correctly. 2. Check allowances before transfers. 3. Listen for confirmation events.
Build a smooth wallet connection flow.
--- name: wallet-connect-flow description: Build a smooth wallet connection flow. --- # Wallet Connect Flow ## When to use Build a smooth wallet connection flow. ## Instructions 1. Support multiple wallet providers. 2. Handle chain switching gracefully. 3. Show connection state clearly.