agentleFS
HeyEddi-comHeyEddi-com/heyeddi-skills/skills/quasar-foundation/SKILL.md

quasar-foundation

Skill0 starsChanged 7 days agoMITView on GitHub

Quasar application frames, drawers, mobile gestures, and Capacitor or Tauri shells for Vue 3. Use for headers, footers, navigation, pull-to-refresh, bottom sheets, and quasar build targets. Not for data tables or CLI.

  • Installs packages

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Quasar only for these primitives:

    line 32
  2. Very specific:

    Use <script setup> and the primitives above.

    line 44
  3. Very specific:

    After the shell exists, load @motion-physics for entry and press feedback.

    line 46
  4. Very specific:

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

    line 47
  5. Distinctive:

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

    line 51

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

Quasar Foundation

Responsive application framing, mobile touch gestures, drawer interactions, and platform wrappers for Capacitor (mobile) and Tauri or Electron (desktop).

Load @vue-design-system first if this skill was opened alone. Data grids, complex pickers, and menus belong to @primevue-aura. Colors belong to @aura-design-tokens. Motion belongs to @motion-physics.

When the agent activates this skill

  • Defining application scaffolding: headers, footers, responsive side drawers, and page containers.
  • Touch-first mobile layouts requiring pull-to-refresh, swipeable tabs, or bottom sheets.
  • Configuring multi-platform target builds (quasar build -m capacitor, quasar build -m tauri).

Installation

npm install quasar @quasar/extras
npm install -D @quasar/vite-plugin

Vite and main.js load order is the hybrid setup in @primevue-aura. Quasar core CSS loads first. Do not let Quasar components replace PrimeVue data components.

Component responsibility

Use Quasar only for these primitives:

Component categoryQuasar primitiveRationale
Layout framing<q-layout>, <q-page-container>, <q-page>Handles viewport calculation and native safe areas automatically.
Side navigation<q-drawer>Built-in touch swipe, responsive breakpoints, mini-mode toggles.
Application bars<q-header>, <q-footer>, <q-toolbar>Sticky positioning and elevation handling without manual CSS.
Mobile actions<q-bottom-sheet>, <q-fab>, <q-pull-to-refresh>Hardware-optimized touch listeners.

Instructions

  1. Confirm the surface is a shell, drawer, bar, or mobile gesture. If it is a table, tree, select, or menu, stop and load @primevue-aura.
  2. Use <script setup> and the primitives above. Do not recreate the shell with raw div sticky positioning.
  3. Brand color comes from --q-primary, which @aura-design-tokens bridges to PrimeVue. Do not set a second Quasar palette in hex.
  4. After the shell exists, load @motion-physics for entry and press feedback.
  5. When the Quasar MCP server is connected, confirm component props there before inventing them. Config is in @vue-design-system.

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 quasar-foundation --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.