angular-architecture

Angular architecture: Scope Rule, project structure, file naming, style guide. Trigger: When structuring Angular projects or deciding where to place components.

Quality

78%

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 ./curated/angular/architecture/SKILL.md

Quality

Content

68%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 body is a concise, actionable reference with concrete examples and commands that assume Claude's competence. Its main weakness is the absence of an explicit multi-step workflow with validation checkpoints, which is fine for a guidance skill but caps workflow clarity at the midpoint.

Suggestions

Add a short "Placement decision" workflow (1. identify component consumers → 2. if 1 feature, place under features/[feature]/components/; if 2+, place under features/shared/components/ → 3. verify naming has no .component/.service suffix) to raise workflow clarity.

Complete the @Component example bodies (computed() expression, save() method) or mark them as intentional placeholders so the example is fully copy-paste ready.

Trim the "What We Override" table since the no-suffix naming rule is already shown in the File Naming section, to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Lean throughout with no explaining of concepts Claude already knows, using terse tables and rules; minor padding in the "What We Override" table which restates the naming rule keeps it just below the top anchor.	4 / 5
Actionability	Provides concrete folder structures, ✅/❌ naming examples, executable `ng` commands, and a real @Component skeleton, but a few example bodies use `...` placeholders, leaving minor gaps.	4 / 5
Workflow Clarity	The Scope Rule is a clear decision procedure (place by usage), but the body is reference material with no explicit sequenced workflow or validation checkpoints; it is coherent but lacks the sequencing and checkpoints of higher anchors.	3 / 5
Progressive Disclosure	A single self-contained file with well-organized section headers and no nested references; content is appropriately inline since nothing clearly belongs in a separate file, though it does not demonstrate the well-signaled one-level-deep reference split that earns the top score.	4 / 5
	Total	15 / 20 Passed

Description

87%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 is well-constructed: it states the domain and scope concisely and pairs it with an explicit, natural trigger clause. It is distinctive and largely free of vague fluff. The only gap is slightly less comprehensive action specificity and a few missing trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names the Angular domain and lists four concrete facets ("Scope Rule, project structure, file naming, style guide"), but lacks concrete action verbs and comprehensive coverage, so it sits just below the top anchor.	4 / 5
Completeness	Explicitly answers what ("Angular architecture: Scope Rule, project structure, file naming, style guide") and when ("Trigger: When structuring Angular projects or deciding where to place components") with a concrete trigger clause.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ("Angular projects", "structur", "place components") with good coverage, though a few synonyms (e.g. "organize", "folder structure") are missing.	4 / 5
Distinctiveness Conflict Risk	A clear Angular-specific niche with triggers tied to Angular projects and component placement, giving minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Gentleman-Programming/Gentleman-Skills
Path: curated/angular/architecture/SKILL.md
Commit: c8036a3

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