backend-patterns

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The skill is a strong, executable reference catalog of backend patterns with concrete code throughout, but it re-teaches well-known concepts, carries no unifying sequenced workflow, and packs everything into one large file. Trimming known patterns, splitting topics into referenced files, and adding a quick-start workflow with validation would raise its three 2-scored dimensions.

Suggestions

Move the depth material (auth/RBAC, caching, background queues, logging) into one-level-deep reference files (e.g. AUTH.md, CACHING.md) and keep SKILL.md as a concise overview with signaled links, improving progressive disclosure and conciseness.

Trim re-explanation of textbook concepts (what the Repository/Service/cache-aside patterns are) to only what is project-specific (e.g. the Supabase RPC transaction and the 'markets' domain context), trusting Claude's competence.

Add a short quick-start workflow with explicit validation checkpoints (e.g. for the transaction or batch-indexing path: apply -> validate -> rollback/retry) to lift workflow clarity above 2.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and sectioned rather than rambling prose, but ~580 lines re-explain textbook patterns Claude already knows (Repository, Service layer, N+1, cache-aside, RBAC, rate limiting, structured logging), so it is mostly efficient yet could be tightened substantially rather than hitting the lean level-3 bar.	2 / 3
Actionability	It provides extensive, largely copy-paste-ready TypeScript plus a Supabase RPC SQL function across repository, caching, auth, retry, rate-limiting, and logging examples, matching the level-3 'fully executable, specific examples' anchor despite a few '// ...' ellipses in catalog spots.	3 / 3
Workflow Clarity	This is a patterns catalog, not a sequenced multi-step workflow; isolated error-recovery exists (transaction rollback, exponential-backoff retry) but there is no overarching step sequence with validation checkpoints, fitting the level-2 'sequence/checkpoints missing or implicit' anchor rather than the level-3 feedback-loop pattern.	2 / 3
Progressive Disclosure	The body is internally well-sectioned (API design, database, caching, auth, etc.) but is a monolithic ~580-line SKILL.md with no bundle files and no one-level-deep references, so content that should be split is inline; the under-50-line simple-skill exemption does not apply.	2 / 3
	Total	9 / 12 Passed

Description

65%

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 is reasonably specific and rich in natural trigger terms, but it tells Claude what the skill covers without ever stating when to invoke it. Adding an explicit 'Use when...' clause and reframing domains as concrete actions would lift its two weakest dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when designing or reviewing backend APIs, optimizing database queries, or structuring server-side code in Node.js, Express, or Next.js.'

Convert topic nouns into concrete actions ('design REST APIs', 'optimize database queries', 'implement caching and auth middleware') to raise specificity from a domain list to an action list.

Sharpen distinctiveness by scoping the niche (e.g. 'for Supabase-backed market/trading applications') so it is less likely to collide with generic backend skills.

Dimension	Reasoning	Score
Specificity	The description names concrete domains ('API design', 'database optimization', 'server-side best practices for Node.js, Express, and Next.js API routes') rather than vague abstractions like 'Helps with documents', but it lists topic areas as noun phrases without concrete action verbs, so it stops short of the multi-action list at level 3.	2 / 3
Completeness	It clearly answers 'what does this do' but provides no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric guidelines explicitly cap at 2.	2 / 3
Trigger Term Quality	It packs in natural terms a developer would actually say ('API design', 'database optimization', 'Node.js', 'Express', 'Next.js API routes'), matching the dense keyword coverage of the level-3 anchor; it is not merely technical jargon like 'document object model manipulation'.	3 / 3
Distinctiveness Conflict Risk	The named framework stack (Node.js, Express, Next.js) carves out a niche, but the broad framing 'backend architecture patterns' and 'server-side best practices' could still overlap with general backend or web-development skills, fitting the level-2 'somewhat specific but could overlap' anchor.	2 / 3
	Total	9 / 12 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
skill_md_line_count	SKILL.md is long (588 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: affaan-m/everything-claude-code
Commit: 4130457

Reviewed: 4 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.