Stats
Actions
Tags
Blue Corvid Group / Jason's engineering standards for any code work under ~/code. Use BEFORE writing, modifying, reviewing, refactoring, or architecting code in any repo. Routes to three on-demand references — principles (always relevant), stack (architecture/tech decisions only), testing (when adding or touching tests). Read only the reference the task needs; do not load all three by default.
How this skill is triggered — by the user, by Claude, or both
Slash command
/engineering-guidelines:engineering-guidelinesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Source of truth for how we build. Three reference files, loaded on demand — read the one the task calls for, not all of them.
Source of truth for how we build. Three reference files, loaded on demand — read the one the task calls for, not all of them.
| Read this | When |
|---|---|
principles.md | Default for any real code work: principles (YAGNI/KISS/DRY/composition/explicit/colocation), separation of concerns, layered architecture, working with AI agents, security hard-rules, decision frameworks. Read once per session the first time engineering work starts. |
stack.md | ONLY when making a tech-stack or architecture decision — picking a framework/library for a new project, choosing between two libraries for a core concern, or committing to a hard-to-reverse pattern. This file requires a fresh landscape check (current releases, what engineers are reaching for now); that research is token-expensive, so do not open it for routine work. |
testing.md | When writing, changing, or reviewing tests, or finishing a feature (smoke test + coverage expectations). |
Do not restate these files back to the user. Apply them.
Hard rules that always apply (full detail in principles.md → Security): never commit secrets; gitignore .env* before the first commit; never expose API keys client-side. These also live in global CLAUDE.md — that file owns the secrets incident-response procedure; this skill defers to it.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub blue-corvid-group/engineering-team-guidelines --plugin engineering-guidelines