Loading...
Loading...
Found 2,058 Skills
Load PROACTIVELY when task involves reviewing code, auditing quality, or validating implementations. Use when user says "review this code", "check this PR", "audit the codebase", or "score this implementation". Covers the 10-dimension weighted scoring rubric (correctness, security, performance, architecture, testing, error handling, type safety, maintainability, accessibility, documentation), automated pattern detection for anti-patterns, and structured review output with actionable findings.
Shared foundation for Oracle & Corrector agents. Establishes the source hierarchy for resolving conflicts between documentation, code, and specs. Load this skill first when investigating how the system works.
Create structured documents from conversations, summaries, or content in open formats (markdown, PDF, text). Use when the user requests document creation, report generation, content export, conversation summaries, or structured documentation. Triggers include "create a document", "make a report", "summarize this conversation", "export to PDF/markdown", or any request to formalize content into a document. Works independently or integrates with design-assistant skill for polished visual output.
Generate Drizzle ORM schemas for Cloudflare D1 databases with correct D1-specific patterns. Produces schema files, migration commands, type exports, and DATABASE_SCHEMA.md documentation. Handles D1 quirks: foreign keys always enforced, no native BOOLEAN/DATETIME types, 100 bound parameter limit, JSON stored as TEXT. Use when creating a new database, adding tables, or scaffolding a D1 data layer.
Comprehensive guide to Miro as a visual collaboration platform. Covers canvas features, content types, AI capabilities, and enterprise use cases. For MCP tool documentation, see the miro plugin's skill (miro-mcp).
Query any public GitHub repo's documentation via DeepWiki. Use when needing to understand a library, framework, or dependency. Triggers on "look up docs", "how does X work", "deepwiki", "deepwiki".
Use the SmartThings Public REST API and automation models (rules, scenes), including endpoints for devices, locations, rooms, capabilities, automations, subscriptions, and rules, based on official documentation.
Comprehensive documentation of Claude's capabilities for visual regression testing, CI/CD integration, and quality assurance automation. Use when setting up testing infrastructure, implementing visual regression, or understanding agent testing capabilities. (project)
Scrape documentation websites into local markdown files for AI context. Takes a base URL and crawls the documentation, storing results in ./docs (or custom path). Uses crawl4ai with BFS deep crawling.
Research topics using web search and content fetching to find accurate, current information. Use when you need modern information, official documentation, best practices, technical solutions, or comparisons beyond your training data.
Explain English technical documents and text in Japanese with contextual understanding. Not a simple translator — reads the surrounding file or codebase context to provide deeper, more accurate explanations tailored for Japanese-speaking developers. Use when: "explain this English", "この英文を解説", "英語の解説", "en-explainer", "what does this mean", "この英文の意味", "英文を日本語で説明", "ドキュメントを解説", "README解説", "エラーメッセージの意味", "コメントの意味", "API仕様の解説", or when the user pastes English text and asks for explanation in Japanese. Also use when the user provides a file path and asks to explain specific English sections, or when they want to understand English code comments, error messages, config files, or technical documentation.
Manage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", or "strategic vs tactical". Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For boundaries, see clean-architecture.