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. Skip repo shape, top-level docs, delivery, CI, proof harness work, and SDK package patterns.
77
97%
Does it follow best practices?
Impact
—
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, lists concrete actions, includes natural trigger terms, and explicitly distinguishes itself from related skills by naming them and specifying boundary conditions. The 'Skip for...' clause is particularly effective at reducing conflict risk in a multi-skill environment.
| 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, seed repo-local .patterns/ conventions) and 'when' (writing or reviewing UI/frontend code, picking default approaches for specific concerns). Also explicitly states when NOT to use it, referencing alternative skills. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'UI', 'frontend', 'code patterns', 'types', 'data parsing', 'state machines', 'error handling', 'components', 'testing', '.patterns/', 'put.io'. These cover a broad range of natural terms for the domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit boundary-drawing: it names the specific domain (put.io frontend code patterns), lists what it covers, and explicitly delineates what should go to `putio-frontend-repos` or `putio-sdk-dev` instead, minimizing conflict risk. | 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 excellent — terse, opinionated, and immediately useful. The workflow is clear with appropriate validation steps. The main weakness is that bundle files weren't provided to verify referenced paths, and some inline content (patterns setup, concrete examples) could potentially be offloaded to the referenced files for better progressive disclosure.
Suggestions
Ensure the referenced bundle files (references/frontend-defaults.md and references/pattern-template.md) are actually provided so the progressive disclosure structure is complete and verifiable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It assumes Claude's competence with TypeScript, frontend frameworks, and state machines. Every section earns its place — quick rules are terse bullet points, the workflow is numbered without padding, and code examples are minimal but complete. No unnecessary explanations of what schemas, discriminated unions, or state machines are. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples (Effect Schema parsing, discriminated union with exhaustive match), concrete file naming conventions (kebab-case, specific seed filenames), a clear 6-step workflow with specific actions, and precise criteria for when to add pattern entries. The guidance is copy-paste ready and specific. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with explicit checkpoints: inspect repo first, read existing patterns before writing, apply defaults when patterns are silent, capture divergences as draft entries, run verify command, and audit for drift. Step 5 includes a validation checkpoint (run verify + browser exercise), and step 6 adds a drift audit — both serve as feedback loops for catching errors. | 3 / 3 |
Progressive Disclosure | References to bundled files (frontend-defaults.md, pattern-template.md) are well-signaled and one level deep, and boundary skills are clearly named. However, no bundle files were provided to verify the references actually exist, and some content that could live in the referenced files (like the concrete code examples and the '.patterns/' setup instructions) is inline, making the main file longer than necessary. | 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