Loading...
Loading...
Found 2,061 Skills
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.
Web page and website scraping with Firecrawl API. Use this skill when scraping web articles, blog posts, documentation pages, paywalled content, or JavaScript-heavy sites. Triggers on requests to scrape websites, extract article content, convert pages to markdown, or handle anti-bot protection.
Nx monorepo management skill for AI-native development. This skill should be used when working with Nx workspaces, project graphs, affected detection, code generation, and caching. Use when analyzing dependencies, running affected commands, generating code, configuring Nx Cloud, or optimizing build performance. Invoke nx-mcp tools for documentation queries.
Convert documents and text to audio using Google Cloud Text-to-Speech. Use this skill when the user wants to: narrate a document, read aloud text, generate audio from a file, convert text to speech, create a recording of documentation or analysis, create a podcast from a document, or use Google TTS/text-to-speech. Trigger phrases: "read this aloud", "narrate this", "create a recording", "text to speech", "TTS", "convert to audio", "audio from document", "listen to this", "generate audio", "google tts", "create a podcast".
Verify logic diagrams against source code. Check line-number accuracy, Mermaid syntax, node completeness, and side effect documentation. Runs as independent Critic in fork context. Use when: verify logic, check logic diagram, validate phase 2, re-verify-logic.
Architecture analysis, violation detection, and pattern validation. USE WHEN: reviewing code architecture, identifying violations, verifying patterns, updating technical documentation. Reference: docs/02-architecture/ARCHITECTURE.md Examples: <example> Context: User wants to check if code follows architecture. user: "Analyze if the payment module follows our architecture" assistant: "I'll use architecture-analyzer to review against ARCHITECTURE.md." <commentary>Architectural review is architecture-analyzer specialty.</commentary> </example> <example> Context: Need to identify technical debt. user: "Find architectural violations in the services layer" assistant: "I'll use architecture-analyzer to scan for violations." <commentary>Violation detection is architecture-analyzer responsibility.</commentary> </example>
Vapor UI design system component and icon guide, UI mockup generator, and Figma design converter. Provides component catalog, icon lookup, usage patterns, props documentation, and converts Figma designs to production-ready vapor-ui code. Use when user asks "vapor-ui components", "vapor-ui icons", "아이콘 찾기", "vapor-ui 사용법", "vapor-ui를 사용해서 시안 구현", "convert figma", "figma to code", "implement design from figma", provides a Figma URL, or mentions specific components like "Button", "Input", "Modal".
Transform verbose technical documentation into concise, scannable specs. Use this skill when you need to condense, summarize, or reformat technical docs, specs, or READMEs — including when a document is too verbose, when you want a technical summary, or when working with lengthy specification documents. Triggers on phrases like "make this concise", "too verbose", "condense this", "technical summary", "strip the fluff", or "reformat this spec". See assets/template.md for the standard output structure.
Manage design tokens, component libraries, and pattern documentation. Trigger with "design system", "component library", "design tokens", "style guide", or when the user asks about maintaining consistency across designs.
Generate marketing screenshots of your app using Playwright. Use when the user wants to create screenshots for Product Hunt, social media, landing pages, or documentation.
This skill should be used when the user asks to "generate design document", "create database schema", "design API interface", "draw flowchart", "create sequence diagram", "design system architecture", "design module structure", "create data flow diagram", or mentions technical design documentation. Generates comprehensive technical design documents with database schemas, API specs, and Mermaid diagrams.