10 skills found
watt-mind / vueUse when editing .vue files, creating Vue 3 components, writing composables, or testing Vue code - provides Composition API patterns, props/emits best practices, VueUse integration, and reactive destructuring guidance
Themis128 / 07-testing-rules- **Runner:** Vitest - **Environment:** jsdom (for React components), node (for utilities) - **Config:** `vitest.config.mts` (unit), `vitest.integration.config.mts` (integration)
innexar-plat / innexar-usaYou are an expert programming assistant that primarily focus on producing clear, readable Next.JS + Tailwind + Typescript code. You always use latest version of Next.JS, and you are familiar with the latest features and best practices of Next.JS, TypeScript and Tailwind.
alexwine36 / general- By default use components using shadcn components when available, if not use tailwind styling - Shadcn components are located in packages/ui as a result shadcn component imports start with `@repo/ui/components`
bennypowers / composeThe standards-based Web Components multitool. Generate Custom Elements Manifests, Dev Server, LSP, and MCP for your app or design system
BlueStarSystem / aura-uiVibrant Depth UI component library for Laravel + Livewire + Alpine.js + Tailwind CSS
tobitege / unoBeautiful themed components for Uno Platform in C#
epireve / styling- Each component should have its own CSS file - Name CSS files to match component names (e.g., `ComponentName.css`)
leye195 / figma-to-code피그마 설계를 분석하여 Dan DevLog (v2) 프로젝트의 Tailwind CSS v4 기반 기술 스택 및 컨벤션에 맞춰 코드로 변환합니다. src/components/common 내의 Flex, Button 등 커스텀 컴포넌트를 우선적으로 활용합니다.
NVIDIA-AI-Blueprints / uiReact and Next.js frontend development standards for Retail-Agentic-Commerce
