I just watched a walkthrough that completely changed how I think about Claude for marketing work. The whole “prompt and pray” approach? Done. Once you start treating Claude as a system instead of a chat window, the leverage is on another level.
The walkthrough comes from Grace Leung, a digital growth consultant who put together a campaign workflow built entirely on Claude skills and the new Claude design tool. She layers eight custom skills on top of a healthcare SaaS brand called Carely and runs a full campaign from a single brief. I was honestly impressed by how clean the orchestration looked.
Here’s the framework she uses to organize Claude skills for marketing work.
Three skill types to map your week
The creator groups skills into three buckets, and this part alone is worth the watch:
- Brand skills: define your brand standard (voice, design system). Foundation for everything else.
- Function skills: cover the marketing tasks you do day to day (campaign planning, carousels, video).
- Specialty skills: handle rules specific to your domain or industry.
Her suggestion is to look at your marketing week, list the repeating tasks, sort them into these three buckets, and build brand skills first. Almost every other skill stacks on top of those.
The project setup that makes Claude actually useful
Grace sets up a clean project folder with a context folder (brand context, ICP, marketing strategy), a campaigns folder for outputs, and a CLAUDE.md file that tells Claude how to navigate everything. She runs all of this through the new Claude code desktop, which lets you filter by project and switch instantly.
From there she builds the skills one by one.
The eight skills she built (and what each one does)
- Brand voice skill: pulls from the brand voice guide, includes examples as assets, and runs an evaluation step to keep quality high. She also adds versioning, which becomes critical later.
- Brand design system skill: built using Claude design tool, which extracts colors, fonts, components, logos, and UI mockups from existing assets. The expert says the biggest value is exporting the design system as a portable Claude skill you can drop into any project.
- Campaign planning skill: uses Perplexity for research, then calls the design system skill to build a branded slide deck and campaign brief. The output included KPI targets, persona mapping, funnel mapping, budget allocation, and a roadmap.
- Carousel design skill: references a carousel template built in Claude design, generates cover images with nano banana, and exports each slide as an individual image.
- Animated video skill: creates 30-second motion videos in HTML using a motion engine built in Claude design. Always proposes a storyboard first.
- Landing page skill: pulls everything together with the embedded video and CTA.
- Skill library manager: pushes skills to a Notion-based library so the team can browse and download them.
- Campaign manager agent: orchestrates all the skills end to end, asking clarifying questions when the brief is vague.
Pro tips that save real time
A few things the creator highlighted that I’d steal immediately:
- Build your asset templates first in Claude design, then export and edit in Claude code. She warns that editing inside Claude design burns tokens fast and changes are hard to revert.
- Always include versioning when you build a skill. It’s how the Notion library tracks updates and stays current.
- Use the agent command (only available in Claude code terminal, not desktop) to spin up an orchestrator. It runs sub-agents so the main context stays clean.
- Click the task view at any time to see what Claude is working on across agents.
The campaign manager run that closed the loop
The most impressive part: she gave the campaign manager agent almost no detail about a new product launch. The agent asked her about goal, budget, and audience, then ran research, built the deck, generated carousels, produced an animated video, and assembled a landing page. About 25 minutes of compute, fully on brand, with a performance tracker that already had Excel formulas baked in for actual versus forecast tracking.
Where it gets real: the team library
This is where the post’s author takes it from personal hack to team system. She pushes every skill to a Notion library with name, description, category, version, and the zipped skill file. Then she sets up a Claude routine to scan for new or updated skills every Monday at 9 AM and auto-publish them. No manual uploads, no version drift.
A few honest limits worth knowing
Not everything was perfect. A couple of carousel slides had text overflow. The animated video was good for landing page explainers but not professional broadcast quality. And Claude design generation can take 10 to 15 minutes per run, so you really want your inputs ready before you hit go.
If you run marketing campaigns and you’ve been treating Claude like a fancy autocomplete, this video is the reset. Watch the full walkthrough for the actual prompts and folder structure, it’s the kind of thing you’ll want to copy step by step.