Documentation

Use when you have a spec or requirements for a multi-step task, before touching code. Creates detailed implementation plans with bite-sized tasks.

Web crawling and content extraction to clean markdown files. Use this skill when the user wants to: (1) Crawl a website or webpage, (2) Extract and clean content from URLs, (3) Create markdown documentation from websites, (4) Analyze website structure before crawling, (5) Download website content including subpages. Typical triggers include 'crawl this website', 'extract content from URL', 'download this site as markdown', 'analyze website structure'.

Create comprehensive, production-ready frontend implementation plans for any UI screen or feature. Use this skill when documenting how to build UI components, establishing design systems, planning component architecture, or creating technical specifications for frontend development. Works across frameworks (React, Vue, Angular, Svelte, etc.) and focuses on clear structure, reusable patterns, and maintainability.

Research documentation and evidence synthesis framework for MYCURE healthcare products using HIGH/MEDIUM/LOW confidence grading, triangulation methodology, and rigorous citation standards. Auto-activates for research documentation, evidence grading, healthcare systems analysis, user research synthesis, market analysis, competitive research. Includes Philippine healthcare context (LGU health systems, FHISIS, PhilHealth).

Organize and normalize an Obsidian vault in a Zettelkasten, folder-first style. Use when asked to scan/analyze an Obsidian vault, generate Report.md and an executable Plan.md, normalize filenames (YYYYMMDD Title), merge YAML frontmatter (type/status/created/updated/tags/aliases/source), plan moves between top folders (00_Inbox/10_Literature/20_Permanent/30_Maps/40_Projects/90_Archive), fix wikilinks and markdown links after renames/moves, manage attachments in per-top-folder _assets, and apply changes with rollback via backups in 90_Archive/_organizer_backups.

Provides guidance and best practices for writing simple, understandable code that developers can easily maintain

Create well-structured user stories from requirements with clear acceptance criteria, technical context, and test scenarios. Use when creating user stories, refining backlog items, or breaking down epics.

Documentation generation patterns for technical specs, API docs, user guides, and knowledge bases using real tools like Sphinx, MkDocs, TypeDoc, and Nextra. Use when creating docs from code, building doc sites, or automating documentation workflows.

Use when user requests automated documentation generation from requirements file. Triggers include:- Korean: "문서 작성해줘", "write-docs 실행해줘", "자동 문서 생성"- English: "write documentation", "run write-docs", "generate from requirements"- Context: User has run prepare-docs and has docs/doc-requirements.md file readyThis skill focuses on Step 2 of automated workflow: Reading requirements file and generatingdocumentation automatically with per-sentence accuracy tracking and rationale for low-confidence statements (< 70%).

Default testing standard for all implementation work - ensures code actually works through mandatory execution validation before confirming to user. Applies automatically whenever writing, modifying, debugging, or implementing any code (scripts, APIs, UI, configs, data operations, logic changes). This is the baseline expectation, not an optional extra - every implementation must be verified through actual execution, not assumed correct.

Sync markdown projects to Confluence using the markdown_confluence tool. Use for publishing, crawling, and managing Confluence pages from local markdown files.

Use when creating or pricing energy consulting proposals including ASHRAE Level 1/2/3 audits, benchmarking services, commissioning, compliance pathway consulting, and performance target analysis. Provides pricing models, cost estimation, scope templates, service definitions, labor hour estimates, and proposal generation. Use when the user mentions proposal writing, pricing services, scoping work, energy audit costs, consulting rates, or needs to generate professional proposals for energy projects.

Technical content writer for marketing pages, blogs, documentation, and video scripts. Use when asked to create marketing content, landing pages, blog posts, technical documentation, video scripts, or any content that requires deep understanding of the codebase and task history.

Comprehensive Playwright automation testing skill with E2E testing standards, test generation workflows, and browser automation best practices. Use when writing automated browser tests, testing user flows, or performing web application QA.

Critical review and gap analysis skill that can be invoked at any workflow stage. Use to challenge decisions, identify missing specifications, verify coherence, and surface unaddressed questions in CDC, findings, plans, or any deliverable. Acts as a devil's advocate by deeply analyzing codebase, project documentation ([DOC]-* folders), and context.

Automatically bridge long technical sessions to keep context window small and costs low. Extracts key technical decisions, resolved bugs, active tasks, and essential code snippets from conversation history into a compact markdown summary (2,000–5,000 tokens). Use when reaching a project phase milestone, when Claude warns the context window is getting full, or to start a fresh session with minimal token cost while maintaining continuity.

Hidden automatic debugging when something breaks - user sees simple question or "fixing..." not stack traces or technical errors

Expert knowledge for Motivation Layer modeling in Documentation Robotics

Guide for the inter-host agent API system. Use when adding capabilities to hosts, writing handlers, understanding the GC protocol, or debugging agent call issues.

Documentation and code examples research expert using Exa AI and Context7. Finds official docs, production code examples, technology comparisons, and best practices. Auto-activates when new libraries mentioned or user requests "docs", "examples", "best practices", or technology comparisons.