Loading...
Loading...
Found 25 Skills
Go Development Guidelines, including naming conventions, error handling, concurrent programming, testing specifications, etc.
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
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 writing, fixing, editing, reviewing, or refactoring any Python code. Enforces Robert Martin's complete Clean Code catalog—naming, functions, comments, DRY, and boundary conditions.
. Use when writing tests, reviewing test coverage, or setting up testing.
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
Reviews code for quality, security, tests, and project standards (PEP 8, type hints, VERSION, Docker, funcoes.md). Use when reviewing pull requests, code changes, or when the user asks for a code review or quality check.
Use when symfony functional tests
Use when symfony e2e panther playwright
Shared Go best practices for LlamaFarm CLI. Covers idiomatic patterns, error handling, and testing.
Everything you need to know to build, test and review Home Assistant Integrations. If you're looking at an integration, you must use this as your primary reference.
Use when symfony tdd with phpunit