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 category |
Quasar primitive |
Rationale |
| 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
- 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.
- Use
<script setup> and the primitives above. Do not recreate the shell with raw div sticky positioning.
- Brand color comes from
--q-primary, which @aura-design-tokens bridges to PrimeVue. Do not set a second Quasar palette in hex.
- After the shell exists, load
@motion-physics for entry and press feedback.
- 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:
Run:
python .agents/skills/heyeddi/scripts/suggest_next_skill.py --current-skill quasar-foundation --project-root .
Include the script's ### Next step block in your final reply.
1---2name: quasar-foundation3description: "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."4version: 1.0.05product-version: 3.8.186author: HeyEddi-com7metadata:8 source: https://skillmd.com/skills/heyeddi-com/quasar-foundation9---1011# Quasar Foundation1213Responsive application framing, mobile touch gestures, drawer interactions, and platform wrappers for Capacitor (mobile) and Tauri or Electron (desktop).1415Load `@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`.1617## When the agent activates this skill1819- Defining application scaffolding: headers, footers, responsive side drawers, and page containers.20- Touch-first mobile layouts requiring pull-to-refresh, swipeable tabs, or bottom sheets.21- Configuring multi-platform target builds (`quasar build -m capacitor`, `quasar build -m tauri`).2223## Installation2425```bash26npm install quasar @quasar/extras27npm install -D @quasar/vite-plugin28```2930Vite 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.3132## Component responsibility3334Use Quasar only for these primitives:3536| Component category | Quasar primitive | Rationale |37|--------------------|------------------|-----------|38| Layout framing | `<q-layout>`, `<q-page-container>`, `<q-page>` | Handles viewport calculation and native safe areas automatically. |39| Side navigation | `<q-drawer>` | Built-in touch swipe, responsive breakpoints, mini-mode toggles. |40| Application bars | `<q-header>`, `<q-footer>`, `<q-toolbar>` | Sticky positioning and elevation handling without manual CSS. |41| Mobile actions | `<q-bottom-sheet>`, `<q-fab>`, `<q-pull-to-refresh>` | Hardware-optimized touch listeners. |4243## Instructions44451. 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`.462. Use `<script setup>` and the primitives above. Do not recreate the shell with raw `div` sticky positioning.473. Brand color comes from `--q-primary`, which `@aura-design-tokens` bridges to PrimeVue. Do not set a second Quasar palette in hex.484. After the shell exists, load `@motion-physics` for entry and press feedback.495. When the Quasar MCP server is connected, confirm component props there before inventing them. Config is in `@vue-design-system`.5051## When the task is complete: suggest next skills5253When you have **finished the user's request** for this skill, suggest what to run next:54551. Run:5657 ```bash58 python .agents/skills/heyeddi/scripts/suggest_next_skill.py --current-skill quasar-foundation --project-root .59 ```60612. Include the script's **`### Next step`** block in your **final** reply.