Run any Skill in Manus with one click

vue-conventions

Vue/Nuxt code conventions for SFC structure, props, state, template directives, and composables. Load whenever writing or editing Vue Single-File Components (.vue) or Nuxt-specific code anywhere in this repo — components, pages, layouts, composables, or plugins.

Run Skill in Manus

Overview

Install command

npx skills add https://github.com/lttr/jedlik-nejedlik --skill vue-conventions

Copy and paste this command into Claude Code to install the skill

Source

lttr/jedlik-nejedlik

Stars0

Forks0

UpdatedMay 19, 2026 at 19:36

SKILL.md

readonly

name	vue-conventions
description	Vue/Nuxt code conventions for SFC structure, props, state, template directives, and composables. Load whenever writing or editing Vue Single-File Components (.vue) or Nuxt-specific code anywhere in this repo — components, pages, layouts, composables, or plugins.

Vue/Nuxt Code Conventions

Apply these whenever creating or modifying .vue files or Nuxt composables/plugins in this repo.

Vue SFC Structure

ALWAYS place <template> first in the SFC, before <script> and <style>.
ALWAYS use <script setup lang="ts">.
PREFER grouping by logical concern, not by type (data/methods/computed).

Props & State

ALWAYS use TypeScript type-based defineProps(), never runtime PropType.
ALWAYS use type-based defineEmits(), never runtime array syntax.
ALWAYS destructure props directly from defineProps() for reactivity + inline defaults. Do not use withDefaults or assign to a props variable. If the script uses no props, call defineProps() without destructuring.
ALWAYS use same-name shorthand :propName instead of :propName="propName".
NEVER mutate props or their nested properties; emit changes to the parent.
ALWAYS keep computed properties pure — no mutations, no async, no logging.
USE defineModel() for two-way binding instead of manual prop+emit pairs.
PREFER ref() over reactive() for state.
PREFER VueUse composables over custom browser/DOM/state implementations (e.g. useEventListener over manual addEventListener + cleanup). @vueuse/nuxt is installed and auto-imports.

Template Directives

ALWAYS use v-for="item of items", never v-for="item in items".

Composables

PREFER toValue() to accept refs, getters, or plain values as input in shared composables.
PREFER grouping composable code by concern/feature, not by Vue API type.
PREFER extracting calculations to pure helper functions; the composable only handles reactivity.
PREFER plain utility functions over composables unless reactivity or lifecycle hooks are needed. Expose state; let components handle presentation.

More from this repository

same repository

implement

lttr/jedlik-nejedlik

Full autonomous feature implementation from customer spec to PR. Use when user provides a customer spec (file path, inline text, or ticket reference) and wants end-to-end implementation including spec/plan artifacts, feature branch, coding, verification, commits, and PR creation.

2026-05-190

monitor-deploy

lttr/jedlik-nejedlik

Monitor Coolify deployment of jedlik-nejedlik-production triggered by git push. Streams build logs, filters errors live, checks final status, and suggests fixes if deployment failed. Use when user says "monitor deploy", "watch deployment", "check deploy", or after pushing to master.

2026-05-010

gdoc-to-spec

lttr/jedlik-nejedlik

Download a Google Doc as markdown and turn it into an .aiwork spec ready for the `implement` skill. Detects inline editor notes (e.g. "Přeformulovala bych", "KLIKACÍ TLAČÍTKO", "@@", strike-through remarks) and converts them into `` markdown comments so the implementer sees them as actionable items. Trigger when the user pastes a docs.google.com URL and wants to import it as a spec, or says "stáhni gdoc", "import gdoc", "gdoc as spec", "gdoc → spec".

2026-04-290

Source

lttr

lttr/jedlik-nejedlik

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	vue-conventions
description	Vue/Nuxt code conventions for SFC structure, props, state, template directives, and composables. Load whenever writing or editing Vue Single-File Components (.vue) or Nuxt-specific code anywhere in this repo — components, pages, layouts, composables, or plugins.

Vue/Nuxt Code Conventions

Apply these whenever creating or modifying .vue files or Nuxt composables/plugins in this repo.

Vue SFC Structure

ALWAYS place <template> first in the SFC, before <script> and <style>.
ALWAYS use <script setup lang="ts">.
PREFER grouping by logical concern, not by type (data/methods/computed).

Props & State

ALWAYS use TypeScript type-based defineProps(), never runtime PropType.
ALWAYS use type-based defineEmits(), never runtime array syntax.
ALWAYS destructure props directly from defineProps() for reactivity + inline defaults. Do not use withDefaults or assign to a props variable. If the script uses no props, call defineProps() without destructuring.
ALWAYS use same-name shorthand :propName instead of :propName="propName".
NEVER mutate props or their nested properties; emit changes to the parent.
ALWAYS keep computed properties pure — no mutations, no async, no logging.
USE defineModel() for two-way binding instead of manual prop+emit pairs.
PREFER ref() over reactive() for state.
PREFER VueUse composables over custom browser/DOM/state implementations (e.g. useEventListener over manual addEventListener + cleanup). @vueuse/nuxt is installed and auto-imports.

Template Directives

ALWAYS use v-for="item of items", never v-for="item in items".

Composables

PREFER toValue() to accept refs, getters, or plain values as input in shared composables.
PREFER grouping composable code by concern/feature, not by Vue API type.
PREFER extracting calculations to pure helper functions; the composable only handles reactivity.
PREFER plain utility functions over composables unless reactivity or lifecycle hooks are needed. Expose state; let components handle presentation.