Technical Writing

Central CLAUDE.md file with project guidelines auto-injected into system prompt, achieving 10% accuracy lift in multi-hop reasoning through consistent context. Use for repo-wide context, coding standards enforcement, project guidelines, or architecture documentation. Auto-loaded by Claude Code CLI. Triggers on "project context", "coding standards", "CLAUDE.md", "project guidelines", "repo documentation".

Creates Better Auth configuration for frontend and backend: handlers, providers, middleware, session/token options. Uses Context7 MCP to retrieve Better Auth docs.

Write clean, readable code with consistent naming conventions, proper formatting, small focused functions, and DRY principles. Use this skill when writing ANY code in the project regardless of language or framework. When naming variables, functions, classes, or files. When structuring functions and deciding on their size and scope. When removing dead code, unused imports, or commented-out blocks. When applying the DRY principle to extract common logic. When ensuring consistent indentation and formatting across the codebase.

Atlassian Rovo Dev CLI 어댑터 (ACLI 서브커맨드). Jira/Confluence 통합 AI 개발 도구.

Use when implementing a new data source adapter for metapyle, before writing any source code

Create production-quality EPUB 3 ebooks from markdown and images with automated QA, formatting fixes, and validation. Use when creating ebooks, converting markdown to EPUB, or compiling chapters into a publishable book. Handles markdown quirks, generates TOC, adds covers, and validates output automatically.

Update all documentation in .plans, CLAUDE.md files, docs, and .tasks to match current codebase state. Use when user asks to update docs, refresh documentation, sync docs with code, or validate documentation accuracy.

Write rigorous implementation plans as if presenting to distinguished engineers. Use when entering plan mode, designing architecture, or when the user asks to plan a feature. Raises plan quality through expert audience framing.

Convert structured markdown hierarchies into professional SVG taxonomy diagrams with nested card support, trunk-and-branch arrow routing, and color-coded categories.

Apply rigorous scientific writing standards for academic manuscripts. Use when writing abstracts, introductions, methods, results, or discussions for papers, grants, theses, or mermaid figure.

Implements testing strategies for React Native components, MST stores, and services using Jest, React Testing Library, and Maestro. Use when writing unit, integration, or E2E tests in Purrsuit Mobile App.

Use this skill BEFORE using writing any Clojure code. It teaches how to use the Clojure REPL (via brepl) so you can test code, check if edited files compile, verify function behavior, or interact with a running REPL session.

HTML metadata and head content. Use when writing or reviewing page head sections including SEO, social sharing, performance hints, and bot control.

Guidelines for writing unit and integration tests, including mocking strategies and coverage goals.

Apply Matt Palmer's voice, tone, and content pillars to any writing. Use for blog posts, social media, documentation, emails, or any content needing Matt's authentic brand voice.

Guide experienced developers through RED phase of TDD cycle - writing failing tests and verifying expected failures

Conduct comprehensive web research on any topic using available MCP tools including Perplexity for current information, Playwright for web automation, and DeepWiki for encyclopedia-style content. Use when users request research, information gathering, or need to investigate a topic.

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

Guide for writing comprehensive tests in Elixir using ExUnit, property-based testing, mocks, and test organization best practices

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.