技術寫作

Search COMSOL Multiphysics documentation. Use when asked about COMSOL, mesh refinement, boundary conditions, solvers, physics interfaces, FEM simulation, or COMSOL error messages.

Expert API research including discovery, evaluation, integration analysis, and documentation review

Co-create any professional writing through Socratic dialogue using established voice patterns

Write automated tests following a pragmatic, integration-focused philosophy. Use when writing tests for new features, writing tests for bug fixes, adding test coverage, or deciding what/how to test. Emphasizes confidence over coverage, real objects over mocks, integration over isolation, and simplicity over dogma.

Python testing framework for writing simple, scalable, and powerful tests

Complete end-of-session workflow for SheldonFS project. Handles code commits, quality checks, documentation updates, and merge process. Use when finishing a development session or feature branch.

Comprehensive writing guidance for professional documents across legal, academic, executive, and business contexts. Use when drafting, editing, or revising any document where quality prose matters: briefs, memos, law review articles, reports, client letters, contracts, executive summaries, presentations. Provides style selection, cognitive fluency techniques, structure frameworks, concision patterns, and revision checklists. Invoke when users ask to write, edit, revise, or improve documents.

Code complexity guidelines to keep cyclomatic complexity below 6 using strategy patterns or dispatch tables. Use when writing or refactoring functions with complex branching logic.

Guide for implementing MongoDB - a document database platform with CRUD operations, aggregation pipelines, indexing, replication, sharding, search capabilities, and comprehensive security. Use when working with MongoDB databases, designing schemas, writing queries, optimizing performance, configuring deployments (Atlas/self-managed/Kubernetes), implementing security, or integrating with applications through 15+ official drivers. (project)

This skill should be used when working with SLICOT (Subroutine Library In Control Theory) routines, translating Fortran 77 to C, parsing SLICOT HTML documentation, creating test cases from SLICOT examples, understanding SLICOT data formats, or planning translation priorities using dependency analysis tools.

Use when user requests automated documentation preparation. Triggers include: - Korean: "문서 준비해줘", "문서화 준비", "문서 요구사항 작성", "자동 문서화 준비" - English: "prepare documentation", "setup doc requirements", "prepare for automated docs" - Context: User wants to prepare all requirements for automated documentation generation This skill discovers sources, defines structure, and saves complete requirements to file for use with write-docs skill (automated generation).

CLI testing strategies and patterns for Node.js (Jest) and Python (pytest, Click.testing.CliRunner). Use when writing tests for CLI tools, testing command execution, validating exit codes, testing output, implementing CLI test suites, or when user mentions CLI testing, Jest CLI tests, pytest CLI, Click.testing.CliRunner, command testing, or exit code validation.

Testing patterns for litefs-py and litefs-django. Use when writing tests, setting up fixtures, understanding test organization, or configuring pytest marks. Triggers: test, pytest, unit test, integration test, property-based testing, hypothesis, fixtures, in-memory adapters.

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.