Ask Claude to Write a Custom Vite Plugin
Vite's plugin API is powerful but the docs are dense. If you need to transform files, inject code at build time, or hook into the dev server, Claude can write a working plugin rather than you spending an hour in the Rollup internals docs.
Write a Vite plugin that reads all .md files in src/content at build time, parses their frontmatter with gray-matter, and injects a virtual module called 'virtual:content' that exports a typed array of all posts with title, slug, date, and body.
Claude will scaffold the plugin with the correct resolveId and load hooks, handle HMR so the virtual module updates when you edit a markdown file in dev mode, and export a TypeScript declaration file for the virtual module so your imports stay typed.
The same approach works for other common plugin patterns:
Write a Vite plugin that automatically imports all SVG files as React components without manual imports
Write a Vite plugin that strips console.log calls in production builds but preserves console.error and console.warn
Tell Claude which Vite version you're on — the api.version property and some hook signatures changed between v4 and v5.
Custom Vite plugins stop feeling exotic once Claude handles the boilerplate.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.