backend-patterns

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

Quality

48%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs/zh-TW/skills/backend-patterns/SKILL.md

Quality

Discovery

32%

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

The description identifies a clear technical domain and relevant technologies but relies heavily on abstract concepts ('patterns', 'best practices') rather than concrete actions. The critical missing element is any explicit trigger guidance—there's no 'Use when...' clause to help Claude know when to select this skill over others.

Suggestions

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

Replace abstract terms with concrete actions: instead of 'backend architecture patterns', specify 'design REST endpoints, structure middleware, implement authentication flows'.

Include common user phrasings and variations: 'API routes', 'server-side code', 'backend logic', 'database queries', 'Express middleware', 'Next.js API handlers'.

Dimension	Reasoning	Score
Specificity	Names the domain (backend/API/database) and mentions specific technologies (Node.js, Express, Next.js), but uses abstract terms like 'patterns', 'best practices', and 'optimization' rather than concrete actions like 'design REST endpoints' or 'write database queries'.	2 / 3
Completeness	Describes what the skill covers (backend patterns, API design, etc.) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant technical keywords (Node.js, Express, Next.js, API, database) that users might mention, but missing common variations like 'REST', 'endpoints', 'server', 'routes', 'SQL', 'MongoDB', or action-oriented terms like 'build API' or 'optimize queries'.	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, database-specific skills, or framework-specific skills.	2 / 3
	Total	7 / 12 Passed

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 reference document with excellent, executable TypeScript examples covering major backend patterns. However, it's overly comprehensive for a single skill file, presenting patterns Claude likely already knows without clear guidance on when to apply each pattern or how they integrate together. The content would benefit from being restructured as an overview with links to detailed pattern files.

Suggestions

Split into multiple files (e.g., DATABASE-PATTERNS.md, AUTH-PATTERNS.md, CACHING.md) with this file as a brief overview linking to each

Add a decision tree or guidance section explaining when to use each pattern (e.g., 'Use Repository pattern when: ...')

Remove basic patterns Claude already knows (simple middleware, basic repository) and focus on project-specific conventions or non-obvious implementations

Add validation checkpoints for database operations, especially for the transaction pattern (e.g., 'Verify transaction succeeded before proceeding')

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some patterns Claude already knows well (basic repository pattern, middleware pattern). Some sections like the simple queue pattern and rate limiter could be trimmed as these are standard implementations.	2 / 3
Actionability	Excellent executable TypeScript code throughout with complete, copy-paste ready examples. Each pattern includes full implementation 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 which pattern or how they connect. Missing validation checkpoints for database operations and no explicit workflow for implementing these patterns in a new project.	2 / 3
Progressive Disclosure	Content is well-organized with clear section headers, but the file is quite long (~400 lines) and could benefit from splitting into separate files (e.g., CACHING.md, AUTH.md, DATABASE.md) with this file serving as an overview with links.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (588 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: haniakrim21/everything-claude-code
Commit: ae2cadd

Reviewed: 18 days 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.