Chapter 7 of 14 · Use · 4 min read
Everyday workflows with skills for developers, designers and marketers
Skills earn their keep in ordinary, repeated work: the bug you need to track down, the pull request you need to review, the landing page that needs a second pair of eyes, the content brief due on Friday. This chapter shows realistic workflows for three kinds of work, what you’d actually say to the agent, and how skills change the result. You don’t need to adopt them all. Pick one task you do every week and start there.
A pattern that works for everyone
- Pick a task you repeat often and know how to judge.
- Install one skill that covers it, after reading it.
- Ask for the task in plain words and watch the agent follow the skill.
- Compare the result with what you’d have done. Keep the skill if it helps; edit it if it nearly helps.
- After a few runs, write down what you keep correcting. That list is the start of your own skill.
For developers
Coding agents are already capable, but left alone they tend to rush: patching symptoms, skipping tests, declaring victory early. Many of the most popular developer skills exist to slow them down in the right places.
| Task | What you ask | What the skill adds |
|---|---|---|
| Fixing a bug | “The export button fails for large files. Find out why.” | Reproduce first, form hypotheses, find the root cause, then fix |
| New feature | “Add rate limiting to the public API.” | Write a plan first, then implement in small, tested steps |
| Tests | “Add a discount code field to checkout.” | Write a failing test, make it pass, then refactor |
| Code review | “Review this branch before I open a pull request.” | A consistent checklist: correctness, security, tests, readability |
| Finishing up | “Is this ready to merge?” | Run the checks and show evidence rather than asserting success |
Systematic DebuggingAgent skillRoot-cause debugging in four phases, before any fix.Agent skill · MITTest-Driven DevelopmentAgent skillRed, green, refactor, enforced as a habit.Agent skill · MITWriting PlansAgent skillTurns a feature request into a step-by-step plan first.Agent skill · MITA developer workflow, end to end
Say you’ve been asked to add CSV export to a reports page. Ask the agent to plan the feature; a planning skill has it write a short plan with steps and tests before touching code. Review the plan and adjust it. Then ask it to implement step one; a test-driven skill has it write the failing test first. When something breaks unexpectedly, a debugging skill stops it guessing. Before you open the pull request, a review skill and a verification skill run the checks. Each skill is small, but together they turn a capable but impatient agent into a methodical one.
Put the skills your whole team relies on in the repository’s .claude/skills/ folder. New teammates get the same workflow from their first day.
For designers
Agents that can write front-end code tend to produce interfaces that are functional but generic. Design skills give them taste and a checklist: spacing systems, type scales, contrast, states for empty, loading and error, and a habit of reviewing the result critically.
- Building a UI from a brief: “Build a pricing page for three plans, matching our existing styles.” A front-end design skill pushes for a deliberate visual direction instead of default component-library looks.
- Critiquing a screen: “Review this page for hierarchy, spacing and accessibility.” A review skill makes the critique specific and actionable rather than vague praise.
- Accessibility pass: “Check this form for accessibility problems and fix them.” A skill can walk through labels, focus order, contrast and keyboard use every time.
- Design-to-code handoff: pair a design tool’s MCP server, which gives access to the file, with a skill describing your component conventions.
Impeccable Frontend Design SkillAgent skillDesign guidance and commands that sharpen front-end output.Agent skill · Apache-2.0
Frontend DesignAgent skillAnthropic’s skill for distinctive, production-grade interfaces.Agent skill · Apache-2.0AAccessibility review workflowPromptA step-by-step accessibility review you can reuse.Free promptFor marketers
Marketing work is full of repeatable formats with house rules: briefs, landing pages, email sequences, social posts, SEO audits. Skills are an ideal way to capture those rules so every draft starts on-brand.
| Task | What you ask | What the skill adds |
|---|---|---|
| Landing page copy | “Rewrite this page for trial sign-ups.” | A clear structure: promise, proof, objections, call to action |
| Brand voice | “Draft three LinkedIn posts about the launch.” | Your tone, vocabulary and banned phrases, applied every time |
| SEO audit | “Audit this page for search.” | A fixed checklist: titles, headings, internal links, intent match |
| Email sequence | “Write a five-email onboarding sequence.” | Timing, one goal per email and consistent subject-line rules |
Copywriting AssistantAgent skillConversion copywriting guidance for pages and campaigns.Agent skill · MITSEO AuditAgent skillA structured SEO audit an agent can run on any page.Agent skill · MIT
Brand VoiceAgent skillCapture a brand voice and apply it to drafts.Agent skill · MITThe biggest win for marketers is often a brand-voice skill you write yourself: a page of real examples, words you use and avoid, and how formal to be for each channel. It replaces the paragraph of context you used to paste into every chat. For a broader view of tools, see Build a marketing stack with AI.
Check facts, figures and claims in anything an agent drafts for publication. Skills improve structure and consistency, but they don’t make the model infallible about your product, prices or legal claims.
Combining skills
Skills compose naturally because each loads only when relevant. A single session might plan, implement, debug and review, with a different skill for each phase. You don’t have to orchestrate this. Ask for each step and the right skill loads. If two skills conflict, such as two code-review skills with different rules, uninstall one; overlapping descriptions make the agent’s choice unpredictable.
Key takeaways
- Start with one weekly task and one skill, and judge the result honestly.
- Developer skills mostly add discipline: plan, test, debug methodically, verify.
- Designer skills add taste and checklists; marketer skills add structure and voice.
- The corrections you keep making are the raw material for your own skill.
Put it into practice
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Written by the AI Tool Garage editors. Tool details link to their catalogue pages, which are refreshed weekly; spotted something out of date? Tell us.