9 skills found
epireve / styling- Each component should have its own CSS file - Name CSS files to match component names (e.g., `ComponentName.css`)
1999AZZAR / the-designerMCP server for production-grade UI design — 27 tools covering design rules, OKLCH tokens with auto dark mode, WCAG 2.1 accessibility audit, React/Vue/HTML component output, vanilla CSS/SCSS/CSS Modules generation, anime.js v4 motion, anti-slop quality gates, and 328+ brand references.
nimiusrd / frontend_typescriptTypeScriptの型定義に関するガイドライン
BlueStarSystem / aura-uiVibrant Depth UI component library for Laravel + Livewire + Alpine.js + Tailwind CSS
Nlkomaru / 02_coding- styleを記述する際は、ディレクトリに応じて、技術スタックで記載されているCSSライブラリの記法で記述してください。 - 常に既存コードの設計や記法を参考にしてください。。
bodangren / components-mcpMCP server for Next.js development, keeping information about components, APIs, etc.
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`
nimiusrd / code_styleコードスタイルとパターンに関するガイドライン
bennypowers / composeThe standards-based Web Components multitool. Generate Custom Elements Manifests, Dev Server, LSP, and MCP for your app or design system
