agentsclimarketplace
Sign in

Primevue openprops architect

Skill HeyEddi-com/skills/evals/runs/2026-07-04T22-58-59Z/heyeddi-design-from-scratch/.agents/skills/primevue-openprops-architect

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.From its SKILL.md

Install
npx -y skills add HeyEddi-com/skills --skill primevue-openprops-architect

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.4 KB, 282 tokens by cl100k_base, as published. Nobody here has run it

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 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

What ships with it: 7 files

6.1 KB alongside SKILL.md, 2 of them executable

context/

reference/

scripts/

Gives 0 of the 12 instructions most architecture codebase skills give in 282 tokens

Counted across 811 of the 1,134 authors here whose files we hold, read 2026-08-07

  • Ask the user which candidate to explorein 45 of 811, across 15 files
  • Apply the deletion test to suspected shallow modulesin 43 of 811, across 15 files
  • Read any relevant architecture decision records firstin 31 of 811, across 8 files
  • Use exact glossary terms in every suggestionin 30 of 811, across 10 files
  • Accept dependencies instead of creating themin 24 of 811, across 5 files
  • Include before and after visualisations for each candidatein 24 of 811, across 5 files
  • Read the domain glossary before exploringin 24 of 811, across 6 files
  • Return results instead of producing side effectsin 23 of 811, across 4 files
  • Explore the codebase for shallow modules and frictionin 23 of 811, across 3 files
  • Introduce seams only where things varyin 22 of 811, across 3 files
  • Reduce the number of methodsin 21 of 811, across 2 files
  • Design deep modules with small interfacesin 21 of 811, across 3 files

Said here and by no other author read

  • read the vocabulary and anti-pattern context first
  • read the token strategy reference
  • detect whether the project uses openprops
  • reuse primevue components from the catalog
  • never invent component props
  • use semantic css variables

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,614. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.