원클릭으로
vue-component-setup
Rules for vue component setup. Use this when writing a new vue component or when reviewing an exisinging component.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Rules for vue component setup. Use this when writing a new vue component or when reviewing an exisinging component.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | vue-component-setup |
| description | Rules for vue component setup. Use this when writing a new vue component or when reviewing an exisinging component. |
| license | MIT |
Use these patterns when createing a vue components
<template>...</template>
<script setup lang="ts">
...
</script>
<style scoped>
...
</style>
Only use style for custom animations, use unocss for all styling
Script setup GOOD
const props = defineProps<{collection: { id: string name: string }}>()
const emit = defineEmits<{ updated: [newId: string] }>()
const model = defineModel({ required: true }) // making the v-model required
const model = defineModel({ default: 0 }) // providing a default value
Use VueUse composables that are installed in this project, vueuse needs to be imported GOOD
import { onClickOutside } from '@vueuse/core'
onClickOutside(themeMenuRef, () => { ... }
When using refs and functions from pinia stores GOOD
// do not import useSomeStore they are always auto-imported
const { progress } = storeToRefs(useAdminStore()) // use a reactive ref from store
const { setProgress } = useAdminStore() // use a store action
const archiveProgress = computed(() => progress.value.archive)
function onUpdate(event: string) {
setProgress(event)
}
Never use the following patterns BAD
// utils/ and shared/types/ are alway auto-imported
import { utilFkt } from '../utils/utilName'
import { MovieMetadata } from '../shared/types/movie' alway
One sentence about this skill. Use this skill when: "keyword1" "keyword combination"
Guide for verifying frontend changes using chrome-devtools MCP. Use this when you need to verify UI changes, check for console errors, or test frontend functionality after making changes to Vue components, pages, or styles.
Guide for checking and fixing Nuxt 4 auto-import usage. Use this when reviewing impors in Vue components, composables, or TypeScript files in a Nuxt 4 project.
Guide for creating commit message. This skill should be used when you try to create a commit message.