Technical Writing

Top orchestrator for complete doc system. Delegates to ln-110 coordinator (project docs via 5 L3 workers) + ln-120-150 workers. Phase 4: global cleanup. Idempotent.

Fetch and summarize web content for any research task - documentation, design inspiration, competitor analysis, tutorials, API docs. Use when you need to understand web pages, extract key information, research patterns, or gather context for development work.

This skill should be used when the user asks about "tests", "unit tests", "EditMode tests", "PlayMode tests", "Test Runner", "test coverage", "NUnit", "Assert", "test fixtures", "writing tests", "running tests", or discusses Unity testing patterns and practices.

Expert software product manager who works directly with stakeholders to understand their needs and create comprehensive product specifications. Use when users need help designing software, defining requirements, creating PRDs, writing user stories, or developing functional specifications. Guides product management aspects of software development, asks clarifying questions, uncovers unstated preferences and assumptions, determines happy paths and error handling, and creates documentation understandable to both stakeholders and engineers.

Write, debug, review and explain source code following object-oriented best practices, DDD principles, and comprehensive testing standards. Use when writing new code, refactoring, debugging, code review, or explaining programming concepts.

Use when editing docs/index.html, creating charts with Plot, adding SQL cells, loading data with FileAttachment, or building visualizations. Triggers on any editing of docs/index.html, Observable notebooks, or front-end visualization work.

Write clean, maintainable Go code following Clean Architecture, dependency injection, and ChecklistApplication patterns. Use when writing new Go code, refactoring, or implementing features.

Test infrastructure patterns - PGlite for in-memory PostgreSQL, Redis/S3 mocks, TestSetup factory, Vitest. Use when writing tests or adding test infrastructure.

Intelligently routes requests to the correct context instructions and documentation files. Use this skill to determine which AGENT.md, guide, or technical instruction file is most relevant for a user's request.

LLM-only skill that takes a textual description of a new skill and generates a complete minimal file plan for a new MOVA skill (schemas, envelope, manifest, prompt profile, runtime binding, docs, cases).

Automatically generate documentation when user mentions needing API docs, README files, user guides, developer guides, or changelogs. Analyzes code and generates appropriate documentation based on context. Invoke when user mentions "document", "docs", "README", "API documentation", "guide", "changelog", or "how to document".

Bidirectional markdown ↔ SQLite conversion with column limit protection and smart section extraction. Import with Python, query with sqlite3.

학습 중 떠오른 아이디어와 메모를 아카이브 파일에 시간순으로 기록합니다. `scripts\study-note-helper.bat`를 사용하여 현재 KATA 프로젝트의 docs/study/아카이브.md에 노트를 추가합니다.

Python coding standards, conventions, and best practices. Use when writing, reviewing, or testing Python code.

Look up official documentation for any library, framework, or API using web search. Find usage examples, API references, and best practices. Activated when users ask "how do I use [library]?", need API documentation, or reference external packages.

Apply wikilink suggestions to current or specified note. Triggers on "apply wikilinks", "add wikilinks", "wikilink this note".

Comprehensive documentation maintenance operations including facts derivation, extraction, building, validation, and drift detection

Systematically improve documentation quality from 7/10 → 9/10 using assessment checklists and transformation patterns. Use when documentation exists but lacks Quick Start, clear prerequisites, or working examples. Optimized for crypto/trading data projects.

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.

Use when creating or modifying plugin.json manifests - manifest development with required fields, metadata, and configuration for November 2025 specifications