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.
85
91%
Does it follow best practices?
Impact
95%
3.16xAverage score across 2 eval scenarios
Passed
No known issues
{
"context": "Tests whether the frontend patterns skill makes the agent recommend schema-driven parsing, explicit state modeling, and repo verification for a bug-sensitive UI flow.",
"type": "weighted_checklist",
"checklist": [
{
"name": "parses_unknown_at_boundary",
"description": "Recommends parsing unknown API JSON at the boundary with the repo's schema/parser approach before passing typed values into UI code.",
"max_score": 3
},
{
"name": "models_transfer_states_explicitly",
"description": "Recommends discriminated unions, exhaustive handling, or a state machine for transfer statuses instead of optional-field or boolean-salad state.",
"max_score": 3
},
{
"name": "rejects_type_escape_hatches",
"description": "Explicitly avoids `as` casts, non-null assertions, and loosely typed validated data as the solution to the draft component's problems.",
"max_score": 2
},
{
"name": "uses_repo_local_patterns_first",
"description": "Says to inspect AGENTS.md, README.md, and existing `.patterns/` or code precedent before applying default put.io patterns.",
"max_score": 1
},
{
"name": "includes_verification_plan",
"description": "Names an appropriate verification path, including the repo verify command and a browser/device exercise for the UI behavior.",
"max_score": 1
}
]
}