agentleFS
Sign inStart free
HeyEddi-comHeyEddi-com/heyeddi-skills/skills/primevue-openprops-architect/SKILL.md

primevue-openprops-architect

Skill0 starsChanged 3 months agoMITView on GitHub

Enforces PrimeVue + project design tokens when editing Vue or CSS. OpenProps rules apply only when the project already uses open-props. Runs vue-tsc and stylelint when available.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When chained from parent skills, validate_vue.py runs in a shell subagent by default.

    line 17
  2. Very specific:

    Read context/VOCABULARY.md and context/ANTI_PATTERNS.md, context/PROSE_ANTI_SLOP.md before writing UI code.

    line 27
  3. Very specific:

    Read heyeddi-design/reference/token-strategy.md: detect OpenProps vs custom tokens.css.

    line 28
  4. Very specific:

    Use semantic CSS variables from project tokens.css / design.md: OpenProps-backed (var(--surface-1)) or custom (var(--brand)).

    line 30
  5. Very specific:

    After edits, run python scripts/validate_vue.py --project-root <root>.

    line 31

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PrimeVue + project tokens

Enforces PrimeVue and the project's semantic token system. OpenProps is optional: detect before enforcing OpenProps-specific rules.

When chained from parent skills, validate_vue.py runs in a shell subagent by default. See reference/subagents.md.

When to use

  • Editing .vue single-file components or project stylesheets
  • Agent is about to add UI components, tokens, or layout
  • Validating generated Vue against team design system

Instructions

  1. Read context/VOCABULARY.md and context/ANTI_PATTERNS.md, context/PROSE_ANTI_SLOP.md before writing UI code.
  2. Read heyeddi-design/reference/token-strategy.md: detect OpenProps vs custom tokens.css.
  3. Reuse PrimeVue components from the project catalog: never invent props.
  4. Use semantic CSS variables from project tokens.css / design.md: OpenProps-backed (var(--surface-1)) or custom (var(--brand)). No scattered hex in .vue / CSS.
  5. After edits, run python scripts/validate_vue.py --project-root <root>.
  6. Fix all reported issues before finishing.

Scripts

  • validate_vue.py: runs vue-tsc --noEmit and stylelint if installed

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free