engineering-standards

Enforce engineering standards for code, APIs, frontend, testing, and deployment.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/redbananastudios/ai-library --skill engineering-standards-redbananastudios
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineering-standards
Source: https://github.com/redbananastudios/ai-library/tree/main/generated/claude/skills/engineering-standards
Command: npx skills add https://github.com/redbananastudios/ai-library --skill engineering-standards-redbananastudios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

engineering-standards eliminates inconsistent code quality and architecture drift by turning team expectations into enforceable constraints that must be followed on every commit and file.

Core Features & Use Cases

  • Architecture and layering guardrails: Keeps controllers as routing-only, centralizes business logic in dedicated handlers/services, and prevents business logic from directly calling side-effectful concerns like messaging, notifications, and audit logging.
  • API and data contract consistency: Enforces a uniform success/failure envelope, structured error codes, authenticated-by-default behavior, and response-shape stability for live routes (using v2 alongside v1).
  • Cross-platform engineering hygiene: Standardizes logging structure and PII handling, frontend UX patterns (loading/error/empty states, table behavior, themed date/number input rules), and pragmatic workflow/testing/deployment rules to reduce regressions.
  • Tech-stack-specific idioms: Applies tailored rules for C#/.NET, Node.js/TS, Go, and Python based on detected ecosystem files.

Quick Start

Instruct your AI agent to apply the engineering-standards rules when reviewing or generating changes for a repository, ensuring every proposed file follows the required architecture, API envelope, logging, UX, and workflow constraints.

Frequently Asked Questions about engineering-standards

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

FAQPage Schema
How do I enforce architecture layering and keep controllers free of business logic?▼

To enforce architecture layering, you must keep controllers strictly for routing, centralize business logic in dedicated handlers or services, and prevent logic from directly calling side-effectful concerns like messaging, notifications, and audit logging.

Can I standardize API response envelopes and error codes across different tech stacks?▼

Yes, you can standardize API response envelopes across different tech stacks by enforcing a uniform success or failure envelope, structured error codes, authenticated-by-default behavior, and response-shape stability for live routes.

What is the best way to maintain stable API contracts when modifying live routes?▼

The best way to maintain stable API contracts for live routes is to preserve response-shape stability by deploying new versions alongside existing ones, such as introducing v2 routes while keeping v1 intact.

Does this engineering standards tool support Go and Python codebases?▼

Yes, this engineering standards tool supports Go and Python codebases by applying tailored rules based on detected ecosystem files, alongside support for C#/.NET and Node.js/TS environments.

How do I standardize structured logging and PII boundaries in Node.js or TS projects?▼

To standardize structured logging and PII boundaries in Node.js or TS projects, you apply cross-platform engineering hygiene rules that define strict logging structures and protect sensitive PII data.

What frontend UI guardrails are enforced for tables, inputs, and loading states?▼

Frontend UI guardrails enforce standardized UX patterns including loading, error, and empty states, table behavior consistency, and themed date and number input rules to reduce regressions.