jpc0/headless-architecture
Use this skill whenever the user discusses application architecture, clean architecture, separating business logic from UI, or cross-platform/WASM-based development. It enforces the 'Headless Core & Passive View' pattern, ensuring that the 'Core' (Business Logic) is platform-agnostic and the 'View' (UI) is a 'Humble Object' that only reflects state.
95
93%
Does it follow best practices?
Impact
98%
1.13xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 skill description that clearly articulates a specific architectural pattern and when to apply it. It uses third person voice correctly, provides concrete actions, and includes explicit trigger conditions. The description effectively distinguishes itself from general coding or refactoring skills through its focus on the specific 'Headless Core & Passive View' pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'refactor, design, or review application architecture', 'refactors logic out of the UI', 'creates platform-agnostic Core interfaces', 'ensures the View is a Humble Object that only reflects state'. | 3 / 3 |
Completeness | Explicitly answers both what ('enforces Headless Core & Passive View pattern, refactors logic, creates interfaces') AND when ('Trigger it when discussing clean architecture, separating business logic from UI, or cross-platform/WASM development'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'refactor', 'design', 'review', 'clean architecture', 'separating business logic from UI', 'cross-platform', 'WASM development', 'Headless Core', 'Passive View'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on a specific architectural pattern ('Headless Core & Passive View') with distinct triggers like 'clean architecture', 'WASM', and 'separating business logic from UI' that are unlikely to conflict with general coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured architectural skill that efficiently communicates a complex pattern through clear layering and developer instructions. The main weakness is the lack of inline executable code examples - the skill describes patterns conceptually but defers all concrete implementation to an external file, which reduces immediate actionability.
Suggestions
Add at least one minimal executable code example inline (e.g., a simple Core struct with validate() method and corresponding ViewModel) to demonstrate the pattern without requiring navigation to patterns.md
Include a brief concrete example showing the 'refuse and refactor' behavior from step 5, such as transforming `if user.is_admin` in UI to a ViewModel property
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using bullet points and clear headers without explaining concepts Claude already knows. Every section adds specific architectural guidance without padding. | 3 / 3 |
Actionability | Provides clear conceptual guidance and developer instructions, but lacks executable code examples - instead deferring to an external patterns.md file. The patterns section describes what to do but doesn't show how with concrete code. | 2 / 3 |
Workflow Clarity | The Developer Instructions section provides a clear 5-step sequence for implementation, and step 5 explicitly includes a validation checkpoint ('refuse and move it to the Core'). The layer progression A→B→C→D is also clearly sequenced. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview sections and appropriate reference to external file (references/patterns.md) for detailed code examples. Content is appropriately split between conceptual overview here and implementation details elsewhere. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents