Technical Writing

Use when writing infrastructure-as-code with Pulumi using programming languages for cloud resource provisioning.

Use when typeScript async patterns including Promises, async/await, and async iterators with proper typing. Use when writing asynchronous TypeScript code.

Use when writing and deploying Kubernetes manifests for container orchestration.

Use when writing SOPs that require precise requirement levels using RFC 2119 constraint keywords (MUST, SHOULD, MAY). Covers proper usage of requirement keywords for deterministic agent behavior.

Use when creating bidirectional links between code and documentation. Covers link patterns, documentation references, context preservation across artifacts, and maintaining synchronization between code and docs.

Use when Go concurrency with goroutines, channels, and sync patterns. Use when writing concurrent Go code.

Use when writing technical documentation, READMEs, or project documentation in markdown. Covers structure, conventions, and best practices.

Use when writing effective BDD scenarios including acceptance criteria, edge cases, and scenario organization. Use when defining behavior specifications.

Use when Java generics including type parameters, wildcards, and type bounds. Use when writing type-safe reusable code.

Use when writing and organizing Terraform infrastructure-as-code configurations for cloud resource provisioning.

Use when writing and organizing Ansible playbooks for automated configuration management and infrastructure orchestration.

Use when applying Behavior-Driven Development patterns including Given-When-Then structure, feature files, and acceptance criteria. Use when writing BDD-style tests and specifications.

Use when managing blueprints directory structure and avoiding duplication. Always search_blueprints before creating to prevent duplicate documentation. Handles naming conventions and cross-references.

Use after modifying existing systems to update blueprint documentation. Read blueprints with read_blueprint before changes, update with write_blueprint after. Prevents documentation drift.

Use when writing shell scripts that need to run across different systems, shells, or environments. Covers POSIX compatibility and platform differences.

Use when creating or formatting tables in markdown. Covers table syntax, alignment, escaping, and best practices.

Use when Rust async programming with tokio, async/await, and futures. Use when writing asynchronous Rust code.

Configure markdownlint rules and options including rule management, configuration files, inline comments, and style inheritance.

Use when working with Claude Code CLI, plugins, hooks, MCP servers, skills, configuration, or any Claude Code feature - provides comprehensive official documentation for all aspects of Claude Code

Use when creating structured operational runbooks for human operators. Covers runbook organization, documentation patterns, and best practices for clear operational procedures.