# Quasar Foundation

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

- Skill: `heyeddi-com/quasar-foundation` (Agent Skill, multi-file: 9 files)
- Install (CLI): `npx get-skill add heyeddi-com/quasar-foundation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/heyeddi-com/quasar-foundation/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: HeyEddi-com (https://skillmd.com/u/heyeddi-com)
- Updated: 2026-11-11
- Page: https://skillmd.com/skills/heyeddi-com/quasar-foundation

---


# 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

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

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:

   ```bash
   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.

