0 vue rules available
Browse optimized Kiro rules specifically designed for Vue.js development. These rules help Kiro's AI understand Vue.js best practices and patterns.
Vue 3's Composition API represents a significant shift from the Options API, and AI rules need to reflect your team's preferences. Rules that specify ref vs reactive usage, component communication patterns, and Pinia store structure help generate consistent Vue code that matches your project's conventions.
When configuring Kiro for Vue.js development, consider these recommendations:
Vue rules commonly cover Composition API with script setup, Pinia for state management, and Vue Router for navigation. Many include patterns for Nuxt.js integration and TypeScript support with defineComponent.
Most modern rules target Vue 3 with Composition API. If you're maintaining a Vue 2 project or using the Options API, look for rules explicitly tagged with 'vue2' or 'options-api'.
Vue 3 rules typically include full TypeScript support with defineComponent, typed props, and typed emits. Script setup syntax provides even better type inference with defineProps and defineEmits.
General Vue rules work with Nuxt, but for best results, look for Nuxt-specific rules that include auto-imports, useFetch patterns, and Nuxt-specific file conventions.
Create your own Kiro rules for Vue.js and share with the community.