Automated summary
Provides the Vibecode brand system—colors, typography, spacing, radii, and component styling—for building consistent UI.
Strengths
- Clear color tokens, type scale, and 8px spacing system
- Ready-to-use CSS snippets for buttons, inputs, and cards
- Guidance for radius, shadows, and glassmorphism surfaces
Limitations
- Tied to the Vibecode brand and not portable to other identities
- Does not cover dark mode, responsive breakpoints, or detailed accessibility states
- Component coverage is limited to buttons, inputs, and cards
Use it when creating or restyling UI components for the Vibecode app and needing to match its visual identity.
Avoid it for non-Vibecode projects or when a different design system or full dark theme is required.
Security analysis
SafeThe skill contains only static design system documentation (colors, typography, spacing, CSS snippets) with no declared tools or instructions to execute code, access networks, or modify files. There is no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Create a Vibecode pricing card using the official brand colors, typography, spacing, and border radius tokens.Style this React settings form with Vibecode primary and secondary buttons, input focus states, and the 8px spacing system.Review this landing page against the Vibecode brand design guide and list deviations in color, typography, spacing, and component styling.name: vibecode-brand-design description: Vibecode brand design system with colors, typography, spacing, and component guidelines. Use when designing UI, styling components, or ensuring brand consistency in the Vibecode app.
Vibecode Brand Design Guide
This skill provides the official Vibecode brand design system. Follow these guidelines when creating or styling UI components.
Core Design Philosophy
Vibecode is a modern, tech-forward brand emphasizing clarity, accessibility, and innovation. Focus on creating intuitive digital experiences while maintaining visual consistency.
Color System
Background Colors
- Primary Background: Clean whites (
#FFFFFF) and light neutrals (#F8FAFC,#F1F5F9) - Secondary Background: Soft grays for depth and hierarchy (
#E2E8F0,#CBD5E1)
Text Colors
- Primary Text: Dark charcoal for readability (
#1E293B,#0F172A) - Secondary Text: Medium grays for supporting information (
#64748B,#94A3B8)
Accent Colors (Kiwi/Teal Scale)
The primary accent palette - vibrant, modern, suggesting growth and technology:
#14B8A6- Teal 500 (Primary accent)#0D9488- Teal 600 (Hover states)#0F766E- Teal 700 (Active states)#2DD4BF- Teal 400 (Light accent)#5EEAD4- Teal 300 (Backgrounds)
Secondary Accent (Blueberry)
Deep blue tones for contrast and professional grounding:
#3B82F6- Blue 500#2563EB- Blue 600#1D4ED8- Blue 700
Typography
Font Family
Primary Typeface: Play (Google Fonts) - Modern, clean aesthetic
font-family: 'Play', sans-serif;
Type Scale
| Level | Size | Weight | Line Height | Usage | |-------|------|--------|-------------|-------| | Display | 48px | 700 | 1.1 | Hero headings | | H1 | 36px | 700 | 1.2 | Page titles | | H2 | 28px | 600 | 1.25 | Section headings | | H3 | 22px | 600 | 1.3 | Subsections | | H4 | 18px | 500 | 1.4 | Card titles | | Body | 16px | 400 | 1.5 | Main content | | Small | 14px | 400 | 1.5 | Captions, labels | | Tiny | 12px | 400 | 1.4 | Fine print |
Typography Rules
- Use weight variation for emphasis rather than size alone
- Maintain consistent line-height for readability
- Apply color strategically to guide user attention
Spacing System
Use an 8px base unit for consistent spacing: | Token | Value | Usage | |-------|-------|-------| | xs | 4px | Tight spacing, inline elements | | sm | 8px | Between related elements | | md | 16px | Standard padding | | lg | 24px | Section spacing | | xl | 32px | Large gaps | | 2xl | 48px | Major sections | | 3xl | 64px | Page-level spacing |
Border Radius
Subtle rounded corners for professionalism:
- Small: 4px - Buttons, inputs, tags
- Medium: 8px - Cards, panels
- Large: 12px - Modals, large containers
- Full: 9999px - Pills, avatars
Component Guidelines
Buttons
/* Primary Button */
.btn-primary {
background: #14B8A6;
color: white;
padding: 12px 24px;
border-radius: 8px;
font-weight: 500;
}
.btn-primary:hover {
background: #0D9488;
}
/* Secondary Button */
.btn-secondary {
background: transparent;
border: 1px solid #E2E8F0;
color: #1E293B;
padding: 12px 24px;
border-radius: 8px;
}
Input Fields
.input {
border: 1px solid #E2E8F0;
border-radius: 8px;
padding: 12px 16px;
background: #FFFFFF;
}
.input:focus {
border-color: #14B8A6;
outline: none;
box-shadow: 0 0 0 3px rgba(20, 184, 166, 0.1);
}
Cards
.card {
background: #FFFFFF;
border-radius: 12px;
padding: 24px;
box-shadow: 0 1px 3px rgba(0, 0, 0, 0.1);
}
Effects
Glassmorphism
For overlay elements and floating panels:
.glass {
background: rgba(255, 255, 255, 0.8);
backdrop-filter: blur(12px);
border: 1px solid rgba(255, 255, 255, 0.2);
}
Shadows
| Level | Value | Usage |
|-------|-------|-------|
| sm | 0 1px 2px rgba(0,0,0,0.05) | Subtle elevation |
| md | 0 4px 6px rgba(0,0,0,0.1) | Cards, dropdowns |
| lg | 0 10px 15px rgba(0,0,0,0.1) | Modals, popovers |
| xl | 0 20px 25px rgba(0,0,0,0.15) | Major floating elements |
Interaction States
Hover
- Subtle color darkening (10-15%)
- Optional slight elevation increase
Focus
- Clear outline using accent color
box-shadow: 0 0 0 3px rgba(20, 184, 166, 0.2)
Active/Pressed
- Slightly darker than hover
- Scale down subtly if appropriate (
transform: scale(0.98))
Disabled
- Opacity: 50%
- Cursor: not-allowed
Tailwind CSS Variables
Add to your Tailwind config:
colors: {
vibecode: {
kiwi: {
50: '#F0FDFA',
100: '#CCFBF1',
200: '#99F6E4',
300: '#5EEAD4',
400: '#2DD4BF',
500: '#14B8A6',
600: '#0D9488',
700: '#0F766E',
800: '#115E59',
900: '#134E4A',
},
blueberry: {
500: '#3B82F6',
600: '#2563EB',
700: '#1D4ED8',
}
}
}
Do's and Don'ts
Do's
- Maintain grid consistency
- Use accent colors purposefully and sparingly
- Ensure accessible contrast ratios (WCAG AA minimum)
- Apply effects subtly
- Keep layouts clean and organized
Don'ts
- Avoid overusing accent colors - they should highlight, not dominate
- Don't break grid systems arbitrarily
- Avoid excessive shadows that clutter the interface
- Don't compromise readability for aesthetics
- Avoid generic AI-generated aesthetics (purple gradients, Inter font)
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/vibecode-brand-design-system-msfn19zj/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/vibecode-brand-design-system-msfn19zj' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/vibecode-brand-design-system-msfn19zj/download' --output '.skill-downloads/vibecode-brand-design-system-msfn19zj/SKILL.md.part' && mv '.skill-downloads/vibecode-brand-design-system-msfn19zj/SKILL.md.part' '.skill-downloads/vibecode-brand-design-system-msfn19zj/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/vibecode-brand-design-system-msfn19zj/SKILL.md' && test -s '.skill-downloads/vibecode-brand-design-system-msfn19zj/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/vibecode-brand-design' && cp -R '.skill-downloads/vibecode-brand-design-system-msfn19zj' '.claude/skills/vibecode-brand-design'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/vibecode-brand-design-system-msfn19zj'openskills read 'vibecode-brand-design-system-msfn19zj'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/vibecode-brand-design-system-msfn19zj/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.