We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈4

  Distinctive · estimate

  This author's own choices. Worth a look.

• 2

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   Use this adapter when the design target is a browser-based product.

   line 10
2. Distinctive:

   Treat hover, focus, active, disabled, loading, validation, and empty states as first-class.

   line 15
3. Distinctive:

   Keep forms, tables, filters, and navigation feasible in HTML/CSS terms.

   line 16
4. Distinctive:

   Use semantic structure, keyboard navigation, visible focus, and contrast checks.

   line 17
5. Distinctive:

   Prefer implementation notes that can be verified in a browser.

   line 18
6. Very specific:

   If the repo uses shadcn/ui or Tailwind CSS, load framework-shadcn-tailwind-ui and map visual decisions to local components, tokens, and …

   line 19

≈ “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.