Technical Writing

Apply Single Responsibility Principle when writing code. Keep modules focused, cohesive, and loosely coupled. Guide splitting classes with too many methods. Ensure code is reusable and testable.

Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation

Comprehensive testing workflows for Practice Hub including Vitest configuration, tRPC router testing, multi-tenant validation, Better Auth flows, and component testing. Use for writing tests, validating multi-tenant isolation, and ensuring production readiness.

Expert direct mail marketing strategist for writing compelling copy, designing high-converting mail pieces, and developing measurement strategies. Use when planning direct mail campaigns, writing mailer copy, designing postcards/letters, or measuring campaign effectiveness with incremental lift analysis.

画面ID（SAPP-CTG-030 など）から仕様・ワイヤーフレーム・Figma ノードを特定し、関連ドキュメントや画面遷移を横断して確認したいときに使います。docs/2-requirements/24-画面一覧.csv・23-画面設計.md・assets/*.svg・figma・docs/3-external/31-画面遷移図.md を参照して要件を整理する用途を想定しています。

Systematic documentation audit that validates every documentation claim against code and identifies undocumented features - executable as a repeatable Claude Code skill (project)

Generate comprehensive Pest test suites for Laravel projects including tests for controllers, services, Livewire components, commands, jobs, and models with proper describe blocks for organization, mocking setup, happy path and failure scenarios, RefreshDatabase trait, and coverage for all public methods. Use this skill when creating test files for new features, adding test coverage for controllers or services, writing tests for API endpoints, testing Livewire components, ensuring proper test structure with beforeEach and describe blocks, implementing mocking strategies, or writing dataset-driven tests. This skill applies when working on files in tests/Feature/ or tests/Unit/ directories, creating Pest test files, or ensuring comprehensive test coverage.

Guide through RED phase - writing failing tests and verifying failures

WasteWise Complete Analysis with automated regulatory compliance research and LLM Judge validation. Includes all standard analysis features PLUS automated ordinance research, compliance checklists, and quality-scored evaluation. Use when you need both waste analysis AND regulatory compliance documentation.

Core software engineering principles including DRY, SOLID, KISS, and YAGNI for writing maintainable and scalable code

Proactively analyzes Parquet file operations and suggests optimization improvements for compression, encoding, row group sizing, and statistics. Activates when users are reading or writing Parquet files or discussing Parquet performance.

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

Generate comprehensive handoff documentation optimized for AI agent takeover by analyzing project structure, design docs, and codebase

Complete GitHub workflow from commit to PR including conventional commits, branch management, pre-push quality checks, PR creation with gh CLI, and wiki synchronization. Use when creating commits, ...

Use the MIDI Markdown Compiler (mmdc) CLI for compiling MMD to MIDI, validating syntax, real-time playback with TUI, exporting to different formats (JSON, CSV, table), and managing device libraries. Use when the user wants to compile, validate, play, inspect MMD files, or work with device libraries.

Feature에 대한 spec 문서를 docs 폴더에 생성합니다. 요구사항, 시나리오, 기술 설계를 포함한 표준 형식을 제공합니다.

Search Practice Hub documentation for architecture, API reference, database schema, integrations, and implementation patterns. Triggers when user asks about multi-tenancy, authentication, tRPC routers, database, Better Auth, pricing calculator, Client Hub, Proposal Hub, Admin Panel, Client Portal, design system, integrations (LEM Verify, Gemini AI, DocuSeal, S3), or implementation patterns.

Fundamental reading and writing capability for the OCTAVE format. Inject this to give an agent basic structural competence without the overhead of full architectural specifications. Triggers on: octave format, write octave, octave syntax, structured output.

Use when reviewing design documents, technical specifications, or architecture docs before implementation planning. Performs exhaustive analysis to ensure the design is specific enough to create a detailed, coherent, and actionable implementation plan without hand-waving or ambiguity.

Component style templates and BEM naming for vehicle insurance platform. Use when styling Vue components, implementing BEM classes, creating responsive layouts, or writing scoped CSS. Keywords: BEM naming, component styles, KpiCard, FilterPanel, scoped CSS, responsive design, card styles, button styles, form controls.