技術寫作

Expert SQL query writing, optimization, and database schema design with support for PostgreSQL, MySQL, SQLite, and SQL Server. Use when working with databases for: (1) Writing complex SQL queries with joins, subqueries, and window functions, (2) Optimizing slow queries and analyzing execution plans, (3) Designing database schemas with proper normalization, (4) Creating indexes and improving query performance, (5) Writing migrations and handling schema changes, (6) Debugging SQL errors and query issues

Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization

Use when creating or improving README files, project documentation, getting started guides, or installation instructions.

Expert guidance for Sparze ECS apps including systems, queries, components, resources, events, and performance trade-offs.

Complete testing infrastructure and patterns for the monorepo. Use this skill when writing tests, setting up test configuration, troubleshooting test failures, or working with the CI pipeline. Covers vitest configuration, Storybook addon-vitest integration, React Testing Library patterns, mock data setup, and the test-suite-runner agent for comprehensive testing.

効果的な学習体験を提供するチュートリアル・学習コンテンツの設計スキル。段階的学習パス、成功体験ファースト、レベル別ガイドを組み合わせた体系的アプローチで、学習者の理解度に応じた最適な学習導線を構築します。Anchors:• The Pragmatic Programmer（Andrew Hunt, David Thomas） / 適用: 実践的改善とコンテンツ品質維持 / 目的: 学習体験の効率化• Docs for Developers（Jared Bhatti） / 適用: チュートリアル設計と段階的ガイド / 目的: 学習パス最適化Trigger:チュートリアル設計、学習コンテンツ作成、段階的ガイド構築、教材構造化、学習者向けドキュメント開発時に使用

This skill should be used when the user wants to start a complete article writing project and needs guidance through the full iterative workflow. Triggers: "开始写作流程", "开始创作", "help me write article", "guide writing process"

Extract and maintain company-specific coding best practices from PR review comments. Use when the user requests to analyze PR comments from a repository to generate best practices documentation, or when implementing features and needs to reference established coding standards. Triggers include requests like "analyze PR comments and create best practices", "extract coding standards from repo X", or "check if this code follows our best practices".

Comprehensive error documentation patterns for APIs, libraries, and systems.Covers error catalogs, troubleshooting guides, recovery procedures, andrunbook creation to improve developer experience and reduce support burden.Anchors:• The Pragmatic Programmer (Hunt, Thomas) / 適用: error communication / 目的: clear actionable messages• Site Reliability Engineering (Google) / 適用: runbook patterns / 目的: operational excellence• API Design Patterns (JJ Geewax) / 適用: error response design / 目的: consistent error contractsTrigger:Use when documenting API errors, creating error catalogs, writing troubleshooting guides,designing runbooks, standardizing error responses, improving error discoverability.

Python language expertise for writing idiomatic, production-quality Python code. Use for Python development, type hints, async patterns, testing with pytest, packaging, and following PEP 8 standards. Triggers: python, py, pytest, pep8, typing, asyncio, poetry, uv, pyproject.

Apply consistent documentation standards and style guidelines when creating, reviewing, or improving project documentation (README, architecture docs, guides, references). This skill should be used when writing new documentation, reviewing existing docs for style consistency, or when users request documentation improvements or style guide compliance checks.

構造化出力を設計・生成・検証するためのスキル。JSON/YAML/CSV/Markdownなどの機械可読な出力を、用途と受け手に合わせて最小の仕様で定義し、一貫性と再利用性を確保する。Anchors:• JSON Schema / 適用: 出力スキーマ定義 / 目的: 型・必須項目の明確化• RFC 8259 (JSON) / 適用: JSON構文 / 目的: 互換性の担保• RFC 4180 (CSV) / 適用: CSV出力 / 目的: 区切りとエスケープの標準化Trigger:Use when designing or validating structured outputs, schema-driven responses, or machine-readable reports.structured output, JSON schema, CSV, YAML, markdown table, response format

This skill enables Claude to automatically check for HIPAA (Health Insurance Portability and Accountability Act) compliance issues in codebases, infrastructure configurations, and documentation. It leverages the hipaa-compliance-checker plugin to identify potential violations related to data privacy, security, and access controls. Use this skill when the user explicitly requests to "check HIPAA compliance", "scan for HIPAA violations", "assess HIPAA readiness", or similar phrases related to HIPAA audits and security best practices. It is useful for projects handling protected health information (PHI) and requiring adherence to HIPAA regulations.

Critical rules and best practices for working with markdown files.

Comprehensive guide for creating React components in the squared package and squareone app. Use this skill when creating new components, setting up component structure, implementing CSS Modules styling, writing Storybook stories, or setting up component tests. Covers TypeScript patterns (type vs interface, no React.FC), CSS Modules with design tokens, compound component patterns, Storybook integration, and vitest testing.

Use when the user asks to generate comprehensive feature documentation with verified test cases, create feature README with code evidence, or document a complete feature with test verification. Triggers on keywords like "feature documentation", "document feature", "comprehensive docs", "feature README", "test verification", "verified documentation".

Interact with Jira and Confluence via REST API - search, create, update issues and pages

Use when updating specifications, comparing branches, or ensuring documentation reflects current implementation.

Use this still to write reports.

TDD for process documentation - test with subagents before writing, iterate until bulletproof