Claude Code skills should fix real weak spots
files should do more than say “act like an experienced developer” or “write clean code.” Claude already understands those broad ideas, so repeating them does not teach it anything useful. A good skill should target mistakes Claude keeps making.
It should push Claude to think about before the end, including which resources slow page loading, what should be included immediately, and what can wait. It should also make mobile layout part of the first design, not a late fix.
Before public deployment, it should raise security checks such as and planning. It should also force basic habits, such as using real buttons, managing keyboard focus, and not adding ARIA as an afterthought.
Key points
- should correct repeated mistakes, not restate broad developer traits.
- should be considered early, before a final Lighthouse check.
- Mobile layout should be planned from the start of the build.
- Public projects should include security checks like and planning.
- needs practical rules for buttons, keyboard focus, and ARIA use.