vibe-coding
Skill4 starsChanged 12 days agoApache-2.0View on GitHub
Guide for creating modern UI without design knowledge via \"vibe coding\": React + Vite + Tailwind 4 + shadcn/ui, design briefs, style references, design tokens, production-ready components. Use for frontend interfaces, landing pages, design systems.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- xieqiyong/skillstheir own version, first seen Nov 8, 2026
- MUSE-CODE-SPACE/vibe-coding-mcptheir own version, first seen Nov 1, 2026
- OpenxIntelligence/Coding-Agent-Skillstheir own version, first seen Nov 1, 2026
- I-Onlabs/claude-code-skillstheir own version, first seen Oct 25, 2026
- realjaymes/marketingagentskillstheir own version, first seen Oct 21, 2026
- adhi-jp/agent-skillstheir own version, first seen Oct 20, 2026
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- OfficeDev/microsoft-365-agents-toolkit★ 786same name
- sarvamai/skills★ 72same name
- realjaymes/marketingagentskills★ 68same name
- Exploration-labs/Nates-Substack-Skills★ 55same name
- I-Onlabs/claude-code-skills★ 4same name
- OpenxIntelligence/Coding-Agent-Skills★ 4same name
- TabithaFanny/claude-skills-collection★ 4same name
- xieqiyong/skills★ 4same name
- HanksChen0110/skills★ 2same name
- adhi-jp/agent-skills★ 1same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill
- business-consultantSkill
- cfoSkill
- environment-setupSkill
- find-skillsSkill
- legalSkill
- linkedin-contentSkill
- prdSkill
- prepare-goalSkill
- prepare-openspec-goalSkill
- process-mappingSkill
- research-add-fieldsSkill
- research-add-itemsSkill
- research-deepSkill
- research-reportSkill
- researchSkill
- review-fixSkill
- review-loopSkill
- slidesSkill
- tax-advisorSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 11 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Create modern, professional UI without UX/UI design knowledge using AI-driven "vibe coding" - describe the vibe and feeling you want, not …
- Distinctive: line 21
Never start from scratch. Use a proven boilerplate with:
- Distinctive: line 54
Before requesting code, clarify what you want.
- Distinctive: line 64
Create a document that AI uses as reference for the entire project.
- Distinctive: line 67
Layout Structures: - When to use different layout types
- Very specific: line 76
Use the template from assets/templates/design-tokens.css.
- Very specific: line 80
Create or import design tokens in your main CSS file using @theme
- Distinctive: line 88
Use the implementation prompt template from references/implementation-prompt.md to generate production-ready React components.
- Distinctive: line 94
Don't generate entire pages.
- Distinctive: line 141
Don't request "entire landing page".
- Distinctive: line 151
If every component has different blue shades and border radius, your UI looks like Frankenstein.
- Distinctive: line 179
Design system is foundation: - Create once, use everywhere
- Distinctive: line 184
All templates and detailed guides:
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Vibe Coding
Create modern, professional UI without UX/UI design knowledge using AI-driven "vibe coding" - describe the vibe and feeling you want, not pixel-perfect designs.
What is Vibe Coding?
Vibe coding is an approach to creating interfaces where you describe the vibe and impression you want to achieve instead of precise mockups. AI translates your description into production-ready code.
This democratizes UI creation - even without design skills, you can create professional-looking interfaces.
Three Pillars of Successful Vibe Coding
1. Good Foundation (Starter Kit)
Never start from scratch. Use a proven boilerplate with:
- Configured tools (Vite, React, Tailwind CSS 4)
- Base design system (colors, typography, spacing)
- Core components
Recommended: Vibe Coding Starter Kit - React + Vite + Tailwind CSS 4 + shadcn/ui
Note: Tailwind CSS 4 requires Node.js 20+ and modern browsers (Safari 16.4+, Chrome 111+, Firefox 128+).
See references/starter-setup.md for setup instructions.
2. Good Prompts
Know how to communicate with AI to get sensible results. Use proven prompt templates from:
- references/design-brief-prompt.md - Create comprehensive design briefs
- references/implementation-prompt.md - Generate production-ready components
3. Good Context
AI must understand:
- Your design system (colors, fonts, spacing)
- Libraries you use (Tailwind, shadcn/ui)
- Style you're building (minimalist, bold, glassmorphic)
Without context: Generic, "AI-looking" design With context: Unique, professional design
See references/design-system-template.md for creating AI design style references.
Workflow
Step 1: Define Design Brief
Before requesting code, clarify what you want. Use the prompt template from references/design-brief-prompt.md to define:
- Design Style & Aesthetic - Visual style, mood, design movements
- Target Audience - Users, preferences, devices
- Key Features & Priorities - Core features, primary actions, highlights
Result: Clear brief for subsequent prompts.
Step 2: Create AI Design Style Reference
Create a document that AI uses as reference for the entire project. Use references/design-system-template.md to define:
- Visual Style - Overall aesthetic, color palette, typography, spacing
- Layout Structures - When to use different layout types
- Color Themes - Dark/light mode, accent colors
Save as design-reference.md and attach in AI context (Cursor, Claude, ChatGPT).
Step 3: Set Up Design Tokens
In Tailwind CSS 4, design tokens are defined using @theme in your CSS file instead of JavaScript config.
Use the template from assets/templates/design-tokens.css.
Design tokens are your single source of truth for colors, spacing, typography.
- Create or import design tokens in your main CSS file using
@theme - Tailwind 4 automatically generates CSS variables from your theme
- Reference in prompts: "Use colors and spacing from our design tokens"
AI will adhere to your design system.
Step 4: Implement with AI
Use the implementation prompt template from references/implementation-prompt.md to generate production-ready React components.
Best Practices
Start with Small Components
Don't generate entire pages. Start with:
- Button
- Card
- Input
- Navigation
With base components, AI easily composes them into larger layouts.
Iterate on Live Code
Vibe coding is iterative:
- Generate first version
- View in browser
- Refine prompt ("Make button larger, add hover effect")
- Regenerate
- Repeat
Use Screenshots as Input
AI (especially Claude with vision) can recreate designs from images. Find inspiration on Dribbble/Behance, screenshot, paste to AI:
Recreate this design using React and Tailwind CSS.
Maintain the layout and color scheme, but adapt it to our design system.Keep Documentation Alongside
Attach to context:
design-reference.md- Your style guidedesign-tokens.cssor main CSS file with@theme- Design systemcomponent-patterns.md- How you use your components
AI will stay consistent with your project.
Common Pitfalls
Generic "AI Design"
Without context, AI generates boring, generic UI. Always:
- Specify style (minimalist, brutalist, glassmorphic)
- Point to inspirations (e.g., "like Stripe's homepage")
- Define colors and typography
Oversized Components
Don't request "entire landing page". Split into:
- Hero section
- Features section
- Pricing section
- Footer
Smaller pieces = better control.
No Design System
If every component has different blue shades and border radius, your UI looks like Frankenstein. Create design tokens and stick to them.
Tools
Cursor (Recommended IDE)
IDE based on VS Code with built-in AI:
- Composer - Creates/modifies multiple files simultaneously
- Chat - Conversation with full project context
- Cmd+K - Inline code editing
Why Cursor? AI sees entire project - knows your components, design system, folder structure. Generates consistent code.
Shadcn/ui
Component library installable via CLI. Components are yours - copied to project for modification.
AI knows shadcn/ui well, so "use shadcn Button component" gives exactly that.
v0.dev (Optional)
Vercel tool for generating UI from text prompts. Good for quick prototypes, but code often needs refinement.
Key Takeaways
- Vibe coding works - Even without design skills, create professional UI
- 3 pillars are key - Good foundation, good prompts, good context
- AI is a tool, not magic - Needs clear brief and iteration
- Design system is foundation - Create once, use everywhere
- Get inspired, don't copy - AI helps create something unique, not generic
Resources
All templates and detailed guides:
- references/design-brief-prompt.md - Comprehensive design brief template
- references/design-system-template.md - AI design style reference structure
- references/implementation-prompt.md - Production-ready component generation prompt
- references/starter-setup.md - Tailwind CSS 4 + Vite setup guide
- assets/templates/design-tokens.css - Design tokens template for Tailwind CSS 4
Routing text before the description was cut
The description in the front matter is capped at 250 characters, because the list of skills a model sees has a character budget. The full routing text it carried before — triggers, boundaries, what the skill is not for — is kept here:
Guide for creating modern, professional UI without UX/UI design knowledge using AI-driven "vibe coding" approach. Use when the user wants to create frontend interfaces, landing pages, web components, or design systems by describing vibes/feelings instead of precise mockups. Supports React + Vite + Tailwind CSS 4 + shadcn/ui workflow with design briefs, style references, design tokens, and production-ready component generation. Ideal for developers without design background who want to build attractive, accessible interfaces.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

