Workflow recipes
6 step-by-step recipes that chain Claude skills and MCP servers into actual jobs — decks, weekly reviews, bug fixes, and more. Each step links to the tool, so you can run the chain end-to-end.
For designers
2 recipes
Brand-consistent decks in 10 minutes
Go from blank slide to a polished, on-brand deck without leaving Claude. Five tools, one chain.
- 1PowerPoint Skill
Generate the deck skeleton: title, sections, speaker notes, real PPTX file output.
- 2Brand Guidelines
Apply your brand colors, typography, and accent rules to every slide.
- 3Theme Factory
Pick a curated theme that matches the audience — exec, product, sales.
- 4Canvas Design
Create a hero slide or section divider as a museum-quality visual artifact.
- 5Slack GIF Creator
Make a Slack-ready animated GIF to share the deck with your team.
From Figma to launch-ready asset
Take a single Figma frame and ship the full asset kit a launch needs — copy, code, social, the lot.
- 1Figma Dev Mode MCP
Pull the selected frame's design tokens, structure, and assets directly from Figma.
- 2Frontend Design
Translate the design into clean, accessible component code that matches the spec.
- 3Canvas Design
Polish a hero artwork for the launch — magazine-quality, brand-aligned.
- 4Web Asset Generator
Generate favicons, app icons, and Open Graph images in every size you need.
- 5Slack GIF Creator
Tease the launch with an animated GIF teammates will actually click.
For writers & pms
2 recipes
Weekly review without the slog
Turn a week of scattered work into a clean 3P (Progress / Plans / Problems) update your team will actually read.
- 1Linear MCP Server
Pull every issue your team shipped, started, or got stuck on this week.
- 2GitHub MCP Server
Grab merged PRs and changelogs to confirm what actually landed.
- 3Doc Co-Authoring
Walk through Claude's three-stage co-authoring flow to draft the review.
- 4Internal Comms
Format as a polished 3P update with the right tone for your org.
- 5Slack MCP Server
Post the final update to the team channel.
Research, draft, and polish a doc
Go from a hazy topic to a doc your team will actually finish reading. Research-grounded, structured, ready to publish.
- 1Exa Search
Run semantic searches across the web to gather the strongest sources on the topic.
- 2Context7
Pull up-to-date library and product docs whenever the doc needs technical citations.
- 3Doc Co-Authoring
Co-author with Claude's three-stage flow: gather, refine, and reader-test.
- 4Internal Comms
Reformat the same content as an FAQ, status update, or exec summary for different audiences.
- 5Notion MCP Server
Publish the final doc into the right Notion space and link it everywhere.
For developers
2 recipes
Bug report to merged PR in one chain
Turn a Linear bug ticket into a tested fix on main without hunting through dashboards.
- 1Linear MCP Server
Pull the bug report's full context, repro steps, and any prior debugging comments.
- 2GitHub MCP Server
Locate the offending file, recent commits, and any related PRs or issues.
- 3Playwright MCP Server
Add a regression test that fails before the fix and passes after — proof the bug stays dead.
- 4Sentry MCP Server
After deploy, confirm the error rate dropped and close the loop on the original ticket.
Ship a feature end-to-end with Claude Code
From an empty repo branch to a deployed preview link with passing tests and a clean PR description.
- 1Context7
Pull current, version-pinned library docs so generated code matches what's actually deployed.
- 2Supabase MCP Server
Apply schema migrations and seed data without leaving the conversation.
- 3Vercel Deploy
Spin up a preview deployment your team can poke at before review.
- 4GitHub MCP Server
Open the PR with an auto-generated description that summarizes what changed and why.