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
Quality
93%
Does it follow best practices?
Impact
99%
1.13xAverage score across 5 eval scenarios
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 guidance. The description effectively distinguishes itself through the specific 'Headless Core & Passive View' pattern terminology.
| 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'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('enforces Headless Core & Passive View pattern', 'refactors logic out of UI', 'creates platform-agnostic Core 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', 'architecture', 'clean architecture', 'business logic', 'UI', 'cross-platform', 'WASM'. Good coverage of terms developers naturally use when discussing these topics. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers around a specific architectural pattern ('Headless Core & Passive View'). The combination of clean architecture, WASM, and the specific pattern name makes it unlikely to conflict with general coding or refactoring 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. The layered organization and clear developer instructions provide strong workflow guidance. The main weakness is the lack of inline executable code examples, relying instead on an external reference file for implementation details.
Suggestions
Add at least one minimal executable code example inline (e.g., a simple Core struct with a validate method and corresponding ViewModel) to demonstrate the pattern concretely
Include a brief code snippet showing the boundary enforcement mentioned in instruction #5 (e.g., how to expose `can_access_admin_panel: bool` in a ViewModel instead of checking `user.is_admin` in UI)
| 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 inline. The patterns section references an external file for 'detailed code examples' rather than providing copy-paste ready implementations. | 2 / 3 |
Workflow Clarity | Section 4 provides a clear 5-step sequence for implementation with explicit ordering (Start with Core -> Define Interface -> Build View Last). The 'Enforce Boundaries' instruction provides a clear decision checkpoint for handling edge cases. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear sections. Appropriately references external file [references/patterns.md] for detailed code examples, keeping the main skill focused on concepts and workflow. Single-level reference depth. | 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.
Install with Tessl CLI
npx tessl i jpc0/headless-architecture@0.1.0Reviewed
Table of Contents