Technical Writing

비정형 마크다운 작성을 markdown-writer-agent에 위임

Writing style guidelines for clear, human-centered communication. Use when writing blog posts, documentation, README files, marketing copy, emails, or any external-facing content. Apply these rules to produce direct, specific, jargon-free writing.

Build and maintain high-quality documentation using MkDocs Material. Use this skill to set up new documentation sites or maintain existing ones with a modern, dark-mode-first aesthetic.

Clear writing standards based on Zinsser's principles. Use for documentation, commit messages, PR descriptions, and technical communication.

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.

Design system architectures with focus on scalability, maintainability, and user value. Create comprehensive architectural documentation including technology decisions, API design, data architecture, and security. Use when designing new systems, making technology choices, or planning system migrations.

Analyzes codebases to generate comprehensive documentation including structure, languages, frameworks, dependencies, design patterns, and technical debt. Use when user says "analyze repository", "understand codebase", "document project", or when exploring unfamiliar code.

This is a new rule

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

Software testing patterns, strategies, and best practices. Use when writing tests, discussing test architecture, mocking, fixtures, or test organization. Triggers on mentions of testing, unit tests, integration tests, pytest, jest, mocking, fixtures, TDD, test coverage.

Use when consuming jp-ui in an app: installation, CSS/theme setup, component selection, and token usage; guide Codex to the jp-ui docs and types for implementation details.

Quick access to up-to-date library documentation using MCP. Use this skill when you need to reference official documentation for libraries, frameworks, or APIs. Leverages the context7 MCP server to fetch current docs for React, Next.js, Vue, MongoDB, Supabase, and hundreds of other libraries. Complements the documentation-maintainer agent.

Real-time web search using Exa AI. Use when you need current information, fact-checking, researching unfamiliar topics, or finding documentation. Triggers on requests mentioning search, lookup, find online, current information, or research.

Go idioms, style guide, and best practices with YAGNI/KISS principles. Use when writing or reviewing Go code.

Shared resource library for Google integration skills. DO NOT load directly - provides common references (setup, API docs, error handling, authentication) and scripts used by gmail, google-docs, google-sheets, google-calendar, and future Google skills.

Use when deploying MkDocs documentation to GitHub Pages with GitHub Actions - covers Python-Markdown gotchas (indentation, footnotes, grid tables), workflow configuration, and systematic markdown fixing

Use when writing tests or implementing code. Defines RED-GREEN-REFACTOR cycle and test execution workflow.

Implements database integration patterns for Rust backends using SQLx and SeaORM. Use when setting up database connections, writing queries, defining entities, managing migrations, or configuring connection pools. Covers compile-time checked SQL, ORM patterns, and N+1 prevention.

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

Microsoft Pragmatic Rust FFI Guidelines. Use when working with C/C++ interop, creating cdylib, writing unsafe FFI code, or multi-DLL Rust projects.