Skill Creator
jagreehal
17 published skills · 0 GitHub stars across the catalog. View on GitHub ↗
testing-strategy
Test pyramid approach with unit, integration, and load tests. DI enables testability. Use vitest-mock-extended for typed mocks.
fn-args-deps
Enforce the fn(args, deps) pattern: functions over classes with explicit dependency injection
result-types
Never throw for expected failures. Use Result<T, E> types with explicit error handling and workflow composition.
resilience
Add retry, timeout, and circuit breaker patterns at the workflow level. Business functions stay clean.
config-management
Validate config at startup, secrets in memory only. Never read config during requests, never store secrets in env vars. Use node-env-resolver for multi-source config.
pattern-enforcement
Enforce architectural patterns with ESLint rules. Block infra imports, enforce object params, prevent server/client leaks.
code-flow-analysis
Trace code execution path before implementing fixes. Forces understanding of fn(args, deps) flows, Result types, and workflow composition. Prevents guessing by requiring file:line references and execution diagrams.
design-principles
Software design beyond syntax. Fail-fast over fallbacks, explicit over implicit, composition over inheritance. Integrates with fn(args, deps) and Result type patterns.
critical-peer
Professional skepticism with pattern enforcement. Verify before agreeing, challenge violations, propose instead of asking. Concise output, research before asking, answer questions literally.
strict-typescript
Enforce patterns with TypeScript beyond strict:true. Include noUncheckedIndexedAccess, erasableSyntaxOnly, ts-reset, and type-fest.
tdd-workflow
Test-driven development with Result types. Red-green-refactor cycles using vitest-mock-extended, explicit deps mocking, and Result assertions.
session-continuity
Persist task state across sessions using .claude/ files. Resume work with 'continue'. Never use TodoWrite - use tasks.md, requirements.md, session.md instead.
validation-boundary
Validate at the boundary with Zod schemas and branded types. Business functions trust validated input.
debugging-methodology
Evidence-based debugging. Instrument before guessing, trace before theorizing. Uses observability patterns to make failures visible and systematic.
performance-testing
Load testing, chaos engineering, and performance validation. Prove your system works under pressure with k6, trace correlation, and progressive load profiles.
storybook-journeys
Create Storybook "user journey" storyboards for React apps (page/screen stories, MSW API mocking, interaction play functions, and optional Storybook test-runner setup). Use when the user wants Storybook demos of flows (not just atomic components), e.g., signup/login/checkout, with mocked APIs and scripted interactions.
observability
Make functions observable with trace() wrapper, structured logging (Pino), and OpenTelemetry. Observability is orthogonal to business logic.