security-checklist
Security best practices, OWASP guidelines, and vulnerability prevention checklist. (project)
doc-writer
Technical documentation specialist creating clear, comprehensive documentation including README, API docs, user guides, architecture specs, and tutorials. Use when writing project documentation, API references, setup guides, or any technical documentation requiring professional structure and clarity.
accessibility-complaint-narrative
Parse WCAG accessibility scan reports and combine with personal accessibility testing experiences to generate compelling, evidence-based violation narratives that cite both user impact and technical violations. Generates plain-text complaint narratives suitable for demand letters, legal notices, and accessibility audit reports.
product-manager
Organizing features and complex work into manageable/logical tasks
clarification-phase
Executes the /clarify phase using AskUserQuestion tool to resolve ambiguities through structured questions (≤3), prioritization, and answer integration. Use when spec.md contains [NEEDS CLARIFICATION] markers, when requirements need disambiguation, or when running /clarify command to resolve critical scope/security/UX ambiguities before planning. (project)
project-architecture
This skill should be used when the user asks about "namespaces", "singleton", "TileManager", "GameManager", "TokenManager", "InputManager", "data flow", "class responsibilities", "layers", "folder structure", "code organization", "design patterns", "ScriptableObject", "databases", or discusses Zero-Day Attack codebase architecture and patterns.
task-writing
Write high-quality, actionable tasks that are clear, well-scoped, and contain all the information needed for successful execution. Use when breaking down implementation plans, creating issues for bug fixes or features, writing tickets for sprints, defining work items from spec requirements, converting user feedback into tasks, or creating technical debt items. Triggers include "write task", "create issue", "write ticket", "define task", "bug report", "feature request", or when creating trackable units of work.
role-software-engineer
Role definition for software engineer agents. Defines responsibilities, principles, required skills, and success criteria. Use to understand what it means to operate as a software engineer in this codebase.
constitution-format
Knowledge about writing effective project constitution files for LLM/coding agents. Use this skill when creating, editing, or reviewing constitution.md files.
tyree-akerman-adr-format
This skill should be used when the user asks about "Tyree-Akerman format", "sophisticated ADR", "comprehensive ADR", "enterprise ADR", "formal ADR template", or needs guidance on creating ADRs using the Tyree-Akerman format for enterprise and formal documentation.
otaku-domain
Convention management domain knowledge for Otaku Odyssey. Use when implementing features related to conventions, attendees, vendors, sponsors, panels, or volunteers.
docs-writing
Writing clear, user-facing documentation for non-technical users. Use when creating in-app docs, help content, or feature documentation.
tech-specs-writer
Guidelines for creating technical specification and API reference documentation. Use when writing factual, complete content about data models, API contracts, and configuration options.
user-manual
エンドユーザー向けのマニュアル（USER_GUIDE.md）を生成・更新します。「ユーザーマニュアル更新」「マニュアル生成」「ユーザーガイド作成」などのリクエストで使用します。
ucp-protocol-architecture
This skill should be used when the user asks about "UCP architecture", "protocol structure", "OpenAPI spec", "OpenRPC spec", "capability design", "method naming", or needs to understand how UCP works. Provides guidance on UCP's layered architecture and spec generation.
interview-kernel
Core interview engine enforcing single-question discovery/decision gating. Use when building interview wrapper skills.
customer-experience
Expert customer service guidance from Madame Zelda for managing guest interactions, queue flow, and creating memorable festival experiences
feedback-integration
Process viewer comments and feedback to improve content
architecture-patterns
Provides guidance on software architecture patterns and design decisions. Use when designing systems, choosing patterns, structuring projects, or when asked about architectural approaches.
writing-documents
Technical documentation creation with focus on clarity, UI terminology consistency, and Japanese writing quality. Use when creating or reviewing technical documentation, API docs, feature specifications, or user guides.
ask-questions-if-underspecified
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly. Triggers: "ask questions", "clarify requirements", "need more info", "what's missing".
moonshot-detect-uncertainty
Detects missing requirements and generates clarification questions. Use after classification/complexity to decide if user input is needed.
technical-writing
Creates high-quality technical documentation including API documentation, user guides, tutorials, architecture documents, README files, release notes, and technical specifications. Produces clear, structured, and comprehensive documentation following industry best practices. Use when writing technical documentation, creating API docs, developing user guides, documenting architecture, writing tutorials, preparing release notes, or when users mention "technical writing", "documentation", "API docs", "user guide", "tutorial", "README", "technical specification", "architecture document", or "developer documentation".
