We kept seeing the same issues across cards. Small, but persistent
Across multiple cards, from different developers on the team — the same small bugs kept showing up. Wrong label text, misaligned fields, dropdowns breaking on scroll, loaders with the wrong opacity. Nothing critical on its own, but collectively they were eating into review cycles, QA time, and everyone’s patience.
So we decided to stop patching and start preventing. We went through the recurring patterns, traced them back to their root causes, and turned those findings into two things the whole team can actually use — a set of development guidelines and a pre-QA handoff checklist, both available as Claude skills.
Development Guidelines
A set of 30 coding and implementation standards derived directly from recurring bug patterns. Covers areas like multi-locale number formatting, popup and overlay positioning, URL state persistence, access control, package version pinning, timezone handling, file upload validation, and more.
The idea is simple — if we follow these guidelines upfront, most of these bugs would never make it to QA.
development_guidelines.md (20.5 KB)
Pre-QA Handoff Checklist
A 19-item verification checklist that surfaces automatically when you complete a feature, open a PR, or push code. It identifies which checklist items are relevant to what you just built, asks you to confirm each one, and offers to track any unchecked items.
The goal is to catch the obvious misses — layout shifts, text mismatches, broken scroll behaviour, missing validation — before they reach QA.
pre_handoff_cheklist.md (9.1 KB)
Both skills are ready to use — just drop the linked SKILL.md files into your skills directory and they plug in seamlessly to your Claude workflow.
Would love feedback as we continue to add to these — if you spot a recurring pattern that isn’t covered, flag it and we can document and add it.