skills.rest
FernandoBade
FernandoBadeCOMMUNITY
Explore all skills by this author →
GitHub

staff-backend

Enforce backend coding standards across Zinero's monorepo controllers, services, repositories, and utils.

Updated Aug 23, 2026
Search Tags:#typescript#architecture#backend#governance#code-quality#reviews
One-click install
npx skills add https://github.com/FernandoBade/zinero-hack-your-expenses --skill staff-backend
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: staff-backend
Source: https://github.com/FernandoBade/zinero-hack-your-expenses/tree/main/skills/staff-backend
Command: npx skills add https://github.com/FernandoBade/zinero-hack-your-expenses --skill staff-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unifies and enforces backend coding standards within the Zinero monorepo to maintain clean architecture, strong typing, consistent patterns, and high maintainability across controllers, services, repositories, and utils.

Core Features & Use Cases

  • Enforces naming conventions, layer responsibilities, and shared contract usage across backend modules.
  • Guides code reviews, onboarding, and audits to raise overall backend quality and maintainability.
  • Provides a guardrail for documentation, error handling, and validation discipline in the backend.

Quick Start

Run a focused audit of the Zinero backend modules and implement the recommended improvements.

Frequently Asked Questions about staff-backend

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

FAQPage Schema
How do I enforce backend code quality and architecture consistency in a TypeScript monorepo?▼

Enforce backend code quality by auditing controllers, services, and repositories against staff-backend guidelines, ensuring naming consistency, layer separation, strong typing, and shared contract usage across the monorepo.

What is the best way to standardize TypeScript backend validation patterns and monetary safety practices?▼

Standardize TypeScript backend validation by applying explicit return types, JSDoc summaries, and safe monetary practices defined by repository architecture guidelines to maintain consistent and secure backend modules.

How do I audit backend layer separation and naming conventions during code reviews?▼

Audit backend layer separation during code reviews by checking controller, service, repository, and util modules against established naming conventions and architecture guidelines to raise overall maintainability.

Can I use this to guide onboarding and documentation discipline for backend TypeScript modules?▼

Yes, you can guide onboarding and documentation discipline by enforcing JSDoc summaries, explicit return types, and shared contract usage across backend TypeScript modules to ensure consistent architecture.

Does this approach work for improving error handling and validation discipline across backend services?▼

Yes, this approach works for improving error handling and validation discipline by acting as a guardrail to enforce safe monetary practices and strong typing across all backend services and utilities.

Related Skills

Explore More Software Engineering Skills→
changgengluchanggenglu

laravel-architecture

Enforce multi-layer Laravel architecture across controllers, services, repositories, and requests.

Community
Intermediate
Prompt-or-Die-LabsPrompt-or-Die-Labs
7

Type Safety Guardian

Enforce strict TypeScript typing by rejecting `any` and `unknown` misuse.

Official
Advanced
nguyenphpnguyenphp
41

lint-and-validate

Run linters, type checkers, and security audits across Node.js and Python projects.

Community
Intermediate
excattexcatt
14

audit

Execute project-specific verification rules for business logic, architecture, and naming conventions.

Community
Advanced