Loading...
Loading...
Found 9,934 Skills
Scan skills to extract cross-cutting principles and distill them into rules — append, revise, or create new rule files
Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.
Build node-based editors, interactive diagrams, and flow visualizations using Svelte Flow. Use when creating workflow editors, data flow diagrams, organizational charts, mindmaps, process visualizations, DAG editors, or any interactive node-graph UI. Supports custom nodes/edges, layouts (dagre, hierarchical), animations, and advanced features like proximity connect, floating edges, and contextual zoom.
Angular SSR with @angular/ssr, hydration, and prerendering. Covers server-side rendering setup, transfer state, and deployment. USE WHEN: user mentions "Angular SSR", "server-side rendering", "Angular Universal", "@angular/ssr", "hydration", "prerendering", "Angular SEO" DO NOT USE FOR: Next.js SSR - use `nextjs`, Nuxt SSR - use `vue-composition`, SvelteKit SSR - use `svelte`
REST Assured Java library for testing REST APIs. Covers HTTP requests, JSON/XML validation, and Spring Boot integration. USE WHEN: user mentions "rest assured", "api test java", "rest api test", asks about "given when then", "RestAssured", "HTTP test", "JSON validation" DO NOT USE FOR: Unit tests - use `junit`; E2E browser tests - use Selenium; WebSocket testing - use dedicated tools; Non-Java projects - use language-specific HTTP clients
Schema.org structured data audit and generation optimized for AI discoverability — detect, validate, and generate JSON-LD markup
Deterministic 4-phase documentation drift detector: Scan, Cross-Reference, Detect, Report. Use when skills/agents/commands are added, removed, or renamed, when README files seem outdated, or before committing documentation changes. Use for "check docs", "sync README", "documentation audit", or "stale entries". Do NOT use for writing documentation content, improving descriptions, or generating new README files.
Statistical rule discovery through measurement of Go codebases: Count patterns, derive confidence-scored rules, produce Style Vector fingerprint. Use when analyzing codebase conventions, extracting implicit coding rules, profiling a repo before onboarding or PR automation. Use for "analyze codebase", "find coding patterns", "what conventions does this repo use", "extract rules", or "codebase DNA". Do NOT use for code review, bug fixes, refactoring, or performance optimization.
Deterministic 3-phase GitHub PR review comment extraction: Authenticate, Mine, Validate. Use when mining tribal knowledge from PR reviews, extracting coding standards from review history, or building datasets for the Code Archaeologist agent. Use for "mine PRs", "extract review comments", "tribal knowledge", or "PR review history". Do NOT use for analyzing patterns, generating rules, or interpreting comments — that is the Code Archaeologist agent's responsibility.
Persistent markdown files as working memory for complex tasks: plan, track progress, store findings. Use when tasks have 3+ phases, require research, span many tool calls, or risk context drift. Use for "plan", "break down", "track progress", "multi-step", or complex tasks. Do NOT use for simple lookups, single-file edits, or questions answerable in one response.
Deterministic audit of cron/scheduled job scripts for reliability, error handling, logging, cleanup, and concurrency safety. Use when user says "audit cron", "check cron script", "cron best practices", "scheduled job review", or "bash script audit". Do NOT use for crontab scheduling syntax, systemd timers, or general shell linting without a cron/scheduled-job context.
Systematic detection and prioritization of neglected code quality issues: stale TODOs, unused imports, deprecated functions, high complexity, dead code. Use when user requests "code cleanup", "find TODOs", "technical debt scan", or "quality of life fixes". Do NOT use for bug fixing (use systematic-debugging), feature work (use test-driven-development), or formatting-only (use code-linting).