Source: raw/Claude_Design_+_Claude_Skills_-_Automate_Your_Marketing_Claude_Code.md (https://www.youtube.com/watch?v=Ph-maUAiSU8) and raw/Master_Claude_Design_in_17_Minutes_for_Marketing.md (https://www.youtube.com/watch?v=aF57uCHuXgY)
Creator: Grace Leung
Platform: YouTube
Duration: 16:49 (“Claude Design + Claude Skills”, published 2026-04-25) and 16:43 (“Master Claude Design in 17 Minutes for Marketing”, published 2026-07-31)
Published: 2026-04-25 and 2026-07-31
Skill level: Intermediate (Claude Design plus Claude Code skills; one terminal step)
Grace Leung’s rule across both videos: use Claude Design to make visual decisions once, then do the repeat work in Claude, where the brand context already lives. She builds a design system, designs reusable templates in Claude Design, exports them, and turns each into a Claude skill that produces on-brand assets from a brief. The April video goes further and wires the skills into a campaign-manager agent and a team skills library in Notion. Both videos predate the 2026-09-16 merge that brought Design into ordinary conversations, so the “separate platform” steps are dated.
Key Takeaways
- Design decides, Claude executes. Most marketers keep brand context, instructions and project files in Claude projects, not in Claude Design. So she uses Design for the template and Claude for each new asset.
- Three steps: (1) a brand design system, (2) a reusable template per repeat asset, (3) a skill built from the exported template.
- The export path is standalone HTML. In Share, she exports the whole project as standalone HTML (Canva and Claude Code are also offered), uploads it to Cowork or Claude Code, and asks Claude to “extract the template and package it into a reusable … skill”.
- Skill or one-off? Her rule: if you make the asset again and again (a slide deck, a carousel, a lead magnet), build a skill. If it is a one-off you design and refine (a lead-gen landing page, where every offer differs), make it directly in Claude Design.
- More layouts give the skill more room. Her campaign-deck template has 25 layouts; her carousel template has at least six body-slide variants. “The more the layout, the better, so Claude will have more flexibility.”
- Model choice (her testing). Sonnet for simple templates such as a carousel, “as it’s much more token efficient”. Opus for a landing page and for animation, which she found “consistently better for design project like this”.
- Token cost. In April she exported a carousel to finish edits in Claude Code, because otherwise “Claude design will burn your token so fast”. Her opinion, not a measurement.
- Three kinds of marketing skill (April). Brand skills (your standards), function skills (day-to-day tasks), specialty skills (rules of your domain). Build brand skills first, since nearly every task depends on them.
Step 1 — Build the brand design system
- Minimum inputs: brand logo, brand colours and fonts, and one real marketing asset (a landing page or a slide deck), in one folder.
- In Claude Design: Design System, create, name it, drag in the folder, add notes about the brand. In April she also pasted her brand-voice notes “to play safe”. A GitHub repo can be linked for extraction; she skipped it.
- Time: she says at least 15 minutes (10 to 15 in April), so check the materials before generating.
- Review: the result lists colours, fonts, logos, components and UI mockups. Fix problems by prompting (her example: a tagline overlapping the background). The design-files view lets you edit elements directly, but she found those edits “hard to revert”.
- Start basic. Add things later, such as an icon library attached with “add this to my brand design system”.
- Share it. Publish the system for team use, and optionally set it as the company default.
- Take it into Claude Code (April). She says “this whole design system is actually an exportable Claude skills”. She exported it and dragged the folder into her project’s skills, adding version notes.
Step 2 — Templates in Claude Design
| Template | How she built it | What it contains |
|---|---|---|
| Social carousel | Blank project, Sonnet. “Create a reusable social media carousel template with cover slide, body slide, and end slide”, at least six body-slide variants. | 1:1 and 4:5 ratios; body layouts for stats, quotes, bullets, image upload and image placeholder |
| Campaign deck | Slides template. Ask it to brainstorm and propose layouts before building; she asked for label placeholders and chart and diagram layouts. | 25 layouts |
| Lead magnet | Document template; a folder of SVG icons attached (they scale cleanly and Claude can recolour them). | Cover with image placeholder, checklist, flowchart, scorecard, CTA end page |
| Lead-gen landing page (one-off) | UI mockups template, Opus, the lead-magnet cover and file, and her existing lead-gen page as a layout reference. | Lead form you can test in the preview; she then handed it to Claude Code to connect the form to her email platform |
- Editing tools: the tweaks panel (one-click layout, spacing and style variations you can save as the default), comment mode, and direct edit mode. Aim to be “99% satisfied” before export, and be specific in comments.
Step 3 — Turn templates into skills
- Copy the exported template folder into the project’s
templates/folder, then ask Claude Code to build a skill that references it. - Carousel skill (April): reads the template, proposes a content angle, makes a cover image with Nano Banana, and exports each slide as its own image. (July): the skill proposes an outline and waits for approval before building; a separate image-export skill turns the HTML carousel into individual images.
- Campaign-deck skill (July): given a campaign brief, it built a 12-slide deck in the template with Nano Banana image concepts in the brand style.
- Lead-magnet skill (July): given a cover image and source material, it laid out the lead magnet in her tone of voice, because it runs inside her “team marketing OS” project.
- Watch the template quality. The skill’s output is only as good as the template: “it’s much more important you get this template built right in the first place”. Her April carousels had too much text for performance ads, and two slides overflowed in the agent run.
Motion graphics
- April: a Claude Design prototype called “Animated Video” with the design system selected. She exported it to
templates/and built a skill that makes a 30-second HTML motion video and always proposes a storyboard first. One run took about 15 minutes. She judged it fine for landing-page explainers, not professional video. - July: the Animation template. Her prompt always has five parts: (1) one line on the project and why it needs a scene, (2) the information, kept short, (3) the job the scene does (explain, show a statistic, compare, simplify, or list), (4) ask for three storytelling directions before animating, (5) the animation specification. Use Opus, get the concept about 90% right before generating, then adjust timing in the tweak panel’s motion editor and share as video.
- See Claude Design Animations for other creators’ motion workflows.
The April campaign system
- Project folder: demo brand “Carely” (healthcare SaaS) with a context folder (brand context, ICP, marketing strategy), system folders, a campaigns folder and a
CLAUDE.mdexplaining how to navigate it. Built in Claude Code inside the Claude desktop app. - Skills shown: brand voice (with example files as assets, versioning, and an evaluation run), the design-system skill, a campaign planning brief (Perplexity research plus the design-system skill for an on-brand deck and a brief file), carousel, animated video, and a “skill library manager”. She says “seven marketing skills” in total; not all are shown.
- Campaign manager agent. She says Claude Code Desktop did not support the agent command at the time, so she opened the terminal view inside a session, started Claude Code there and used the agent command to create a campaign-manager agent, then registered it in
CLAUDE.md. Given a thin brief, it asked about goal, budget and audience, then ran research, the deck, a campaign performance tracker in Excel with formulas, carousels, an animated video and a landing page with the video embedded. She says it took almost 25 minutes and that sub-agents kept the main context clean. - Team skills library in Notion. A Notion database with skill name, description, category, version and the zipped skill file. The skill-library-manager skill pushes a test entry first, then all project skills, and on “sync” pushes only skills with a new version.
- Routine to keep it synced. In Routines, a new local routine: check for unpublished skills and push them, auto mode on (Claude approves lower-risk actions), same project folder, weekly at 9:00 AM. See Routines.
Try It
- Put your logo, colour and font specs and one real marketing asset in a folder; build a Claude Design design system from it. Start basic.
- Pick your most repeated asset. Build a template in Claude Design with several layout variants, and get it right before exporting.
- Export as standalone HTML, upload to Claude Code or Cowork, and ask: “extract the template and package it into a reusable [asset] skill that proposes an outline and waits for my approval.”
- Run the skill inside the project that holds your brand context, so tone of voice comes along.
- Keep one-off pieces (a campaign landing page) in Claude Design, then hand off to Claude Code to wire forms.
- Once you have several skills, add a version line to each and keep a shared list for your team.
Implementation
- Tool/Service: Claude Design (paid plans; a separate surface linked from Claude at the time), Claude Code in the Claude desktop app, Cowork, Nano Banana, a Perplexity research tool, Notion, Routines.
- Setup: design-system folder as above;
templates/folder in the project for exported HTML templates; skills and agent in the project’s.claude/folders ^[inferred: standard Claude Code layout, not shown on screen]. - Cost: not stated beyond “you do need a paid plan” for Claude Design.
- Integration notes: both videos are sponsored by HubSpot (free guides “Claude Design in Action” and “AI Toolkit I use every week”; neither was fetched). Her skill course and templates are in her paid community.
Open Questions
- After the merge. Since 2026-09-16 Design works inside ordinary conversations (Claude Cowork). Whether the export-HTML-then-skill step is still the best route, or whether the design skill replaces it, is not covered here.
- “The design system is an exportable skill.” Grace’s claim; the export format was not shown in detail and is not confirmed against Anthropic’s docs.
- Agent command in Claude Code Desktop. Her April statement that Desktop did not support it is unverified and may have changed.
- Model and cost claims (Sonnet more token-efficient, Opus better for design, Design “burns” tokens) are her experience, not measurements.
- Skill count. She introduces “eight Claude skills” and later says “seven marketing skills”; the difference may be the library-manager skill.
Related
- Pre-Established Design with Claude (Ben AI) — the closest method: design system, templates and copy skills before the canvas
- Claude Design (Anthropic Labs) — product page, exports, plans and timeline
- design Skill — the canvas inside Claude Code and Cowork
- Claude Design Animations — motion workflows from other creators
- Cowork + Skills Content System (Grace Leung) — her earlier folder-and-planner content system
- Routines — local and remote scheduled runs
- Lead Magnet Creation with Claude Code — another lead-magnet build
- Building Skills Guide — how to package a workflow as a skill