文件

Methodology for summarizing changes, extracting insights, and identifying follow-up actions.Triggers: catchup, what changed, summarize changes, context acquisition, handoff,progress review, recent changes, git log analysis, sprint summaryUse when: resuming work after absence, preparing handoff documentation, reviewingsprint progress, analyzing git history for contextDO NOT use when: doing detailed diff analysis - use diff-analysis instead.DO NOT use when: full code review needed - use review-core instead.Use this skill to quickly understand "what changed and what matters".

Workflow for capturing evidence and citations to create reproducible analysesand audit trails.Triggers: evidence capture, citations, reproducible analysis, audit trail,documentation, evidence logging, findings documentationUse when: conducting any review that needs evidence trails, creating auditdocumentation, ensuring reproducibility of analysesDO NOT use when: quick informal checks without documentation needs.DO NOT use when: structured output is the focus - use structured-output.Use this skill as foundation for all evidence-based review workflows.

Communicating the intended behavior and context of code through clear documentation and comments, and sharing knowledge with the team.

Incorporating security at every step of software development – writing code that defends against vulnerabilities and protects user data.

Ensuring software correctness and reliability by writing automated tests, using quality assurance tools, and systematically debugging issues.

Writing clean, understandable, and self-documenting code that is easy to review and maintain over time.

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

Creates syntactically correct mermaid diagrams (flowchart, sequenceDiagram, classDiagram, stateDiagram, erDiagram, gantt, mindmap) following official specifications. Prevents common errors like special characters in labels, subgraph syntax, note misuse, and reserved words. Use when creating or editing mermaid diagrams in documentation or design files.

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.

Generate images using Nano Banana Pro (Gemini 3 Pro Preview). Use when creating app icons, logos, UI graphics, marketing banners, social media images, illustrations, diagrams, or any visual assets. Supports reference images for style transfer and character consistency. Triggers include phrases like 'generate an image', 'create a graphic', 'make an icon', 'design a logo', 'create a banner', 'same style as', 'keep the style', or any request needing visual content.

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.

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

Write self-documenting code with clear structure and naming, adding minimal, helpful, evergreen comments only for large sections of complex logic, avoiding comments about recent changes or temporary fixes. Use this skill when writing or reviewing code in any file where comments or code documentation are involved. Apply when deciding whether to add comments, when refactoring code to be more self-explanatory through better naming and structure, when reviewing existing comments for relevance and evergreen quality, when removing outdated or change-related comments, or when adding concise explanatory comments for complex logic sections. Use for any task involving code documentation strategy, comment quality assessment, or improving code readability through structure rather than comments.

Expert guidance for writing secure, reliable, and performant Claude Code hooks - validates design decisions, enforces best practices, and prevents common pitfalls

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.

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