backend-patterns

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/ja-JP/skills/backend-patterns/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

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

The content is a well-organized, largely executable catalog of backend patterns with concise code, but it is a monolithic single-file reference with no progressive disclosure and limited validation feedback loops for its destructive/batch operations.

Suggestions

Split the pattern categories into one-level-deep reference files (e.g., references/api-design.md, caching.md, auth.md) and keep SKILL.md as a concise overview with clear links.

Add explicit validate->fix->retry checkpoints to the destructive/batch patterns (e.g., verify a transaction's result before committing, confirm DELETE authorization outcomes).

Remove the duplicate Cache-Aside example that restates the CachedMarketRepository logic to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable TypeScript with terse Japanese comments and avoids tutorial padding, but the overlapping Redis caching examples (CachedMarketRepository and getMarketWithCache) are near-duplicates that could be trimmed, fitting the "efficient with minor over-explanation" anchor.	4 / 5
Actionability	Most sections give concrete, copy-paste-ready TypeScript (repository, service, middleware, RBAC, rate limiter, logger); held below 5 by a couple of explicitly stubbed bodies ("vectorSearch" and JobQueue "execute") and "// その他のメソッド..." placeholders.	4 / 5
Workflow Clarity	This is a pattern catalog organized by topic rather than a sequenced workflow, and several destructive/batch patterns (DELETE endpoints, transactions, batch fetch) lack explicit validate->fix->retry feedback loops, so the destructive/batch cap applies despite the transaction EXCEPTION block and retry-with-backoff example.	3 / 5
Progressive Disclosure	No bundle files exist and all ~580 lines are inlined in SKILL.md; section headers provide good structure, but content that could live in separate reference files (each pattern category) is inlined with no one-level-deep references, and the under-50-line simple-skill exception does not apply.	3 / 5
	Total	14 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 clearly states what the skill covers and names specific frameworks that act as strong triggers, but it omits any explicit "Use when..." guidance, which caps completeness. It is specific and distinct but not maximally actionable as a trigger.

Suggestions

Add an explicit "Use when..." clause naming concrete trigger phrases (e.g., designing API routes, optimizing database queries, adding auth or caching to a Node/Express/Next.js backend).

Replace category labels ("server-side best practices") with a few concrete actions (e.g., "implement auth, rate limiting, and caching layers") to lift specificity.

Include a synonym or two (e.g., "REST/RESTful APIs") to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Quotes "API design", "database optimization", and "server-side best practices" name the domain and a couple of activities, but these are category labels rather than concrete actions like 'extract', 'fill', or 'merge', matching the anchor that names the domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	The "what" is clearly stated ("Backend architecture patterns, API design, database optimization, and server-side best practices") but there is no "Use when..." clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	"Node.js, Express, and Next.js API routes" plus "API design" and "database optimization" are natural terms users say, giving good keyword coverage; held below 5 because no synonyms or variants are included and there is no "Use when" phrasing.	4 / 5
Distinctiveness Conflict Risk	Scoping to "Node.js, Express, and Next.js API routes" gives a clear niche with mostly distinct triggers; held below 5 because "backend architecture patterns" and "server-side best practices" still overlap broadly with general web-dev skills.	4 / 5
	Total	14 / 20 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/ECC
Path: docs/ja-JP/skills/backend-patterns/SKILL.md
Commit: e04ea0b

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