backend-patterns

tessl i github:sickn33/antigravity-awesome-skills --skill backend-patterns

Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.

54%

Overall

Validation — 63%

Implementation — 57%

Activation — 33%

SKILL.md

Review

Evals

Validation

63%

Warnings & errors only

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (584 lines); consider splitting into references/ and linking	Warning
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
body_steps	No step-by-step structure detected (no ordered list); consider adding a simple workflow	Warning

	Total	10 / 16 Passed

Implementation

57%

This skill provides excellent, actionable code examples covering a wide range of backend patterns with proper TypeScript implementations. However, it suffers from being a monolithic reference document that would benefit significantly from being split into focused sub-files. The lack of workflow guidance on when and how to apply these patterns together limits its practical utility.

Suggestions

Split content into separate files (e.g., API_PATTERNS.md, DATABASE_PATTERNS.md, AUTH_PATTERNS.md, CACHING.md) with a concise overview in the main SKILL.md

Add a decision tree or guidance section explaining when to use each pattern (e.g., 'Use repository pattern when you need to swap data sources')

Add validation checkpoints for database transactions and destructive operations (e.g., 'Verify transaction success before proceeding')

Remove basic patterns Claude already knows (simple rate limiter, basic queue) or condense them to one-liners with links to detailed implementations

Dimension	Reasoning	Score
Conciseness	The content is comprehensive but includes some patterns Claude already knows well (basic repository pattern, simple rate limiting). Some sections like the JobQueue could be trimmed, and the closing reminder is unnecessary.	2 / 3
Actionability	Excellent executable TypeScript examples throughout with complete, copy-paste ready code. Each pattern includes concrete implementations with proper typing, error handling, and usage examples.	3 / 3
Workflow Clarity	Patterns are presented as isolated examples without clear guidance on when to use each or how they connect. Missing validation checkpoints for database transactions and no explicit workflow for implementing these patterns in a project.	2 / 3
Progressive Disclosure	This is a monolithic 400+ line file with no references to external documentation. Content covering API design, database patterns, caching, auth, rate limiting, queues, and logging should be split into separate focused files with a concise overview.	1 / 3
	Total	8 / 12 Passed

Activation

33%

The description identifies a clear technical domain and lists relevant technologies, but lacks concrete actions (uses category nouns instead of verbs) and critically omits any explicit trigger guidance. The absence of a 'Use when...' clause makes it difficult for Claude to know when to select this skill over others.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when building backend services, designing REST APIs, optimizing database queries, or working with Node.js/Express/Next.js server code'

Replace category nouns with concrete actions: 'Design REST/GraphQL APIs, optimize database queries, structure Express middleware, configure Next.js API routes'

Expand trigger terms to include common variations: 'REST', 'GraphQL', 'middleware', 'endpoints', 'server-side rendering', 'backend development'

Dimension	Reasoning	Score
Specificity	Names the domain (backend/server-side) and lists several areas (architecture patterns, API design, database optimization, best practices) but these are categories rather than concrete actions like 'design REST endpoints' or 'optimize SQL queries'.	2 / 3
Completeness	Describes what the skill covers (backend patterns, API design, etc.) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Node.js', 'Express', 'Next.js API routes', 'API design', 'database' that users might mention, but missing common variations like 'REST', 'backend development', 'server code', 'endpoints', or 'MongoDB/PostgreSQL'.	2 / 3
Distinctiveness Conflict Risk	The combination of Node.js/Express/Next.js provides some specificity, but 'API design' and 'database optimization' are broad enough to potentially overlap with general coding skills or database-specific skills.	2 / 3
	Total	7 / 12 Passed

Reviewed

17 days ago

Table of Contents

Validation Implementation Activation

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.