putio/frontend-patterns
Apply put.io frontend code patterns and seed repo-local `.patterns/` conventions. Use when writing or reviewing UI/frontend code in a put.io frontend repo, picking the default approach for types, data parsing, state machines, error handling, components, or testing, or seeding/extending the repo's `.patterns/` folder.
97
97%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 an excellent skill description that clearly defines its scope, provides rich trigger terms, and explicitly delineates boundaries with related skills. The 'Use when' and 'Skip for' clauses make it highly actionable for skill selection. The description uses proper third-person voice and avoids vague language.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: writing/reviewing UI/frontend code, handling types, data parsing, state machines, error handling, components, testing, and seeding/extending the `.patterns/` folder. | 3 / 3 |
Completeness | Clearly answers both 'what' (apply put.io frontend code patterns and seed repo-local .patterns/ conventions) and 'when' (explicit 'Use when' clause with detailed triggers, plus a 'Skip for' clause that clarifies boundaries with other skills). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'UI/frontend code', 'types', 'data parsing', 'state machines', 'error handling', 'components', 'testing', '.patterns/', 'put.io frontend repo'. These cover a wide range of natural user queries. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit boundary-drawing via 'Skip for' clauses that name three other specific skills (`putio-frontend-repos`, `putio-frontend-docs`, `putio-sdk-dev`), making it very clear when this skill should and should not be selected. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that is concise, actionable, and well-structured for its domain. The quick rules are crisp and opinionated, the code examples are executable and illustrative, and the workflow provides clear sequencing with validation steps. The main weakness is that the referenced bundle files (frontend-defaults.md, pattern-template.md) are not provided, making it impossible to fully evaluate the progressive disclosure structure, though the references themselves are well-signaled.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It assumes Claude's competence with TypeScript, schemas, state machines, and frontend patterns. Every section earns its place — quick rules are terse bullet points, code examples are minimal but complete, and there's no explanation of basic concepts. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples for schema parsing and discriminated unions with exhaustive matching. The workflow is concrete with specific steps (inspect repo, read files, run verify command). The `.patterns/` setup instructions are specific with file naming conventions and content structure. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with explicit checkpoints: inspect repo first, read existing patterns, apply defaults when silent, capture divergences, run verify, and audit for drift. The 'when to add a pattern entry' section provides clear decision criteria. Step 5 includes a validation checkpoint. | 3 / 3 |
Progressive Disclosure | References to `references/frontend-defaults.md` and `references/pattern-template.md` are well-signaled and one level deep, which is good. However, no bundle files were provided, so we cannot verify these references exist. The skill also inlines a fair amount of content (quick rules, concrete shapes, pattern setup) that could potentially be split, though the total length is reasonable. | 2 / 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