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.
85
91%
Does it follow best practices?
Impact
95%
3.16xAverage score across 2 eval scenarios
Passed
No known issues
task.mdevals/scenario-2/
The user says:
"I'm adding a transfers panel in a put.io frontend repo. The API response is loosely typed JSON with different transfer states, and the existing component draft uses optional fields, as casts, and isLoading / error / data booleans. Please tell me how you'd structure the implementation before I write the code."
Respond with the implementation approach the agent should take.