ux-designer
Perfect UX/UI designer that eliminates bugs, improves usability, and ensures flawless user experience. Use when user mentions "perfect the UI", "fix UX bugs", "improve demo", or "make it flawless".
daily-learning
Daily random learning assistant. Randomly picks topics from robot/coding/engineering/business/history/math, teaches with progressive depth, and quizzes on learned material using local cache.
reflect
Analyze and improve skills based on session outcomes. Use when: user says "reflect", "improve the skill", "what went wrong with the skill", "optimize skills", or wants to analyze skill effectiveness after using one. Triggers: "reflect", "skill improvement", "fix the skill", "update skill based on session".
skillsmatrix
Operator training and competency tracking for MNMUK machine shop. Supports IATF 16949 competency requirements and workforce planning. USE WHEN user asks 'who can run', 'training matrix', 'competency', 'skills matrix', 'operator certification', 'who is trained on', or workforce planning questions.
gentle-teaching
Guide AI-assisted learning that empowers learners while maintaining appropriate boundaries. Use when teaching, explaining concepts, or helping someone who is struggling to understand.
memory-summarize
Compress memories into structured summaries using low-cost AI models (Claude Haiku, GPT-4o-mini). Triggers when memory count exceeds 50 or token estimate exceeds 40000. Outputs structured JSON with compression metrics.
skill-spec
Claude Code プラグインの skill 仕様知識。スキルの正しい形式、フロントマター、description のベストプラクティスを提供。Use when creating, updating, or maintaining skills, understanding skill structure, or implementing SKILL.md files. Also use when user says スキル, SKILL.md, skills.
authoring-skills
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.
project-knowledge
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.
multi-ai-orchestration
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
your-skill-name
A clear, concise description of what your skill does and when Claude should use it. Include the main functionality and use cases.
global-tech-stack
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.
documentation-best-practices
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.
deliveryrelease-notes
Generate structured release notes tailored to the specified audience and highlighting value, rollout, and risks.
skill-name
Clear, concise description of what this skill does and when to use it (1-1024 chars). Include relevant keywords for agent discovery.
improve-skill
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.
bootstrap-product
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"
sequentialthinking
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.
software-design
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.
