技術寫作

TDD方法論に従ってテストを作成します。テストファイルの配置（コロケーション）、命名規則、テスト構造のベストプラクティスに従います。React/TypeScript、Go、Rustで適切なパターンを使い分けます。「テストを書いて」「テストを作成」「単体テストを追加」などのリクエストで起動します。

Format and lint markdown and MDX files using markdownlint with comprehensive rule knowledge for automated and manual fixes. Use when working with .md or .mdx files, formatting documentation, linting markdown/MDX, or when user mentions markdown issues, formatting problems, or documentation standards.

Command-line tool for managing TiddlyWiki files. Use when working with TiddlyWiki (.html) files, tiddlers, or when the user mentions TiddlyWiki operations.

Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.

Write focused tests for core user flows and critical paths with clear test names, behavior-focused assertions, mocked external dependencies, and fast execution, deferring edge case testing until explicitly required. Use this skill when creating or modifying test files, writing unit tests, integration tests, or test cases for any feature. Apply when writing test files (test/, __tests__/, spec/, .test.js, .spec.ts, test_*.py), implementing tests for core user workflows, testing critical business logic, mocking external dependencies (databases, APIs, file systems), writing descriptive test names, creating fast-running unit tests, or adding tests at logical completion points of feature development. Use for any task involving test creation, test coverage, test strategy, or test-driven development.

Use when creating Continue rules - provides required name field, alwaysApply semantics, glob/regex patterns, and markdown format with optional frontmatter

Apply rigorous test-driven development methodology following the Red-Green-Refactor cycle (write failing test, implement minimal code to pass, refactor while staying green) that ensures tests genuinely verify behavior by requiring observed failure before implementation, preventing untested code and false-positive tests. Use this skill when implementing any new feature or functionality in any programming language, when fixing bugs or resolving defects in existing code, when refactoring code to improve design while preserving behavior, when adding new methods, functions, classes, or modules to a codebase, when modifying existing behavior or business logic, when writing code in any file that will be executed in production environments, when creating API endpoints, service methods, or controller actions, when implementing data validation, transformation, or processing logic, when building user interface components with testable behavior, when writing algorithms, calculations, or business rules, when integrating w

Follow consistent project structure, clear documentation, version control best practices, environment configuration, dependency management, code review processes, and feature flag usage for maintainable team development. Use this skill when organizing project files and directories, writing or updating documentation (README files, architecture docs, contribution guidelines), managing dependencies (package.json, requirements.txt, Gemfile), configuring environment variables, implementing feature flags, writing commit messages, creating pull/merge requests, or establishing team development workflows. Apply when setting up project structure, documenting setup instructions, managing configuration files, maintaining changelogs, or implementing development conventions. Use for any task involving project organization, team collaboration standards, or development workflow best practices.

Write secure, optimized database queries using parameterized queries, eager loading to prevent N+1 problems, and strategic indexing for performance. Use this skill when writing SQL queries, ORM queries, database interactions, or optimizing data fetching logic. Apply when working with query files, repository patterns, data access layers, SQL statements, ORM methods (ActiveRecord, Sequelize, Prisma queries), JOIN operations, WHERE clauses, preventing SQL injection, implementing eager loading or includes, adding query timeouts, wrapping operations in transactions, or caching expensive queries. Use for any task involving database reads, writes, complex queries, query optimization, or data fetching performance.

Design and implement RESTful API endpoints following REST principles with proper HTTP methods, status codes, and resource-based URLs. Use this skill when creating or modifying API endpoints, route handlers, controllers, or API configuration files. Apply when working on REST API design, endpoint implementations, API versioning, request/response handling, HTTP method routing (GET, POST, PUT, PATCH, DELETE), query parameter filtering, API rate limiting, or any file that defines API routes such as routes.py, api.js, controllers/, endpoints/, or API documentation files.

Prevent common testing anti-patterns that undermine test effectiveness and code quality by ensuring tests verify real behavior rather than mock behavior, keeping production code free from test-only pollution, and enforcing thoughtful mocking strategies. Use this skill when writing or modifying any test files (.test.ts, .test.js, .spec.ts, _test.py, test_*.py, *_test.go, *_spec.rb), when adding mock objects, stubs, spies, or test doubles to test suites, when considering adding methods or properties to production classes that are only called from test code, when setting up complex test fixtures or test data, when tests are failing and you're tempted to adjust mocks to make them pass, when deciding how to isolate code under test from external dependencies, when implementing dependency injection or test seams, during code reviews when reviewing test implementation and mocking strategies, when refactoring tests that have become brittle or hard to maintain, when test setup code is becoming longer than the actual te

Use when creating agents.md files - provides plain markdown format with NO frontmatter, free-form structure, and project context guidelines for AI coding assistants

Implement robust error handling with user-friendly messages, specific exception types, fail-fast validation, centralized error handling, graceful degradation, retry strategies, and proper resource cleanup. Use this skill when implementing error handling logic, try-catch blocks, exception handling, error boundaries, validation checks, API error responses, or resource cleanup. Apply when writing error handling in API controllers, service layers, frontend error boundaries, input validation, external service calls with retry logic, error logging, user-facing error messages, finally blocks for resource cleanup, or when establishing centralized error handling patterns at application boundaries. Use for any task involving exception handling, error recovery, graceful failure, or user error communication.

Use when creating GitHub Copilot instructions - provides repository-wide and path-specific formats, applyTo patterns, excludeAgent options, and natural language markdown style

Use when creating Windsurf rules - provides plain markdown format with NO frontmatter, 12,000 character limit, and single-file structure requirements

Standards and guidelines for organizing, structuring, and maintaining documentation in the PRPM repository - ensures consistency across user docs, development docs, and internal references

Use when creating OpenCode agents - provides markdown format with YAML frontmatter, mode/tools/permission configuration, and best practices for specialized AI assistants

Write consistent, maintainable CSS following the project's methodology (Tailwind, BEM, utility classes, CSS modules) with design system adherence and performance optimization. Use this skill when writing or modifying styles, CSS files, utility classes, CSS-in-JS, styled components, or any styling code. Apply when working with .css, .scss, .module.css files, Tailwind utility classes, styled-components, CSS modules, design tokens (colors, spacing, typography), framework-specific styling approaches, optimizing CSS for production, implementing CSS purging or tree-shaking, or avoiding style overrides. Use for any task involving visual styling, layout styling, design system implementation, or CSS organization.

Write clean, consistent code following naming conventions, automated formatting, DRY principles, small focused functions, and meaningful variable names across all languages and files. Use this skill when writing or modifying any code file in any language or framework. Apply when naming variables, functions, classes, or files, when refactoring code to remove duplication, when breaking down large functions into smaller focused ones, when cleaning up dead code or unused imports, when ensuring consistent indentation and formatting, when choosing descriptive names over abbreviations, or when following the project's linting and formatting rules (ESLint, Prettier, RuboCop, Black, etc.). Use for any task involving code organization, readability, maintainability, or style consistency across the codebase.

Write content that sounds natural, conversational, and authentically human - avoiding AI-generated patterns, corporate speak, and generic phrasing