Technical Writing

Complete Git expertise system for ALL git operations. PROACTIVELY activate for: (1) ANY Git task (basic/advanced/dangerous), (2) Repository management, (3) Branch strategies and workflows, (4) Conflict resolution, (5) History rewriting/recovery, (6) Platform-specific operations (GitHub/Azure DevOps/Bitbucket), (7) Advanced commands (rebase/cherry-pick/filter-repo). Provides: complete Git command reference, safety guardrails for destructive operations, platform best practices, workflow strategies, reflog recovery techniques, and expert guidance for even the most risky operations. Always asks user preference for automatic commits vs manual control.

Linear issue-tracked development workflow. Auto-activates when starting work on issues, creating branches, changing status, writing comments, or creating PRs.

This skill should be used when writing official conference-style reviews for research papers as if from a top-tier systems conference reviewer. Use when the author wants a realistic, formal peer review with scores, strengths, weaknesses, and detailed feedback following standard conference review formats.

Review existing CSS against established Tailwind + semantic component patterns, checking naming, dark mode, tests, and documentation

Meta-skill for improving and optimizing prompts using Anthropic's prompt engineering best practices. Provides the 4-step improvement workflow (example identification, initial draft, chain of thought refinement, example enhancement), keyword registries for documentation lookup, and decision trees for improvement strategies. Use when improving prompts, optimizing for accuracy, adding chain of thought reasoning, structuring with XML tags, enhancing examples, or iterating on prompt quality. Delegates to docs-management skill for official prompt engineering documentation.

Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. All plans MUST be validated using the included validation script. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.

React best practices and anti-patterns reference. Use when writing React components, reviewing code for anti-patterns, debugging useEffect issues, optimizing performance, or deciding between state vs derived values. Covers Effects, state design, component patterns, performance, and event handling.

Use when implementing Home Assistant integration code - covers Nov 2025 best practices for config flows, coordinators, entities, async patterns, manifest, translations, and project structure. Required reading before writing any HA code.

Search and read Atlassian Confluence content.

Reference Docker and Compose documentation for configuration patterns and best practices

Write tests for JavaScript, React, PHP, and WordPress including unit tests, integration tests, and E2E tests. Use when writing tests, setting up testing frameworks, or debugging test failures.

EARS requirement pattern authoring. Use when writing requirements using EARS patterns (Ubiquitous, State-Driven, Event-Driven, Unwanted, Optional, Complex). Provides pattern templates, validation, and examples.

Generate clear conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or after completing TDD cycles.

Use when designing URL structures, slug generation, SEO-friendly URLs, redirects, or localized URL patterns. Covers route configuration, URL rewriting, canonical URLs, and routing APIs for headless CMS.

Reference FilamentPHP v4 documentation for patterns, methods, and implementation examples

Provides documentation and knowledge base for seekdb database.

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

SQLiteにおけるインデックス設計戦略の専門知識。B-Treeインデックス、部分インデックス、式インデックス、カバリングインデックスの特性と選択基準を提供。Turso + Drizzle ORM環境での実装を前提とする。Anchors:• Designing Data-Intensive Applications (Martin Kleppmann) / 適用: データモデリング・インデックス設計原則 / 目的: 体系的なインデックス戦略の確立• SQLite Documentation / 適用: B-Tree実装・クエリプランナー挙動 / 目的: SQLite特有の最適化技法の適用• Drizzle ORM / 適用: index()構文・マイグレーション / 目的: 型安全なスキーマ定義Trigger:Use when designing database indexes, analyzing query performance, optimizing read operations, evaluating index candidates, or implementing Drizzle ORM index migrations.Keywords: index, indexing, B-Tree, query performance, SQLite, Drizzle, cardinality, selectivity, covering index, partial index, expression index.

Guides SDD artifact implementation for NEW and EXISTING projects. Use for DDD glossary, context map, domain models, ADRs, user stories with acceptance criteria. For existing projects, supports gap analysis, code-to-spec reverse engineering, and phased migration. Triggers on SDD, spec-driven, artifact, glossary, context map, domain vision, ADR, legacy documentation, reverse engineering, existing project documentation, gap analysis.

Analyze existing tests to identify patterns, fixtures, and conventions before writing new tests