com um clique
frontend-design
Aesthetic direction for designs outside an existing brand system
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Menu
Aesthetic direction for designs outside an existing brand system
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Export a selected element from the canvas as PNG, JPEG, OGraf bundle, Lottie, or video. Saves to the project's exports/ folder; the chat renders the result inline as an artifact card.
Keep the canvas surface coherent across its three places — the canonical starter at `mcp/starters/DesignCanvas.jsx`, the byte-identical demo copy at `web/projects/demo/design-canvas.jsx`, and the host-side wiring in `web/src/lib/tweakBridge.ts` plus `mcp/CANVAS_PROTOCOL.md`. Use whenever the diff touches any of those files, or when the user says "fix the canvas", "update DesignCanvas", "tweak the design canvas", "the canvas isn't working in new projects", or anything similar. Without this rule, fixes land in one place and silently miss the other — the demo project tests stale code, or new projects get content that doesn't match what's been verified.
Run and triage AI Atelie's Critical User Journey (CUJ) for every PR — the single end-to-end test that proves a user can open the app, create a project, drive the Claude Code agent, and see the canvas render. Before running, gate by inspecting the PR diff for changes that plausibly affect the journey (routes, onboarding, canvas, chat, selectors). On failure, walk a five-step triage to decide "broken feature" vs "stale test" before touching either. Use whenever the user says "run the CUJ", "validate the canonical flow", "ship-readiness check", or before approving any PR.
Aesthetic and convention guide for editing AI Atelie's own chrome — the editor, canvas frame, toolbars, sidebars, dialogs, settings, projects screen. Use whenever the diff touches `web/src/` (especially `*.module.css`, `index.css`, `styles/themes.css`, `lib/theme.ts`) or any user-facing component on the host app. Opts into the canonical craft rulebook at `atelier/` and layers the host-app-specific posture (two-axis theme×design system, warm-cream + Claude rust, restraint over flourish) on top. NOT for user-generated designs inside the canvas — those use the product skill at `skills/frontend-design/`.
Run AI Atelie's journey suite and inject inline-rendering evidence (per-journey video + screenshot, in a 4-column markdown table) into the current PR's body. Use whenever the user says "post evidence", "run journeys", "update PR with videos", or after `ship-task` opens a PR. Wraps `bun run journeys`; idempotent — re-runs replace the evidence block instead of appending.
Take an AI Atelie task — issue, ticket, or ad-hoc ask — all the way from description to merged-ready PR. Use whenever the user says "implement X and ship it", "work on issue
| name | frontend-design |
| display | Frontend design |
| description | Aesthetic direction for designs outside an existing brand system |
| kind | aesthetic |
| body_status | reconstructed |
| sources | ["https://claude.com/blog/improving-frontend-design-through-skills"] |
Build production-grade frontend interfaces with a bold, distinctive point of view. The user provides requirements — a component, a page, an interactive experience — and the job is to design and build something that's not just competent, but striking and memorable.
Use this when there's no existing brand or design system to defer to. Without explicit aesthetic direction the model converges on the same look every time: white background, purple gradient, Inter, rounded cards, system-blue accent. Break that default by committing to a clear direction up front and executing it with precision.
If the user has provided a DESIGN.md at the project root, follow that direction first. This skill is the fallback when no spec is present.
Before writing any code, decide:
Bold maximalism and refined minimalism both work. The variable that matters is intentionality, not intensity. Pick a direction and execute it vigorously.
Typography. Typography carries the design's voice. Choose fonts with personality. Default fonts signal default thinking — skip Arial, Inter, Roboto, Space Grotesk, system stacks. Display type should be expressive, even risky. Body text should be legible and refined. Pair display and body like actors in a scene. Work the full range — size, weight, case, letter-spacing — to establish hierarchy.
Color and theme. Take a position. Bold and saturated, moody and restrained, or high-contrast and minimal — pick one. Lead with a dominant color, punctuate with sharp accents. Avoid timid, evenly-distributed palettes that hedge. Use CSS variables so the position stays consistent across the surface.
Motion. Use animation for effects and micro-interactions. Prefer CSS-only solutions for HTML; reach for the Motion library when in React. Concentrate effort on high-impact moments — one well-orchestrated page-load with staggered reveals creates more delight than scattered micro-interactions everywhere. Use scroll-triggered and hover states that surprise.
Spatial composition. Unexpected layouts. Asymmetry. Overlap and z-depth. Diagonal flow. Grid-breaking elements. Dramatic scale jumps. Full-bleed moments. Generous negative space — or controlled density. Commit to one extreme.
Backgrounds and visual detail. Create atmosphere and depth instead of defaulting to solid fills. Layer effects that match the chosen aesthetic: gradient meshes, noise and grain, geometric patterns, layered transparencies and glassmorphism, dramatic or soft shadows and glows, parallax depth, decorative borders, clip-path shapes, print-inspired textures (halftone, duotone, stipple), knockout typography, custom cursors.
NEVER use generic AI-generated aesthetics. That means:
INSTEAD: distinctive fonts. Bold, committed palettes. Layouts that surprise. Bespoke details. Every choice rooted in the specific context of this design.
Maximalist designs need elaborate code — extensive animation, layered effects, dense composition. Minimalist or refined designs need restraint, elegance, and precision. Both need careful attention to spacing, typography, and subtle detail. Excellence comes from executing the chosen vision well — not from picking a safe middle.
Build creatively on the user's intent. Make unexpected choices that feel genuinely designed for the context. Actively explore the full range — light and dark themes, unusual font pairings, substantially varied directions. Let the specific context drive choices, not familiar defaults.