Claude Code Templates for Your Next Task
Choose a focused setup for reviewing code, setting project instructions, editing content, or building a frontend. Each selection explains when to use it and links to the full guide or resource.
Review code changes
Get a focused review of a supplied diff or a named set of changed files.
A narrow review role makes it easier to ask for concrete defects, supporting code evidence, and practical next steps.
- Bring
- The diff, relevant files, and the behavior the change is meant to implement.
- What to expect
- A findings report with file locations, evidence, and suggested corrections.
The example uses reading and search tools. You supply the diff; it does not run tests or apply fixes.
For separate reviews of repository standards and requirements, explore mattpocock's code-review Skill. It uses a separate review process with its own setup and tool requirements.
Explore the code-review SkillSet up project instructions
Give Claude Code the repository facts you would otherwise repeat in every task.
Clear paths, real commands, and project conventions help the agent work within the repository's existing structure.
- Bring
- The current package scripts, directory layout, environment requirements, and conventions you want to preserve.
- What to expect
- A project instruction file adapted to your repository.
Choose the concise generic template or the annotated Next.js / TypeScript / pnpm example. Replace example-specific facts with your own, then check that Claude Code loads the file.
Improve AI-written content
Revise an existing draft that sounds repetitive, inflated, or formulaic.
Humanizer provides an editing process for improving wording and rhythm while preserving the intended meaning. A writing sample can help guide the voice.
- Bring
- The draft, intended reader, desired tone, and any facts or wording that must stay unchanged.
- What to expect
- Revised prose to review for meaning, accuracy, and voice.
Use it for product descriptions, launch posts, and documentation prose. Check factual claims yourself; it is an editing resource, not a fact-checking service.
Build a frontend
Shape the interface, then review the React or Next.js implementation.
Use one Skill for visual direction and another for implementation patterns, with both working from the same brief and repository conventions.
- Bring
- Your product brief, real page content, brand constraints, existing components, and relevant code.
- What to expect
- A UI implementation and a focused technical review.
- 1.SkillAnthropic
Design and build with Frontend Design
Use frontend-design to guide typography, color, layout, and interface copy around the product and audience.
- 2.SkillVercel Labs
Review with Vercel React Best Practices
Use vercel-react-best-practices to examine React and Next.js patterns involving data fetching, bundle size, rendering, and re-renders.
Check the result in the browser, run the project's relevant checks, and measure performance when claiming an improvement. This is a suggested sequence of two Skills; each has its own setup.
Understand the resource types
“Template” is the collection label. Use each item’s type to understand how it fits your setup.
- Skill
- Reusable task instructions and supporting resources.
- Subagent
- A delegated role with its own context and tool configuration.
- Project instructions
- Repository facts, commands, and conventions.
- Workflow
- A suggested sequence combining resources for a larger task.
Claude Code documents Skills, Subagents, and project instructions separately. The workflow above is our suggested way to combine selected resources.
Use your chosen setup
- 1.
Choose the task that matches your current work.
- 2.
Open the guide or resource page for its files, requirements, and setup.
- 3.
Try one small task and check the result before expanding the setup.
Full installation steps, configuration files, and examples stay in the linked guides and resource pages.