From basaltbytes-skills
Basaltbytes coding-guidelines charter — always-valid domain modeling, functional-core architecture, typed-error discipline, idempotent workflows, observability, testing through real seams, and hygiene. Use when designing or reviewing domain models, value objects, or state machines, when parsing at API/DB/env boundaries (pydantic strict, Zod, branded/newtype ids), when structuring error handling or choosing test seams and mocks, or when code shows primitive obsession, validation inside function bodies, scattered rechecks, assert/non-null narrowing, or raw payloads flowing into domain functions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/basaltbytes-skills:coding-guidelinesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The charter lives in [CODING_GUIDELINES.md](CODING_GUIDELINES.md), shipped with this
The charter lives in CODING_GUIDELINES.md, shipped with this skill — read the sections the task touches. For domain modeling, section 1 is the law: read it with its review checklist and Final check, then follow its language-mapping pointer (PYTHON.md / TYPESCRIPT.md) for the code at hand.
npx claudepluginhub basaltbytes/skills --plugin basaltbytes-skillsGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.