Loading...
Loading...
Found 22 Skills
Guide for writing tests. Use when adding new functionality, fixing bugs, or when tests are needed. Emphasizes integration tests, real-world fixtures, and regression coverage.
Perform comprehensive code reviews with best practices, security checks, and constructive feedback. Use when reviewing pull requests, analyzing code quality, checking for security vulnerabilities, or providing code improvement suggestions.
Guidelines for writing effective tests in this project
Quick reference for n8n patterns. Full docs /AGENTS.md
Shared Go best practices for LlamaFarm CLI. Covers idiomatic patterns, error handling, and testing.
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Test-Driven Development with Iron Laws enforcement. Use when writing any production code to ensure tests are written first. Includes testing-expert capabilities.
Checklists and anti-patterns for reviewing Go code. Covers API design, error handling, concurrency, interfaces, safety, performance, naming, testing, functional options, logging, and deterministic simulation testing.
Use when symfony functional tests
Use when symfony tdd with phpunit
Use when symfony api platform tests
Defines ROI-based coverage targets with critical path identification, layer-specific targets, and explicit "don't test this" guidelines. Use for "test coverage", "coverage strategy", "test priorities", or "coverage targets".