CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frontend-layered-architecture

Use for frontend architecture boundaries: code ownership, directory roles, file placement, import direction, UI/component extraction, API/data contracts, fetching/query, URL state, mappers/schemas/DTOs, hooks/stores, architecture docs, and tool enforcement. Also use before agent-initiated architecture-enforcement changes in lint, CI, import-boundary checks, or similar automation—even without a user request—and for small UI changes that may leak business rules or external data into lower-level code.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 SKILL.md body is a well-written, efficient router: it defines four abstract layers, gives sharp minimum guards, and routes by user purpose with an explicit fallback loop. Its fatal flaw in this bundle is that every one of the five documents it routes to is missing, which cripples actionability and progressive disclosure despite the excellent in-file organization. No destructive or batch operations are involved, so no validation cap applies.

Suggestions

Ship the five routed documents (brownfield.md, greenfield.md, writing-docs.md, enforcing-rules.md, best-practices.md) alongside SKILL.md — none exist in the bundle, so every routing path dead-ends and the skill's core guidance is unreachable (progressive_disclosure).

Add a fallback step to the Purpose Router for when a routed document is missing or fails to answer the purpose, e.g. 'If the routed document is unavailable, apply the Common Foundation and Minimum Guards above and say so' — this both fixes navigation and gives an executable path when files are absent (actionability, workflow_clarity).

Inline a minimal placement/import-direction decision procedure (the essence of the Common Foundation guards) in SKILL.md so the most common decisions can be made without depending entirely on the external documents (actionability).

DimensionReasoningScore

Conciseness

The body is dense with non-obvious guidance ('Shared is determined by code-level independence, not by generic names', 'Judge the application context the code knows, not the package it imports') and explains nothing Claude already knows, but a few passages could be trimmed — e.g. 'Real projects may split them further, but this means at least four concepts are needed. That is why they are abstract layers.' and the 60-plus-word Domain-to-Data guard sentence.

4 / 5

Actionability

Concrete decision rules, a dependency diagram, and worked classification examples ('ProductCard can be Shared if it only renders injected props, while a generic-looking buildSearchParams is not Shared') are present, but the primary instruction — 'read the first matching document' — cannot be executed: none of the five routed files (brownfield.md, greenfield.md, writing-docs.md, enforcing-rules.md, best-practices.md) exist in the bundle, so the key details are missing. This matches 'some concrete guidance but incomplete; missing key details' rather than anchor 4, whose gaps are minor rather than structural.

3 / 5

Workflow Clarity

The router gives a clear sequenced workflow ('Classify the user's purpose in one sentence, then read the first matching document') with an explicit checkpoint and error-recovery loop ('After reading the routed document, check whether it directly answers the user's purpose. If not, say what is missing and route to the next required source'). Not anchor 5 because there is no handling for the case where a routed document is unavailable, which this bundle demonstrates is a real failure mode.

4 / 5

Progressive Disclosure

The structure is the right pattern — a lean overview with a purpose-keyed table of one-level-deep, clearly signaled links — which would score 5 if the files existed. However, all five referenced documents are absent from the bundle, so the references are dangling and the navigation chain is broken; that is worse than the 'minor organization gaps' of anchor 4 but better than anchor 2, since the in-file structure and signaling are genuinely good.

3 / 5

Total

14

/

20

Passed

Description

91%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.

This is a strong description: third-person, trigger-dense, with explicit 'Use for'/'Also use' guidance covering both user-requested and agent-initiated scenarios, and rich synonym coverage of the terms frontend developers actually use. Its only weaknesses are a single-verb framing that lists scope topics rather than concrete actions, and proactive triggers broad enough to slightly overlap with general refactoring and linting skills.

DimensionReasoningScore

Specificity

It enumerates a dozen concrete scope areas — 'code ownership, directory roles, file placement, import direction, UI/component extraction, API/data contracts, fetching/query, URL state, mappers/schemas/DTOs, hooks/stores' — but the only verb is 'Use for', so it lists specific topics rather than the varied concrete actions of the anchor-5 example ('Extract text... fill forms, merge documents'). That is a minor coverage gap, matching anchor 4.

4 / 5

Completeness

'What' is answered concretely ('Use for frontend architecture boundaries' with the enumerated scope list) and 'when' is answered explicitly and unusually thoroughly ('Also use before agent-initiated architecture-enforcement changes in lint, CI, import-boundary checks, or similar automation—even without a user request—and for small UI changes that may leak business rules...'). Both are present with concrete trigger phrases, matching anchor 5; anchor 4's 'when could be more explicit' clearly understates this description.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with explicit synonym groups — 'fetching/query', 'mappers/schemas/DTOs', 'hooks/stores', 'API/data contracts' — plus the tool vocabulary users actually say ('lint, CI, import-boundary checks', 'file placement', 'import direction'). This matches the anchor-5 hallmark of synonyms and variations better than anchor 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (frontend layer/dependency boundaries) with distinct triggers, but the deliberate broadening — 'small UI changes', 'lint, CI' enforcement, 'even without a user request' — creates minor overlap risk with general frontend-refactoring and lint-configuration skills, matching anchor 4 rather than anchor 5's 'minimal conflict risk'.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 5 missing

Warning

Total

15

/

16

Passed

Repository

choegyumin/agent-skills

Path

skills/instruction/frontend-layered-architecture/SKILL.md

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.