Joncik91

This skill should be used when the user asks to "generate tests", "write unit tests", "analyze test coverage", "scaffold E2E tests", "set up Playwright", "configure Jest", "implement testing patterns", or "improve test quality".

This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan for scalability", "make technical decisions", or "review system design".

This skill should be used when the user asks to "design REST APIs", "optimize database queries", "implement authentication", "build microservices", "review backend code", "set up GraphQL", "handle database migrations", or "load test APIs".

Use when reviewing pull requests, analyzing code quality, identifying issues, or generating review checklists. Covers TypeScript, JavaScript, Python, Go, Swift, and Kotlin.

Use when building React components, optimizing performance, analyzing bundle sizes, scaffolding projects, implementing accessibility, reviewing frontend code quality, performing visual overhauls, or designing UI/UX systems.

Use when the user asks about Claude Code best practices, how to write agents, how to use hooks, how to manage context, or how to work effectively with Claude Code's native systems

Use when receiving feedback on code you implemented, responding to reviewer comments, deciding which review suggestions to implement, or pushing back on incorrect review feedback.

Use when setting up CI/CD pipelines, deploying applications, managing cloud infrastructure (AWS, GCP, Azure), implementing monitoring, containerizing services, or automating deployments with infrastructure as code.

Unified inception — distill a vague vision into a First-Principles spec with action/verification steps, then lock it as the active spec.

State-aware spec executor — read the active spec, run the next step's action, gate on its verification, retry once on fail, advance the scratchpad. Halts on any unrecoverable failure with full negative knowledge.

Context-aware code review that adapts its strategy based on what changed

Records the structure of conversations where ideas evolve, branch, get rejected, pivot, or combine. Saves each structural shift as a node in a local JSON tree the user can browse on demand. Zero network access, zero external dependencies. Covers proposals, rejections, pivots, and merges with cross-tree concept linking.

Trigger skill for rapid repository onboarding. Activates when the user wants to understand an unfamiliar codebase. Trigger phrases include "onboard me to this repo", "what does this codebase do", "give me a map of this repo", "ramp up on this project", "first time in this repo", "help me understand this codebase", "orient me to this project", "I'm new to this codebase", "what should I know about this repo".

Pragma watches every Edit/Write of a test file and blocks the gamed ones. Three tiers — AST, coverage, and an LLM judge. Write tests that actually verify behavior.