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
audits_existing_repo_patterns
50%
100%
captures_decision_in_patterns
33%
100%
uses_expected_pattern_shape
100%
100%
keeps_docs_boundary_clear
0%
100%
requires_drift_check_and_verify
100%
50%
parses_unknown_at_boundary
0%
100%
models_transfer_states_explicitly
0%
100%
rejects_type_escape_hatches
0%
100%
uses_repo_local_patterns_first
0%
100%
includes_verification_plan
0%
100%
Table of Contents