We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈2

  Distinctive · estimate

  This author's own choices. Worth a look.

• 4

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Distinctive:

   When generating UI code, accessibility is a strict requirement, not an afterthought:

   line 7
2. Very specific:

   Semantic HTML: Use native semantic elements (<button>, <nav>, <main>) instead of <div> with click handlers.

   line 9
3. Very specific:

   ARIA Attributes: Use ARIA attributes (aria-expanded, aria-hidden, aria-label) only when native HTML falls short (e.g., for complex custom …

   line 10
4. Very specific:

   Keyboard Navigation: Ensure all interactive elements are reachable via the Tab key and have visible :focus or :focus-visible states.

   line 11
5. Distinctive:

   Color Contrast: Ensure text has sufficient contrast against its background (aim for WCAG AA standard of 4.5:1).

   line 12
6. Very specific:

   Alt Text: Always provide meaningful alt text for images conveying information.

   line 13

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.