backend-dev-guidelines
Opinionated 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.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill backend-dev-guidelinesOverall
score
72%
Validation for skill structure
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid architectural guidelines skill with strong actionability through concrete code examples and clear anti-patterns. However, it's somewhat verbose with unnecessary framing, and the BFRI scoring system adds complexity without clear integration into the workflow. The skill would benefit from tighter prose and better progressive disclosure to external references.
Suggestions
Remove the persona framing ('You are a senior backend engineer') and introductory paragraphs - Claude doesn't need this context
Either integrate BFRI into a concrete workflow checkpoint (e.g., 'Before implementing, calculate BFRI and document in PR') or move it to a separate reference file
Add explicit validation steps for risky operations like database migrations or schema changes with feedback loops
Split detailed patterns (Sentry setup, testing examples, Prisma transaction handling) into linked reference files to reduce main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary framing ('You are a senior backend engineer', 'This skill defines how backend code must be written') and explanatory text that Claude doesn't need. The BFRI section adds significant length for a concept that could be condensed. | 2 / 3 |
Actionability | Provides concrete, executable TypeScript/Express code examples throughout. The patterns shown (BaseController, Zod validation, asyncErrorWrapper, DI) are copy-paste ready with clear do/don't comparisons. | 3 / 3 |
Workflow Clarity | The layered architecture flow is clear (Routes → Controllers → Services → Repositories), but lacks explicit validation checkpoints for risky operations. The checklist at the end is helpful but doesn't provide feedback loops for error recovery during development. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one large file. References to other skills (error-tracking, database-verification) are mentioned but not linked. Complex topics like Sentry setup or testing patterns could be split into separate reference files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
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.