Technical Writing

Perform a repo-wide, evidence-based audit of documentation against the current codebase and recent changes. Produces a proposed, fully rewritten documentation set in TempDoc-ForUserReview and asks for approval before any changes are applied to the existing docs.

Generate professional HTML presentation slides from Markdown files or raw content. Use when creating presentations, slide decks, or when asked to make slides. Fully automated workflow - Markdown analysis → Layout selection → HTML generation → Thumbnail generation → Surge deployment. Supports 16 layouts, Chart.js graphs, and interactive features.

Standards and templates for writing detailed feature specifications. Use when transforming requirements into implementation-ready specs.

Expert in Lighthouse Journey Timeline frontend architecture, React patterns, TypeScript, TanStack Query, Zustand, and component development with strong type safety. Use when building UI components, implementing data fetching, managing state, writing forms, styling with Tailwind, testing React components, or integrating with backend APIs.

Generates clear commit messages from git diffs. Use when writing commit messages or reviewing staged changes.

End-to-end feature development workflow with brainstorming, TDD, implementation, testing, and documentation. Use when adding new features, implementing user stories, or building new capabilities. Enforces test-first development, encourages design exploration, and ensures proper documentation.

Create ASCII architecture diagrams for ADRs using graph-easy. Use when writing ADRs, adding diagrams to existing ADRs, or when user mentions "ADR diagram", "architecture diagram", "ASCII diagram". Zero external dependencies for rendering - pure text output embeds directly in markdown.

Access Splynx documentation from wiki.splynx.com using Crawl4AI MCP.Provides navigation guide, URL patterns, and web scraping for JS-rendered pages.

Automatically create weekly folder structures for Gastrohem WhatsApp conversations. This skill should be used when the user asks to create weekly folders, set up a new week, or prepare folder structure for WhatsApp documentation (e.g., "Create weekly structure", "Set up folders for next week", "Create structure for 27.10 - 02.11"). Creates Monday-Sunday folders with chat.md files in each department.

Designs RESTful and GraphQL APIs with clear contracts and documentation

Simplified document review methodology with 4 core tags (@FIX, @TODO, @VERIFY, @OK) and [MACRO] flag for systemic impact. Use for annotating and reviewing documentation.

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.

Convert Markdown files to beautifully styled PDFs with full Chinese font support. Use when: (1) Converting .md files to PDF format, (2) Creating printable documents from Markdown, (3) Generating book chapters or story PDFs, (4) Needing PDF output with custom styling (colors, fonts, backgrounds), (5) Working with Chinese text that needs proper rendering in PDF.

Core development principles and guidelines covering security, QA, performance, documentation, and coding standards. Used by all agents to ensure consistent quality across the Orchestra system.

ドキュメント更新スキル（仕様書、設計書、README等の更新）

Spec-First, Agent-Implemented Software Development Lifecycle. Use when:(1) Starting a new software project that needs structured design-before-code approach,(2) User mentions "SDLC", "spec-first", "design docs", or "implementation spec",(3) User wants to go from requirements/intent to working code with traceability,(4) Project requires documented architectural decisions and review checkpoints,(5) User has existing design artifacts and wants to continue from a specific phase.Produces: Intent doc → HLD → ADR-Lite → EIS → Code → Validation tests.

Interpretive guidance for designing Claude Code sub-agents. Helps apply official documentation effectively and avoid common pitfalls. ALWAYS use when creating or reviewing sub-agents (aka agents or subagents).

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

Use when refactoring fat Rails models with repetitive prefixes like entropy_*, notification_*, or multi-association coordination. Extracts PORO wrappers that group operations around nouns/concepts.

Guidelines for generating coherent book prose including voice and tone, paragraph structure, transition techniques, and chapter flow patterns. Use when writing book content, structuring chapters, or maintaining narrative consistency.