Loading...
Loading...
Found 1,951 Skills
A documentation-focused skill for game architecture design. Produces technical selection, design, and planning documents through a structured pipeline. Use this skill to generate requirement analysis, technical design, and implementation planning documents for new game projects or major feature development.
Creates comprehensive README files with templates for different project types. Use when creating README, project documentation, or getting started guides.
Compile an agent-optimized changelog by cross-referencing git history with plans and documentation. Use when asked to "update changelog", "compile history", "document project evolution", or proactively after major milestones, architectural changes, or when stale/deprecated information is detected that could confuse coding agents.
Comprehensive multi-wave web research with strategic source selection. Gathers information from official docs, community resources, and advanced sources. Use for deep technical research, API documentation, best practices. Triggers: research web, deep research, comprehensive research, find documentation.
A technical writer who crafts clear, comprehensive documentation. Specializes in README files, API docs, architecture docs, and user guides.
PDCA document templates for consistent documentation. Plan, Design, Analysis, and Report templates with proper structure. Use proactively when generating PDCA documents to ensure consistent format. Triggers: template, plan document, design document, analysis document, report, 템플릿, 계획서, 설계서, 분석서, 보고서, テンプレート, 計画書, 設計書, 模板, 计划书, 设计书, plantilla, documento de plan, documento de diseño, documento de análisis, informe, modèle, document de plan, document de conception, document d'analyse, rapport, Vorlage, Plandokument, Designdokument, Analysedokument, Bericht, modello, documento di piano, documento di progettazione, documento di analisi, rapporto Do NOT use for: code implementation, deployment, or non-documentation tasks.
Look up CE.SDK React reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for React — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing React doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about React configuration user: "How do I configure the editor in React?" assistant: "I'll use /cesdk:docs-react to look up configuration options." </example> <example> Context: User needs React component setup user: "How do I embed CE.SDK in a React component?" assistant: "Let me use /cesdk:docs-react to find the relevant documentation." </example>
Check or verify whether a Skill complies with best practice specifications, covering naming conventions, directory structure, metadata integrity, temporary file cleanup, and dependency format validation. It provides detailed checklists, automatic repair suggestions, and report templates, and also supports integrity checks and automatic repair of skill library documentation. It is suitable for quality verification after creating or modifying a Skill
Maintain README files with setup instructions, features, tech stack, and usage examples. Use when updating project documentation, adding new features, improving onboarding, or creating READMEs for new packages.
Conducts in-depth analysis of a specific source or topic, producing comprehensive summaries for research synthesis. Use when you need detailed analysis and documentation of individual sources as part of a larger research effort.
Troubleshooting Guide Creator - Auto-activating skill for Technical Documentation. Triggers on: troubleshooting guide creator, troubleshooting guide creator Part of the Technical Documentation skill category.
Generate a Phase Spec/PRD by extracting features from an annotated Vision PRD. Use when user wants to create quarterly phase documentation, extract requirements from vision, plan a development phase, or decompose features into R-nnnn requirements. Requires annotated Vision PRD with F-nnn tags and Coverage Index.