Claude Skills by johanthoren

Language-agnostic code standards for writing clean, maintainable code. Covers modular design, functional patterns, error handling, security, and testing. Make sure to use this skill whenever writing, refactoring, or reviewing any code, even for quick fixes, prototypes, or single-file changes. This is the baseline for all code quality. Language-specific skills, if present, may override these defaults.

Handle engineering work in an active jeff project and drive its tracked task pipeline. Use when the Chef addresses Jeff, mentions jeff/cook, asks to set up, initialize, turn on, deinit, validate, or check status/tasks; runs `cook`, `cook <taskId>`, or `cook on <ref>`; wants to start or resume a task; asks to implement/build a plan (not merely read/review it); or describes real engineering work in an active jeff project. Ordinary intent starts Explore and assess→forks before durable writes (ad...

Adversarial security auditing workflow for source changes. Make sure to use this skill whenever reviewing code before merge, hunting for vulnerabilities, auditing dependencies, or assessing security exposure of new features, even if the user doesn't explicitly ask for a security review. Includes OWASP-focused scans, dependency-audit attempts, coverage accounting, and strict pass/block recommendations.

Language-agnostic testing standards for writing effective tests. Covers test structure, what to test, mocking, and coverage goals. Make sure to use this skill whenever writing tests, doing TDD, reviewing test coverage, or when code changes should have tests added; testing standards apply to all code, not just dedicated test tasks. Language-specific skills, if present, may override these defaults.