rileyhilliard/claude-essentials

writer

Writing style and tone guide for human-sounding content. Use when writing documentation, READMEs, commit messages, PR descriptions, blog posts, LinkedIn posts, social media content, or any user-facing content.

원문 언어: 영어

executing-plans

Executes implementation plans directly with a verification gate and conditional code review. Use when carrying out a written plan step by step; delegates to subagents only for large, genuinely independent, parallelizable work.

원문 언어: 영어

fixing-flaky-tests

Diagnose and fix tests that pass in isolation but fail when run concurrently. Covers shared state isolation, resource conflicts, and timing-based flakiness.

원문 언어: 영어

optimizing-performance

Measure-first performance optimization that balances gains against complexity. Use when addressing slow code, profiling issues, or evaluating optimization trade-offs.

원문 언어: 영어

post-mortem

Review a completed session to extract actionable improvements. Identifies DX friction, documentation gaps, architectural confusion, anti-patterns, process failures, and skill/config improvements. Uses progressive disclosure for targeted investigation types.

원문 언어: 영어

strategy-writer

Produces executive-quality strategic documents in The Economist/HBR style. Use when writing strategy memos, market analysis, business cases, customer research reports, or any document for Product, Design, and Business leaders. Customer-led, evidence-based,…

원문 언어: 영어

systematic-debugging

Debugging framework that finds root causes before proposing fixes. Use when investigating bugs, errors, unexpected behavior, failed tests, or when previous fixes haven't worked.

원문 언어: 영어

design

Enforces precise, minimal design for dashboards and admin interfaces. Use when building SaaS UIs, data-heavy interfaces, or any product needing Jony Ive-level craft.

원문 언어: 영어

handling-errors

Prevents silent failures and context loss in error handling. Use when writing try-catch blocks, designing error propagation, reviewing catch blocks, or implementing Result patterns.

원문 언어: 영어

writing-tests

Writes behavior-focused tests using Testing Trophy model with real dependencies. Use when writing tests, choosing test types, or avoiding anti-patterns like testing mocks.

원문 언어: 영어

managing-databases

Guides database architecture for PostgreSQL, DuckDB, Parquet, PGVector, and Neo4j. Use when designing schemas, choosing storage strategies, optimizing queries, configuring vector or graph workloads, or diagnosing performance issues.

원문 언어: 영어

managing-pipelines

Guides GitHub Actions CI/CD architecture, security hardening, and deployment strategies. Use when designing workflows, securing supply chains, optimizing build performance, or configuring deployments.

원문 언어: 영어

planning-products

Defines product features from a PM perspective (JTBD, competitive research, scope negotiation) before technical planning. Use when scoping features, writing product specs, defining user problems, or choosing what to build.

원문 언어: 영어

structuring-articles

Selects and applies journalistic story structures (WSJ Formula, Inverted Pyramid, Hourglass, Tick-Tock). Use when writing or outlining articles, blog posts, essays, or any narrative prose longer than a few paragraphs.

원문 언어: 영어

writing-sql

Staff+ DBA SQL patterns targeting what Claude's defaults miss - multi-column statistics, operator classes, keyset pagination, silent performance anti-patterns. Use when writing complex SQL, reviewing queries, adding indexes, or optimizing slow queries.

원문 언어: 영어

architecting-systems

Guides clean, scalable system architecture during the build phase. Use when designing modules, defining boundaries, structuring projects, managing dependencies, or preventing tight coupling and brittleness as systems grow.

원문 언어: 영어

visualizing-with-mermaid

Creates professional Mermaid diagrams with semantic styling and visual hierarchy. Use when creating flowcharts, sequence diagrams, state machines, class diagrams, or architecture visualizations.

원문 언어: 영어