backend-dev-guidelines
tessl i github:sickn33/antigravity-awesome-skills --skill backend-dev-guidelinesOpinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod validation, unifiedConfig, Sentry error tracking, async safety, and testing discipline.
Review Score
64%
Validation Score
11/16
Implementation Score
65%
Activation Score
50%
Generated
Validation
Total
11/16Score
Passed| Criteria | Score |
|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') |
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow |
Implementation
Suggestions 3
Score
65%Overall Assessment
This is a solid, actionable backend development skill with clear architectural rules and executable code examples. Its main weaknesses are moderate verbosity (BFRI section, redundant anti-patterns), lack of explicit validation workflows for risky operations, and monolithic structure that could benefit from splitting detailed patterns into reference files.
Suggestions
- Remove or significantly condense the BFRI section - the checklist at the end already captures the key validation points more concisely
- Add explicit validation/verification steps for risky operations like database migrations or schema changes (e.g., 'Run prisma validate before applying migrations')
- Split detailed patterns (Sentry setup, Prisma repository examples, test patterns) into separate reference files and link from the main skill
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | Generally efficient but includes some unnecessary framing ('You are a senior backend engineer', 'This skill defines how backend code must be written') and the BFRI section adds complexity that Claude could derive from simpler principles. The anti-patterns section largely restates rules already covered. |
Actionability | 3/3 | Provides concrete, executable TypeScript code examples throughout - BaseController pattern, Zod validation, DI constructors, asyncErrorWrapper usage, and test structure. Examples are copy-paste ready and demonstrate both correct and incorrect patterns. |
Workflow Clarity | 2/3 | The layered architecture flow is clear (Routes → Controllers → Services → Repositories), but the skill lacks explicit validation checkpoints for multi-step operations. The checklist at the end is helpful but doesn't integrate into a workflow with feedback loops for error recovery. |
Progressive Disclosure | 2/3 | Content is well-organized with clear sections and tables, but it's monolithic - all content is inline rather than appropriately split. References to other skills (Section 12) are mentioned but the skill itself could benefit from splitting detailed patterns (e.g., Sentry setup, Prisma patterns) into separate reference files. |
Activation
Suggestions 2
Score
50%Overall Assessment
The description excels at specificity and distinctiveness by naming concrete patterns and a precise tech stack, making it clearly identifiable. However, it critically lacks explicit trigger guidance ('Use when...') which would help Claude know when to select this skill, and could benefit from more natural user-facing keywords beyond technical jargon.
Suggestions
- Add a 'Use when...' clause specifying triggers like 'building Express APIs', 'creating Node.js microservices', 'setting up TypeScript backend projects', or 'implementing repository patterns'
- Include natural language variations users might say: 'REST API', 'backend API development', 'server-side Node', 'Express middleware', 'API architecture'
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 3/3 | Lists multiple specific concrete actions and patterns: 'layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod validation, unifiedConfig, Sentry error tracking, async safety, and testing discipline' - these are all concrete, named concepts. |
Completeness | 1/3 | Clearly answers 'what' (backend development standards covering specific patterns) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. |
Trigger Term Quality | 2/3 | Contains good technical keywords (Node.js, Express, TypeScript, Prisma, Zod, Sentry) that developers would use, but missing common variations like 'API development', 'REST', 'backend API', or 'server-side' that users might naturally say. |
Distinctiveness Conflict Risk | 3/3 | Very specific niche: 'Node.js + Express + TypeScript microservices' with named patterns like 'BaseController', 'Prisma repositories', and 'unifiedConfig' make this highly distinguishable from generic coding or other backend skills. |
- Last updated
- Created
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.