project-frontend-design

comprehensive design guide for the Meatballs project, combining high-quality frontend principles with the specific "Craft & Chao" design system. Use this skill for all frontend work in this project.

16 stars

Best use case

project-frontend-design is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

comprehensive design guide for the Meatballs project, combining high-quality frontend principles with the specific "Craft & Chao" design system. Use this skill for all frontend work in this project.

Teams using project-frontend-design should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/project-frontend-design/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/design/project-frontend-design/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/project-frontend-design/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How project-frontend-design Compares

Feature / Agentproject-frontend-designStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

comprehensive design guide for the Meatballs project, combining high-quality frontend principles with the specific "Craft & Chao" design system. Use this skill for all frontend work in this project.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

This skill defines the specific design language for the **Meatballs** project, merging the "Craft & Chao" aesthetic with high-quality production standards. Avoid generic "AI slop" by strictly adhering to these specific theme patterns.

## 🎨 Core Design Philosophy: "Craft & Chao"

Commit to this bold aesthetic direction:
- **Warm & Authentic**: Evoke appetite and warmth using rich orange-red gradients. The site should feel "cooked", not sterile.
- **Premium Quality**: Use refined typography, generous spacing, and glass-morphism effects (`backdrop-blur`).
- **Mobile-First**: Designs must be optimized for single-column, touch-friendly interactions (min 44px targets).

## 📐 Theme & Aesthetics Guidelines

### 1. Color System
Do not use generic colors. Use the specific project palette:
- **Primary**: `orange-500` to `red-600` gradients. Use for CTAs, price highlights.
- **Background**: `#FDFBF7` (Warm Off-White). **Never** use pure white `#FFFFFF` for the main page background.
- **Neutral**: `slate-50` to `slate-900` for text and borders.
- **Semantic**: `green` for success, `red` for warning.
- **Technique**: Use opacity layers (`/90`, `/50`) and gradients to create depth and sophistication.

### 2. Typography
Avoid generic font stacks.
- **UI & Body**: `font-sans` (Clean, readable).
- **Accents & Prices**: `font-serif` (Premium, editorial feel).
- **Hierarchy**:
  - Hero: `text-4xl`, Extrabold.
  - Prices: `text-5xl` (Success page), `text-xl` (Cards).
  - Labels: Uppercase, `text-xs`, Bold, wide tracking.

### 3. Component Patterns
- **Buttons**:
  - Primary: Gradient `from-orange-500 to-red-600`, `rounded-full`, with hover scale effects.
  - Secondary: `orange-50` background, `orange-700` text.
- **Cards**:
  - White background, `rounded-3xl` (Very rounded), `shadow-sm` transitioning to `shadow-xl` on hover.
- **Inputs**: `rounded-xl`, `bg-slate-50`, focus ring in `orange-500`.

### 4. Motion & Interaction
Create a living interface, not a static page.
- **Micro-interactions**: Use `active:scale-95` on clickable elements.
- **Transitions**: Default to `duration-300`. Use `duration-700` for entrances.
- **Feedback**: Visual state must reflect user actions immediately (e.g., pulse animations).

## 🔧 Implementation Strategy

- **Tailwind CSS**: Use utility classes for almost everything.
- **Icons**: Lucide React (`size={14}` to `size={20}`).
- **Images**: High-quality food photography with gradient overlays for text readability.
- **Internationalization (i18n)**: All user-facing text must be internationalized using `next-intl`. **Never** hardcode strings; use translation keys (e.g., `t('menu.title')`).

## 🚫 Anti-Patterns (What to Avoid)
- **Generic Aesthetics**: Do not use "startup blue" or default Bootstrap/Material styles.
- **Sterility**: Avoid cold grays or pure whites without the warm off-white base.
- **Flatness**: Always use shadows, gradients, or blur to add depth to flat elements.
- **Tiny Targets**: Never make touch targets smaller than 44px.

**Remember**: The goal is a "Premium, Warm, Food-Focused" experience. Implementation must be meticulous and polished.

Related Skills

ui-ux-designer

16
from diegosouzapw/awesome-omni-skill

Create interface designs, wireframes, and design systems. Masters user research, accessibility standards, and modern design tools.

ui-ux-design-system

16
from diegosouzapw/awesome-omni-skill

Expert in building premium, accessible UI/UX design systems for SaaS apps. Covers design tokens, component architecture with shadcn/ui and Radix, dark mode, glassmorphism, micro-animations, responsive layouts, and accessibility. Use when: ui, ux, design system, shadcn, radix, tailwind, dark mode, animation, accessibility, components, figma to code.

ui-designer

16
from diegosouzapw/awesome-omni-skill

Generate and serve live HTML/CSS/JS UI designs from natural language prompts. Use when the user asks to design, create, build, or prototype a website, landing page, UI, dashboard, web page, or frontend mockup. Also triggers on requests to update, tweak, or iterate on a previously generated design. Replaces traditional UI design + frontend dev workflow.

ui-design

16
from diegosouzapw/awesome-omni-skill

Applies consistent renderer UI/UX implementation patterns using a Vercel-inspired white theme, strong accessibility defaults, and repository component conventions.

ui-design-styles

16
from diegosouzapw/awesome-omni-skill

Comprehensive guidance for applying modern UI design styles, including Soft UI, Dark Mode, Flat Design, Neumorphism, Glassmorphism, and Aurora UI Gradients. Use when a user asks to: (1) Apply a specific UI style to a project, (2) Create a modern, visually appealing UI prototype, (3) Improve accessibility while following design trends, or (4) Understand the technical implementation of specific UI effects like frosted glass or soft shadows.

ui-design-create-component

16
from diegosouzapw/awesome-omni-skill

Guided component creation with proper patterns Use when: the user asks to run the `create-component` workflow and the task requires multi-step orchestration. Do not use when: the task is small, single-step, and can be completed directly without orchestration overhead.

ui-design-a11y

16
from diegosouzapw/awesome-omni-skill

无障碍设计审查与修复能力。

u04425-experiment-design-for-nutrition-and-meal-planning

16
from diegosouzapw/awesome-omni-skill

Operate the "Experiment design for nutrition and meal planning" capability in production for nutrition and meal planning workflows. Use when mission execution explicitly requires this capability and outcomes must be reproducible, policy-gated, and handoff-ready.

u2615-regression-sentinel-design-for-household-logistics

16
from diegosouzapw/awesome-omni-skill

Operate the "regression sentinel design for household logistics" capability in production for regression sentinel design for household logistics workflows. Use when mission execution explicitly requires this capability and outcomes must be reproducible, policy-gated, and handoff-ready.

tool-design-style-selector

16
from diegosouzapw/awesome-omni-skill

Use when you need to define or converge a project's visual direction. Scan project documentation to identify intent, then produce a design-system.md (either preserve existing style or pick from 30 presets). Triggers: design system, design spec, UI style, visual style, design tokens, color palette, typography, layout. Flow: scan → intent → (gate) preserve vs preset → deploy design-system.md after confirmation → (default) implement UI/UX per design-system.md (plan first, then execute).

test-pyramid-design

16
from diegosouzapw/awesome-omni-skill

Design optimal test pyramids with unit/integration/E2E ratios. Identify anti-patterns and recommend architecture-specific testing strategies.

tailwind-design-system

16
from diegosouzapw/awesome-omni-skill

Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI...