skills.rest
konstantinos-malavazos
konstantinos-malavazosCOMMUNITY
Explore all skills by this author →
GitHub

<layer>-engineering-standards

Generates per-layer coding and review standards scoped to a single language or stack layer.

2|Updated Jul 24, 2026
Search Tags:#template#code review#best practices#coding standards#style guide#multi-layer#severity model
One-click install
npx skills add https://github.com/konstantinos-malavazos/claude-code-playbook --skill layer-engineering-standards-konstantinos-malavazos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: <layer>-engineering-standards
Source: https://github.com/konstantinos-malavazos/claude-code-playbook/tree/main/templates/skills/engineering-standards
Command: npx skills add https://github.com/konstantinos-malavazos/claude-code-playbook --skill layer-engineering-standards-konstantinos-malavazos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams running multi-layer codebases often load one monolithic style guide into every review, wasting context on irrelevant rules. This Skill template generates a separate, layer-scoped engineering standard (schema, backend, frontend) so each specialist agent or reviewer only carries the rules that apply to its language and layer. ## Core Features & Use Cases - Layer-Scoped Standards: Produces one standards document per layer/language (e.g. schema-standards, backend-standards, frontend-standards) with no cross-layer rule leakage. - Shared Severity Model: Defines a common [BLOCKER] / [MAJOR] / [MINOR] / [NIT] severity scale so review feedback is classified consistently across all layers. - Structured Rule Sections: Covers correctness and design, language-specific rules, testing expectations, security and logging, and build correctness before hand-off. - Use Case: A team adopting Claude Code runs /adapt-to-stack, which generates a backend-standards skill for their C# API layer and a schema-standards skill for their SQL layer, so the backend specialist never loads SQL index rules. ## Quick Start Ask the AI to generate the engineering standards skill for your backend layer using this template, filling in the language-specific rules for your stack.

Frequently Asked Questions about <layer>-engineering-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create separate coding standards for each layer of my stack?▼

Run the /adapt-to-stack flow, which generates one standards skill per layer into the repo's .claude/skills/ directory, named per layer such as backend-standards or schema-standards. Each generated skill contains only the rules for its own language and layer.

What severity levels should a code review standard define?▼

This template defines four shared levels: [BLOCKER] for correctness, security, or data loss issues that must be fixed before merge; [MAJOR] for design and maintainability problems; [MINOR] for readability issues; and [NIT] for optional style points.

Can I use my existing company style guide with this template?▼

Yes. The template includes a vendoring note instructing you to paste an authoritative in-house standard verbatim and pin it to a specific commit, so the generated skill matches your source of truth exactly.

Why split engineering standards by layer instead of one document?▼

Splitting keeps each skill cheap to load because a schema specialist never carries frontend rules and a frontend specialist never carries SQL index rules. The guidance is to split content by language and layer rather than trimming it.

When is this engineering standards template not needed?▼

It is unnecessary for single-layer projects or stacks where one language covers the whole codebase, since there is no cross-layer rule leakage to prevent. It targets teams running multi-layer chains with per-layer specialist agents.

Related Skills

Explore More Software Engineering Skills→
j7-devj7-dev
1

analyze

Scan project directories to identify technology stacks and generate SKILL.md and Copilot instruction files.

Community
Advanced
mgkyawzayyamgkyawzayya
1

code-review-checklist

Validate Laravel and React code changes against project standards.

Community
Intermediate
rogerzntsrogerznts
1

anvil-implement

Implements work from specs or tickets using TDD and code review.

Community
Basic
sunLeeesunLeee

quality-ruff

Configure Ruff linting and formatting in pyproject.toml for Python projects.

Community
Intermediate