文件

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

Use when writing or modifying Bash/shell scripts. Covers script structure, variables, quoting, conditionals, and loops with modern best practices.

Use when creating or updating technical blueprint documentation for new features, API changes, or architectural modifications. Always use search_blueprints first to avoid duplication, then write_blueprint with proper structure.

Use when designing system architecture, making high-level technical decisions, or planning major system changes. Focuses on structure, patterns, and long-term strategy.

Use when writing or creating new Standard Operating Procedures (SOPs) for AI agents. Covers effective SOP writing, clarity principles, and actionable instruction design.

Create custom linting rules for markdownlint including rule structure, parser integration, error reporting, and automatic fixing.

Use when testing Effect code including Effect.gen in tests, test layers, mocking services, and testing error scenarios. Use for writing tests for Effect applications.

Use when writing new functions, adding features, fixing bugs, or refactoring by applying TDD principles - write failing tests before implementation code, make them pass, then refactor.

Use when writing or editing markdown files. Covers headings, text formatting, lists, links, images, code blocks, and blockquotes.

Use when creating or improving component documentation in Storybook. Helps generate comprehensive docs using MDX, autodocs, and JSDoc comments.

Use when writing shell scripts following modern best practices. Covers portable scripting, Bash patterns, error handling, and secure coding.

Use when C# async/await patterns including Task, ValueTask, async streams, and cancellation. Use when writing asynchronous C# code.

Use when writing low-level system software in C requiring file I/O, process management, signals, and system calls.

Use when creating or updating documentation including READMEs, API docs, inline comments, or technical guides. Focuses on clarity and usefulness for the intended audience.

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

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 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.