skills

Personal Agent Skills for Cursor and compatible agents. Each skill auto-applies from the task — no @-mention required.

npx skills add equinusocio/skills

Skills

Skill	Docs	Triggers when…
authoring-react	README	Creating, editing, refactoring, or reviewing React/TS UI (components, hooks, JSX/TSX, props)
authoring-css	README	Writing or changing stylesheets, CSS modules, nesting, selectors, colors, gradients, motion, @property
a11y	README	Writing/editing UI (components, HTML, templates) and a11y / APG / ARIA / WCAG audit or keyboard/SR debug (any stack)

authoring-react + authoring-css + a11y can apply together (e.g. new component + CSS + a11y). a11y always loads on UI markup — not audit-only.

Install

# all skills
npx skills add equinusocio/skills

# one skill
npx skills add equinusocio/skills --skill authoring-react
npx skills add equinusocio/skills --skill authoring-css
npx skills add equinusocio/skills --skill a11y

# list
npx skills add equinusocio/skills --list

# local checkout
npx skills add ./path/to/skills

Requires the skills CLI (npx skills).

How to use

1. Install (above).
2. Work as usual — agent matches task to skill descriptions.
3. Optional: name a skill explicitly to force it.

Shared hard contract

• Apply on every matching change — no opt-out for convenience.
• Consumer project guidelines gate: before writing, agent checks whether your project already documents guidelines / style guides / lint rules for that work.
  • None found → follow this skill.
  • Found → agent asks which source to follow (this skill, project guidelines, or a mix) and waits.
  • Unclear or absent answer and local rules exist → follow local project rules for that conflict.
• Force majeure: skip or bend a rule only if you explicitly override for the task, or if following it would break the project’s established pattern / build.

Conflict demo (what “auto-apply” means in an existing repo)

Skill still loads from the task (no @-mention). If the consumer repo already has React conventions, agent does not silently pick — it surfaces the clash and waits.

Task: “Add a Panel component”

Source	Rule
Project (CONTRIBUTING.md / .cursor/rules)	export default function components; import { FC } from 'react'
Skill (authoring-react)	Named const + React.FC; React.* utility types — no named imports from 'react'

Agent asks before coding (AskQuestion when available, else numbered options):

1. Follow authoring-react
2. Follow project guidelines
3. Mix (you specify)

None found in the project → skill rules apply with no question. Same gate exists for authoring-css and a11y.

Repo layout

skills/
  <name>/SKILL.md      # hub (installed)
  <name>/README.md     # human docs (this catalog links here)
  <name>/*.md          # refs agent loads on demand
evals/
  <name>/              # trigger queries + eval prompts (not installed)

License

MIT (see skill frontmatter). Author: equinusocio.