MUST BE USED when creating, improving, or reviewing Skills. Use PROACTIVELY when user mentions "create a skill", "new skill", "write a skill", "improve skill", "skill description", or "progressive disclosure". Guides through specification-compliant skill design with three-level progressive disclosure.
This skill provides guidance on designing effective evaluation rubrics. Use when: - Creating criteria for content or code quality assessment - Defining weights and thresholds for evaluation - Designing check types (pattern-based vs custom) - Structuring rubrics for maintainability and reusability
This skill should be used when implementing new features, understanding existing patterns, or when the user asks about "project-specific knowledge", "domain knowledge", "business logic", "data schema", "pipeline patterns", "WMAPE", "Bias", "Processor". Also used when the user says "document this pattern", "add to knowledge base", or when recurring patterns are identified. MUST reference before implementing features to ensure consistency with existing patterns.
Use when stuck on complex problems, need architecture validation, want code review from multiple perspectives, or debugging hits a wall - guides leveraging multiple AI models in parallel for better results
Generates comprehensive Map of Content (MOC) documentation for software projects using standard markdown links, analyzing current implementation state from codebase and devlog notes
A clear, concise description of what your skill does and when Claude should use it. Include the main functionality and use cases.
Generate comprehensive Game Design Documents for full production games. Use this when transitioning from prototype to full game, or when planning a complete game from scratch.
Create comprehensive spec with diagrams, flows, and thorough documentation. Use when: detailed spec, comprehensive spec, full spec, baldrick spec. Triggers on: detailed, comprehensive, full spec, thorough.
Reference the project's defined technology stack including frameworks, languages, databases, testing tools, and deployment infrastructure. Use this skill when making technology decisions or choosing libraries. When working with project configuration files like package.json, requirements.txt, or Gemfile. When setting up new features that need to align with existing technology choices. When onboarding to understand the project's technical foundation. When choosing tools for testing, linting, CI/CD, or third-party services.
Technical documentation and knowledge management expert. Use when creating comprehensive documentation systems, improving developer knowledge sharing, or building documentation-driven development workflows.
This skill should be used when creating or updating implementation documentation, task breakdowns, verification steps, or phase planning documents. It provides standards and templates for consistent, professional documentation throughout the MTG Agent project.
Generate concise specifications for development tools, editors, and utilities. Use this when planning a new tool, editor plugin, or standalone utility to assist with game development.
Guidelines for creating task-oriented how-to guide documentation. Use when writing content that helps users accomplish specific goals.
Comprehensive guide for coding workflow, naming conventions, architectural principles, and API implementation patterns.
Generate structured release notes tailored to the specified audience and highlighting value, rollout, and risks.
Clear, concise description of what this skill does and when to use it (1-1024 chars). Include relevant keywords for agent discovery.
Analyze coding agent session transcripts to improve existing skills or create new ones. Use when asked to improve a skill based on a session, or extract a new skill from session history.
Use when design is complete and you need detailed implementation tasks - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming minimal codebase familiarity
Transform a product briefing into comprehensive, research-backed product management artifacts. This skill conducts domain-expert research BEFORE user questioning to enable smarter questions and pre-populated artifacts with validated content. Uses Context7 for technology documentation, WebSearch for market/architecture/security research, and WebFetch for deep-dive analysis. Generates 4 research-enriched files: - product.md (product vision with market research citations) - roadmap.md (12-month roadmap with architecture research) - architecture.md (technical design with extensive Context7 references) - adr.md (architectural decisions with research-justified rationale) Triggers: "create product vision", "define new product", "product planning", "bootstrap product", "product documentation", "start new product", "product briefing"
Use this skill for systematic problem-solving through structured, iterative thinking. Break down complex problems, iterate on understanding, catch edge cases, and validate solutions comprehensively.
Structured process for designing software projects and libraries before implementation. Use when a user has a project idea and wants to think it through systematically, create a design document, or prepare a specification before coding. Triggers on phrases like "I want to build...", "help me design...", "I have an idea for...", or explicit requests for design docs, project planning, or architecture decisions.
Classify support tickets by urgency and category. Use when analyzing tickets, determining priority, routing customer requests, or when user asks to classify, triage, or categorize support tickets.
