npx claudepluginhub levifig/loaf --plugin loafWant just this skill?
Then install: npx claudepluginhub u/[userId]/[slug]
Establishes code quality, commit conventions, documentation standards, and security patterns.
This skill is limited to using the following tools:
references/code-review.mdreferences/code-style.mdreferences/commits.mdreferences/debugging.mdreferences/diagrams.mdreferences/documentation-review.mdreferences/documentation.mdreferences/hypothesis-tracking.mdreferences/observability.mdreferences/permissions.mdreferences/production-readiness.mdreferences/review.mdreferences/security-review.mdreferences/security.mdreferences/tdd.mdreferences/test-debugging.mdreferences/verification.mdscripts/check-changelog-format.shscripts/check-commit-msg.shscripts/check-python-style.pyCode Standards
Engineering foundations for consistent, secure, and well-documented code.
Contents
- Topics
- Available Scripts
- Critical Rules
- Naming Conventions
- Commit Types
- Test Patterns
Topics
| Topic | Reference | Use When |
|---|---|---|
| Code Style | references/code-style.md | Writing Python/TypeScript code, naming variables |
| Commits | references/commits.md | Writing commit messages, creating PRs, branching |
| Diagrams | references/diagrams.md | Creating Mermaid diagrams, visualizing architecture |
| Documentation | references/documentation.md | Writing ADRs, API docs, changelogs |
| Security | references/security.md | Threat modeling, managing secrets, compliance checks |
| Debugging | references/debugging.md | Systematically debugging issues with hypotheses |
| Hypothesis Tracking | references/hypothesis-tracking.md | Managing multiple hypotheses during investigation |
| Test Debugging | references/test-debugging.md | Fixing flaky tests, isolation issues, state pollution |
| TDD | references/tdd.md | Writing tests first, red/green/refactor cycle |
| Verification | references/verification.md | Verifying work before claiming done |
| Code Review | references/code-review.md | Requesting or receiving code reviews |
| Permissions | references/permissions.md | Configuring tool allowlists, sandbox, agent permissions |
Available Scripts
| Script | Usage | Description |
|---|---|---|
scripts/check-commit-msg.sh | check-commit-msg.sh <file> | Validate commit message format |
scripts/check-python-style.py | check-python-style.py <dir> | Check Python style (type hints, docstrings) |
scripts/check-test-naming.sh | check-test-naming.sh <dir> | Check test file/function naming |
scripts/validate-adr.py | validate-adr.py <file> | Validate ADR structure |
scripts/check-changelog-format.sh | check-changelog-format.sh <file> | Check micro-changelog format |
scripts/check-secrets.sh | check-secrets.sh <dir> | Scan for hardcoded secrets |
scripts/validate-compliance.py | validate-compliance.py <file> | Validate security checklist completion |
Critical Rules
Always
- Use type hints on all public functions
- Write atomic commits (one logical change)
- Use imperative mood in commit messages
- Validate inputs at trust boundaries
- Log security events (without secrets)
- Include micro-changelog at document bottom
Never
- Commit secrets, passwords, or API keys
- Document APIs before they ship
- Use bare
except:clauses - Force push to main/master
- Log sensitive data or stack traces to users
- Skip commit signing without explicit permission
Naming Conventions
| Context | Python | TypeScript |
|---|---|---|
| Files | snake_case.py | PascalCase.tsx (components) |
| Functions | snake_case | camelCase |
| Classes | PascalCase | PascalCase |
| Constants | UPPER_SNAKE | UPPER_SNAKE |
| Tests | test_<unit>_<scenario>_<result> | describe/it blocks |
Commit Types
| Type | Use For | Version Impact |
|---|---|---|
feat | New features | Minor bump |
fix | Bug fixes | Patch bump |
refactor | Code restructuring | None |
docs | Documentation only | None |
test | Test additions/updates | None |
chore | Maintenance, deps | None |
perf | Performance improvements | Patch bump |
Test Patterns
Scenario-based fixture naming:
*_perfect- Complete, valid data (happy path)*_degraded- Partial data, quality issues*_chaos- Edge cases, malformed data
Coverage target: 70% minimum across all components.
Similar Skills
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.