Generate ESLint and Prettier Configs from Your Preferences
Setting up ESLint and Prettier from scratch means reading docs, cross-referencing plugin versions, and debugging config conflicts for an hour. Instead, just tell Claude what you want.
Generate an ESLint flat config (eslint.config.js) and a Prettier
config (.prettierrc) for a TypeScript React project. Rules I care
about: 2-space indentation, single quotes, no semicolons, no unused
variables, and enforce React hooks rules. We use Tailwind CSS.
Claude will produce working, compatible configs — including the right plugin versions and import syntax for ESLint's flat config format — and explain each rule it adds.
// eslint.config.js — generated and ready to use
import js from '@eslint/js'
import tsPlugin from '@typescript-eslint/eslint-plugin'
import tsParser from '@typescript-eslint/parser'
import reactHooks from 'eslint-plugin-react-hooks'
export default [
js.configs.recommended,
{
files: ['**/*.{ts,tsx}'],
languageOptions: { parser: tsParser },
plugins: { '@typescript-eslint': tsPlugin, 'react-hooks': reactHooks },
rules: {
'no-unused-vars': 'off',
'@typescript-eslint/no-unused-vars': 'error',
'react-hooks/rules-of-hooks': 'error',
},
},
]
You can also paste your existing config and ask Claude to migrate it from .eslintrc to the new flat config format, or to add rules for a new plugin you've just installed.
Stop wrestling with config syntax — describe what you want and Claude delivers a working setup in seconds.
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.