agentleFS
HeyEddi-comHeyEddi-com/heyeddi-skills/skills/primevue-aura/SKILL.md

primevue-aura

Skill0 starsChanged 7 days agoMITView on GitHub

PrimeVue with the Aura preset for dense Vue 3 data grids, filters, complex form controls, and overlays. No Tailwind. Use for DataTable, TreeSelect, menus, badges, and the Quasar plus PrimeVue bootstrap order.

  • Installs packages

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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. Distinctive:

    Use PrimeVue for these primitives:

    line 87
  2. Very specific:

    Import components from primevue/<name> (PascalCase path, unstyled entry is not used.

    line 103
  3. Distinctive:

    When the PrimeVue MCP server is connected, confirm props there before inventing them.

    line 104
  4. Very specific:

    After the view exists, load @motion-physics for row and dialog entry.

    line 105
  5. Distinctive:

    When you have finished the user's request for this skill, suggest what to run next:

    line 110

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 Aura

High-density data, advanced filtering, complex form controls, and contextual menus styled with PrimeVue's Aura preset. No Tailwind.

Application frames, drawers, and native shells belong to @quasar-foundation. Token names belong to @aura-design-tokens. Motion belongs to @motion-physics.

When the agent activates this skill

  • Building data grids, sorting, row expansion, virtual scrolling, and column filters.
  • Multi-tiered menus, tree-select dropdowns, cascade selects, and date or time range pickers.
  • In-app modals, floating tooltips, and popovers that require refined styling.
  • Scaffolding vite.config.js and src/main.js for a Quasar plus PrimeVue app.

Installation

npm install primevue @primevue/themes primeicons

Hybrid harmony setup

Quasar's CSS resets load first. PrimeVue Aura loads second so its components keep their styling.

// vite.config.js
import { defineConfig } from 'vite';
import vue from '@vitejs/plugin-vue';
import { quasar, transformAssetUrls } from '@quasar/vite-plugin';

export default defineConfig({
  plugins: [
    vue({ template: { transformAssetUrls } }),
    quasar({ sassVariables: 'src/quasar-variables.sass' })
  ]
});
// src/main.js
import { createApp } from 'vue';
import App from "@/App.vue";

// 1. Quasar core base & icon assets (Loads FIRST to apply foundational resets)
import { Quasar, Dialog, Notify, Morph } from 'quasar';
import '@quasar/extras/material-icons/material-icons.css';
import 'quasar/src/css/index.sass';

// 2. PrimeVue & Aura Preset (Loads SECOND to take precedence on components)
import PrimeVue from 'primevue/config';
import Aura from '@primevue/themes/aura';
import 'primeicons/primeicons.css';

// 3. Motion Engine
import { MotionPlugin } from '@vueuse/motion';

const app = createApp(App);

app.use(Quasar, { plugins: { Dialog, Notify, Morph } });

app.use(PrimeVue, {
  theme: {
    preset: Aura,
    options: {
      prefix: 'p',
      darkModeSelector: '.dark-mode',
      cssLayer: false
    }
  }
});

app.use(MotionPlugin);
app.mount('#app');

cssLayer: false is required so Aura wins over Quasar resets on PrimeVue components. Dark mode uses the .dark-mode class from @aura-design-tokens.

Component responsibility

Use PrimeVue for these primitives:

Component categoryPrimeVue primitiveRationale
Data presentation<DataTable>, <Column>, <TreeTable>High-density layout, virtual scroll, multi-sort, Excel-like filtering.
Complex pickers<MultiSelect>, <TreeSelect>, <CascadeSelect>Chip badges, grouped hierarchies, inline search filtering.
Context controls<TieredMenu>, <ContextMenu>, <Breadcrumb>Precision desktop menus with sub-menu flyouts.
Status and metric badges<Tag>, <Badge>, <ProgressBar>Consistent typography and semantic tone indicators.

Also use PrimeVue for form fields inside data-dense screens (InputText, Select, DatePicker, Password) when the control is not a Quasar shell primitive. Do not restyle them with Tailwind. Do not wrap them in Quasar q-input when PrimeVue already owns the field.

Card body content goes in <template #content>.

Instructions

  1. Confirm the surface is data, a complex control, or an overlay. Shell chrome stays Quasar.
  2. Import components from primevue/<name> (PascalCase path, unstyled entry is not used; Aura is the preset).
  3. When the PrimeVue MCP server is connected, confirm props there before inventing them.
  4. After the view exists, load @motion-physics for row and dialog entry. Do not add PrimeVue's default CSS transitions for spatial movement.
  5. Surfaces and text use var(--app-*) from @aura-design-tokens, which read --p-*.

When the task is complete: suggest next skills

When you have finished the user's request for this skill, suggest what to run next:

  1. Run:

    python .agents/skills/heyeddi/scripts/suggest_next_skill.py --current-skill primevue-aura --project-root .
  2. Include the script's ### Next step block in your final reply.

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.