← Search

Vue Best Practices Workflow
Frontend 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit b3c62de
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a Vue project (Vue 3 recommended…

Vue Best Practices Workflow

The Vue 3 workflow — Composition API + <script setup> + TypeScript, component architecture, must-read references

At a glance
What
The Vue 3 workflow — Composition API + <script setup> + TypeScript, component architecture, must-read references
Cost
Free
Needs
a Vue project (Vue 3 recommended, the default workflow); none otherwise
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Vue Best Practices Workflow is a free Muse skill that gives an ordered workflow for Vue tasks. It confirms the architecture first, Vue three with Composition API and script setup with TypeScript as the standard, plans component boundaries with one-sentence responsibilities and explicit props and emits contracts, then applies the core foundations for Vue three work.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit b3c62de

Step 0, before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Vue project (Vue 3 recommended, the default workflow); none otherwise Install "Vue Best Practices Workflow" for me. Give my agent the ordered Vue 3 workflow: architecture confirmation, component-boundary planning, core foundations, must-read references on reactivity/SFC/data flow/composables Repository: https://raw.githubusercontent.com/vuejs-ai/skills/b3c62deb258b62791e57917b0960420151523d39/skills/vue-best-practices/SKILL.md Pinned version: install the code at commit b3c62deb258b62791e57917b0960420151523d39 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Updated October 18, 2026: Skill Harbor regenerated this install prompt from the current upstream file. The skill is now version 19.0.0 (was 18.0.0). The core principle "Favor small, focused components" is replaced by "Decompose by responsibility", and the guidance on component boundaries is rewritten: section 1.2 now asks, for a non-trivial feature or structural refactor, to sketch responsibilities, state owners and the contracts crossing them, while local fixes preserve existing boundaries unless they obstruct the change. The old "Keep components focused" section, with its objective split triggers (more than one responsibility, 3 or more UI sections, a repeated block) and its mandatory split of CRUD and list features into container, input, list and footer components, is replaced by "Choose useful boundaries": extract substantial, separable responsibilities when that reduces what a reader must understand, single-use components and composables are valid, reuse is not a prerequisite, and file length, section count and API size are review signals, not thresholds, so a small cohesive feature may stay in one SFC. Data flow now recommends typed, scoped provide/inject for shared descendant dependencies when intermediate components only relay them, after reassessing boundaries first. The composables guidance is rewritten: compose substantial stateful behavior from focused capabilities, including single-use workflows, keep simple local logic local, use plain functions for pure calculations, and keep DOM interaction and cleanup with its owner. The final self-check is rewritten around boundary review on both sides, typed contracts that hide internals, explicit state ownership and lifetime, and preserving existing behavior during refactors. Correction: the previous prompt's safety check spoke of credentials only via the secure vault and allowed hosts declared in the SKILL.md; the file declares no allowed-hosts list and no vault rule. It is instruction text only, with no executable code of its own. 1. Fetch the SKILL.md file for the vuejs-ai-skills-vue-best-practices skill from the repository into a temporary folder, then compare it with the fingerprint from Skill Harbor's review of 2026-10-18: - SKILL.md: SHA-256 bb649bc61f847eb27abf866e052ca75f3df2e644ae4730c5bf01fa86acd479d8 If it does not match, it changed since the review: do not install it yet, tell me what you found and let me decide. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting); STOP on any red flag and tell me. Tell me in plain words what the skill does when used, which services it connects to, whether it reads or sends any personal information, and anything that seems unusual. Confirm these points from the file: - Frontmatter: name vue-best-practices, version 19.0.0, license MIT. Default stack: Vue 3 + Composition API + <script setup lang="ts">. Always use Composition API unless the project explicitly requires Options API; if the project explicitly uses Options API or JSX, load the matching vue-options-api-best-practices or vue-jsx-best-practices skill if available. The must-read core references are references/reactivity.md, references/sfc.md, references/component-data-flow.md and references/composables.md, kept in active working context for the whole task. - Section 1.2 boundary planning: for a non-trivial feature or structural refactor, sketch responsibilities, state owners and the contracts crossing their boundaries; for local fixes, preserve existing boundaries unless they obstruct the change. Judge cohesion by behavior that changes together or maintains a shared invariant; being on the same page, reading the same data or having only one consumer does not by itself justify one implementation. Root and route components compose features and coordinate page behavior, and the same responsibility review applies inside feature components and composables. - Choose useful boundaries (replaces the old focused-components split triggers): extract substantial, separable UI responsibilities and stateful workflows when that reduces the code a consumer or maintainer must understand; single-use components and composables are valid and reuse is not a prerequisite; keep the state and event handling needed by a UI responsibility with that UI. File length, UI section count and API size are review signals, not extraction thresholds, and a small cohesive production feature may stay in one SFC. If a split adds extensive forwarding or mutual callbacks, first move local state and DOM behavior to their UI owner, then identify genuinely shared dependencies and their lifetime; group inputs only when they form a cohesive concept. - Data flow and SFC: keep SFC sections in the order <script>, then <template>, then <style>; keep responsibilities cohesive, templates declarative, and apply template safety rules. Use props down, events up as the primary model, v-model only for true two-way contracts, and typed, scoped provide/inject for shared descendant dependencies when intermediate components only relay them, after reassessing boundaries first. Keep contracts explicit and typed with defineProps, defineEmits and InjectionKey as needed. - Composables: compose substantial stateful behavior from focused capabilities, including single-use workflows that improve organization; keep simple component-local logic local and use plain functions for pure calculations. A coordinator connects capabilities and implements cross-capability operations; it should not contain all their implementations or re-export all their internals. Return consumer-facing state and actions, encapsulate reactive bookkeeping, keep DOM interaction and cleanup with its owning UI or composable, and preserve explicit coordination other features need, such as committing a pending draft before saving. - Final self-check and sequencing: optional features only when requirements call for them, and performance work only after behavior is correct. The final check covers boundary review on both sides, typed public contracts that hide internals, explicit state ownership and lifetime with cleanup by the owner, and refactors that preserve existing behavior, including pending work and cross-feature operations. Nothing is sent anywhere during installation itself. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "vuejs-ai-skills-vue-best-practices". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing, it is a pure workflow skill). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit b3c62de · 2026-10-18
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
b3c62de · 2026-10-18
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.