Technical Writing

Guide technology selection workflow and ADR creation. Use when user asks about choosing a technology, comparing options, or needs to make a tech decision. Orchestrates discovery, evaluation, and documentation.

REST vs GraphQL, API versioning, rate limiting, and documentation for Elixir/BEAM APIs

정형화된 마크다운 문서 템플릿 사용 가이드

Write clean, consistent code following established naming conventions, automated formatting, DRY principles, meaningful variable names, small focused functions, and consistent indentation across all programming languages. Use this skill when writing or refactoring code in any programming language or file type including JavaScript (.js, .mjs, .cjs), TypeScript (.ts, .tsx, .mts), Python (.py), Ruby (.rb), Java (.java), Go (.go), Rust (.rs), PHP (.php), C# (.cs), Swift (.swift), Kotlin (.kt), or any other source code files. Use this when creating new functions, classes, interfaces, types, or variables that need appropriate naming following language-specific conventions like camelCase for JavaScript/TypeScript variables and functions (getUserById, totalPrice, isActive), PascalCase for class names, type names, and interfaces in most languages (UserProfile, DatabaseConnection, ApiResponse), snake_case for Python functions and variables (get_user_by_id, total_price, is_active), SCREAMING_SNAKE_CASE for constants (AP

Plan development sprints for Stapledons Voyage game features. Analyzes design docs, estimates effort considering AILANG constraints, and creates realistic sprint plans. Use when user asks to "plan sprint" or estimate game feature timelines.

Use semantic search to find relevant code and documentation when user asks about specific functionality, features, or implementation patterns. Automatically invoke when user asks "where is...", "how does... work", "find code that...", or similar conceptual queries. More powerful than grep for concept-based searches. Uses odino CLI with BGE embeddings for fully local semantic search.

Package entire code repositories into single AI-friendly files using Repomix. Capabilities include pack codebases with customizable include/exclude patterns, generate multiple output formats (XML, Markdown, plain text), preserve file structure and context, optimize for AI consumption with token counting, filter by file types and directories, add custom headers and summaries. Use when packaging codebases for AI analysis, creating repository snapshots for LLM context, analyzing third-party libraries, preparing for security audits, generating documentation context, or evaluating unfamiliar codebases.

Use when implementing features or adding functionality - dispatches incremental-tdd-agent that enforces ONE test at a time, preventing batch test writing that defeats incremental design discovery. Maintains discipline through entire feature implementation (10+ test cycles)

Terraform Registry documentation inspector using Chrome DevTools MCP. Use when validating provider documentation rendering, checking version availability, navigating resource/data-source docs, finding source code links, or comparing documentation quality against the Azure RM gold standard. Triggers on requests to inspect, validate, review, or benchmark Terraform provider documentation on registry.terraform.io.

babashka.json is a cross-platform JSON abstraction for Clojure/babashka. Use when working with JSON parsing, serialization, or writing portable code that runs on both JVM and babashka.

Analyzes narrative text and files to identify and remove AI-generated signals while preserving authentic voice and style. Runs input through comprehensive protocols covering vocabulary, syntax, character voice, emotional depth, and readability. Use this skill when you need to proof narrative content against AI detection patterns or humanize AI-assisted writing.

Use when writing or updating GitHub Actions workflow files (.github/workflows/*.yml) - provides latest version tags for official and popular third-party actions to avoid using outdated versions

Expert guidance for writing TypeScript code following modern best practices, targeting TypeScript 5.x and ES2022. Use this skill when writing, reviewing, or refactoring TypeScript code in any .ts or .tsx file. Provides comprehensive guidelines on type system usage, architecture patterns, security, testing, and performance.

Follow the project's Python-based tech stack using uv, FastMCP, Claude Agent SDK, Pydantic v2, SQLite with SQLModel, and pytest with ruff. Use this skill when writing Python code for the MCP Task Aggregator. When using FastMCP to create MCP servers or tools. When working with Claude Agent SDK for AI agents. When defining Pydantic models or using pydantic-settings for configuration. When writing SQLModel queries or database operations. When using loguru for logging. When integrating with Jira (jira-python), GitHub (pygithub), or Linear (linear-sdk). When running pytest tests or ruff linting. When configuring GitHub Actions CI/CD.

Write copy that converts. Use when writing landing pages, emails, sales copy, headlines, CTAs, social posts, or any persuasive content. Triggers on: make this convert, write copy for X, help me sell X, punch this up, write a landing page, write sales copy. Produces internet-native copy that sounds like a smart friend explaining something while quietly deploying every persuasion principle in the book. Includes complete reference material from Schwartz, Hopkins, Ogilvy, Halbert, Caples, Sugarman, and Collier.

Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.

MUST be loaded when setting up, installing, migrating, reviewing, auditing, or checking CLAUDE.md files in projects. Covers installing the promode CLAUDE.md into new projects, migrating existing CLAUDE.md content to READMEs (progressive disclosure), and auditing projects for conformance. Invoke PROACTIVELY when user mentions CLAUDE.md, project setup, agent configuration, or code meta files.

Generate and validate tech stack documentation. Use when starting a new project, documenting technology choices, or when user asks to create/update tech stack documentation. Includes structural validation and LLM-as-Judge content review.

Ensures CLAUDE.md, README.md, and CHANGELOG.md are updated before git push operations

Lookup up-to-date library docs via Context7 MCP (resolve-library-id / get-library-docs).