Documentation

Guidelines for writing unit and integration tests, including mocking strategies and coverage goals.

Analyzes business requirements and translates them into technical specifications

Apply Matt Palmer's voice, tone, and content pillars to any writing. Use for blog posts, social media, documentation, emails, or any content needing Matt's authentic brand voice.

NWEA MAP Growth 2025 Norms technical reference for student/school achievement and growth percentile calculations. Use this skill when implementing MAP norm comparisons, calculating student percentile ranks from RIT scores, computing growth percentiles, interpreting seasonal achievement data, or building norm-referenced reporting dashboards. Covers Mathematics, Reading, Language Usage (G2-G11), and Science (G2-G10) with Fall/Winter/Spring seasonal data.

Guide experienced developers through RED phase of TDD cycle - writing failing tests and verifying expected failures

Conduct comprehensive web research on any topic using available MCP tools including Perplexity for current information, Playwright for web automation, and DeepWiki for encyclopedia-style content. Use when users request research, information gathering, or need to investigate a topic.

Guide experienced developers on test structure, patterns, assertions, and test doubles for effective test-driven development

Guide for writing comprehensive tests in Elixir using ExUnit, property-based testing, mocks, and test organization best practices

Guide for spike-driven development methodology. Use when starting new features, testing architecture patterns, integrating unfamiliar APIs/data sources, or validating technical feasibility before full implementation. Emphasizes TDD, real data validation, and risk reduction through minimal proofs-of-concept.

Enhanced Just-In-Time document loading system that intelligently discovers, loads, and caches relevant documentation based on user intent and project context. Use when users need specific documentation, when working with new technologies, when answering domain-specific questions, or when context indicates documentation gaps.

Use when you need to plan technical solutions that are scalable, secure, and maintainable.

Generate comprehensive API documentation for REST, GraphQL, WebSocket APIs with OpenAPI specs, endpoint descriptions, request/response examples, error codes, authentication guides, and SDKs. USE WHEN user says 'viết document API', 'tạo API docs', 'generate API documentation', 'document REST endpoints', hoặc cần tạo technical reference cho developers.

Create a new Claude Code skill with proper structure, YAML frontmatter, and documentation. Use when user asks to "create a skill", "make a skill", "build a new skill", or "add a skill".

Transforms technical specifications into task files with 15 enrichments (10 universal + 5 spec-specific including UX flow and success metrics). Use when user says 'format specification', 'convert spec to tasks', 'process requirements', 'extract tasks from spec', or when detect-input-type returns 'spec'. Handles PRDs, feature specs, and technical requirements in .md files. (plugin:task-streams)

Implement feature changes by updating pseudocode, platform code, and product code from modified feature markdown files. Use when user asks to "implement features", "run miso", "update implementations", or "sync code with features".

Architecture Decision Records (ADRs)をdocs/adr/ディレクトリで管理します。新しいADRの作成、既存ADRの編集、ADR索引の確認を行います。ユーザーがアーキテクチャ決定の記録、ADRの作成・更新・検索を依頼したときに使用してください。番号の自動採番、プロジェクト固有のフォーマット（日本語、メタデータ構造）を遵守します。

Systematic technical debt reduction and code optimization agent. Use when refactoring code, reducing complexity, eliminating code smells, improving performance, cleaning up unused code, or modernizing legacy patterns. Handles dependency updates, architecture improvements, and codebase health metrics.

Use when implementing any feature or bugfix, before writing implementation code

Removes common AI-generated text patterns that make writing obviously machine-produced. Use when: (1) Writing or editing any text content, (2) User requests human-sounding or natural writing, (3) User wants to avoid AI slop or AI tells, (4) Creating content that shouldn't read as AI-generated. Apply automatically when generating prose, articles, emails, or creative content.Invoke with: /humanise-text, /humanize-text, /check-ai-patterns, or say "use the ai-text-humaniser skill to..."

Tests UI components with Testing Library including queries, user events, and async utilities. Use when testing React/Vue/Svelte components, writing accessible tests, or testing user interactions.