backend-dev-guidelines

Comprehensive backend development guide for Node.js/Express/TypeScript microservices. Use when creating routes, controllers, services, repositories, middleware, or working with Express APIs, Prisma database access, Sentry error tracking, Zod validation, unifiedConfig, dependency injection, or async patterns. Covers layered architecture (routes → controllers → services → repositories), BaseController pattern, error handling, performance monitoring, testing strategies, and migration from legacy patterns.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/backend-dev-guidelines/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with actionable code and good progressive-disclosure navigation, but it pads in content Claude already knows and lacks validation checkpoints for destructive database/migration workflows. The referenced detail files are signaled but absent from the bundle.

Suggestions

Remove the HTTP status codes table and the 'Skill Status / Line Count' footer; Claude already knows HTTP codes and self-validation footers add no behavioral value.

Add explicit validation/verification steps to the new-feature and microservice checklists (e.g. run tests, run Prisma migrate status, verify Sentry events captured) so destructive database and migration work has feedback loops.

Either include the 11 referenced files in the bundle (references/ or sibling directory) or drop the dangling links, so progressive-disclosure references resolve to real material.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tight code snippets, but includes padding Claude does not need: a generic HTTP status codes table and a meta 'Skill Status / Line Count / Progressive Disclosure ✅' footer that earn no tokens.	3 / 5
Actionability	Concrete, mostly copy-paste-ready code for route delegation, BaseController, Sentry capture, unifiedConfig, Zod, repository and test patterns, with only minor gaps (e.g. the test snippet is a stub lacking setup).	4 / 5
Workflow Clarity	Checklists provide a rough sequence for new features and microservices, but there are no explicit validation/verification checkpoints; given database (Prisma) and legacy-migration operations, the destructive-ops cap holds this at 3.	3 / 5
Progressive Disclosure	A clear overview with a navigation table and 11 one-level-deep, well-signaled references, but none of the referenced files actually exist in the bundle (no references/ directory), a real organization gap.	4 / 5
	Total	14 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A dense, well-constructed description that covers what the skill does and when to use it with concrete, stack-specific trigger terms. Minor room to tighten the long enumeration and add synonyms, but it clearly distinguishes itself from generic backend skills.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities — 'creating routes, controllers, services, repositories, middleware', 'Prisma database access, Sentry error tracking, Zod validation, unifiedConfig, dependency injection, async patterns' — plus 'layered architecture', 'BaseController pattern', 'testing strategies' giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' ('Comprehensive backend development guide... Covers layered architecture...') and 'when' ('Use when creating routes, controllers, services...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong coverage of natural developer phrases ('routes', 'controllers', 'Prisma', 'Zod validation', 'Sentry error tracking', 'middleware') that a user would actually say, but lacks synonyms or file extensions to reach full comprehensiveness.	4 / 5
Distinctiveness Conflict Risk	Stack-specific markers (Prisma, Sentry, Zod, unifiedConfig, BaseController, Express/TypeScript microservices) carve a clear niche with minimal conflict, but the broad backend scope leaves minor overlap risk with general web-dev skills.	4 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 24 missing	Warning

	Total	15 / 16 Passed

Repository: diet103/claude-code-infrastructure-showcase
Path: .claude/skills/backend-dev-guidelines/SKILL.md
Commit: 07f75ce

Reviewed: ~13 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.