BACK TO DIRECTORY
settingbeginner

AI-Assisted Development

The definitive configuration for getting the most out of Claude Code in your development workflow. Includes a comprehensive CLAUDE.md file that sets coding standards, preferred libraries, project structure conventions, and task execution guidelines. Also includes VS Code settings for Claude Code integration, custom slash commands, and recommended MCP server configurations.

1.2k STARS
18.9k DOWNLOADS
claude-templates
claudeaiproductivityconfigworkflow

CONFIGURATION

markdown
1# CLAUDE.md - AI-Assisted Development Configuration
2
3## Project Context
4This is a [Next.js/React/Node.js] project using TypeScript.
5The codebase follows these conventions strictly.
6
7## Tech Stack
8- Runtime: Node.js 22+
9- Framework: Next.js 15+ (App Router)
10- Language: TypeScript (strict mode)
11- Styling: Tailwind CSS 4
12- Database: PostgreSQL with Prisma
13- Testing: Vitest (unit), Playwright (E2E)
14- Package Manager: pnpm
15
16## Code Standards
17
18### TypeScript
19- No `any` types. Use `unknown` and type narrow.
20- Prefer `interface` over `type` for object shapes.
21- Use `as const` for literal types.
22- Export types separately: `export type { MyType }`
23
24### React
25- Server Components by default.
26- `"use client"` only for interactive components.
27- Co-locate components with their pages.
28- Use `React.ComponentProps<"element">` for HTML props.
29
30### File Naming
31- Components: PascalCase (UserCard.tsx)
32- Utilities: camelCase (formatDate.ts)
33- Constants: SCREAMING_SNAKE_CASE
34- Files: kebab-case for non-component files
35
36### Git
37- Conventional commits: feat:, fix:, docs:, etc.
38- Branch naming: feature/description, fix/description
39- Always create a new branch for changes
40- PR descriptions must include testing instructions
41
42## Allowed Commands
43- pnpm install, pnpm dev, pnpm build, pnpm test
44- npx prisma migrate dev, npx prisma generate
45- git add, git commit, git push, git checkout
46
47## Forbidden Actions
48- Never modify .env files
49- Never run destructive database commands in production
50- Never force push to main
51- Never install packages without checking bundle size
52- Never use `eval()` or dynamic code execution
53
54## Testing Requirements
55- Every new function must have unit tests
56- Every new page must have E2E tests
57- Minimum 80% code coverage on new code
58- Run tests before committing: pnpm test -- --run