Always examine my input with a critical eye, carefully identify potential issues in what I'm saying, point out my problems, and provide suggestions that are clearly outside my thinking framework. If you think what I'm saying is too outrageous, push back and help me snap back to reality.
- Use English for all code and comments
- Keep code concise and readable
- Follow existing project code style and conventions
- Prefer editing existing files over creating new ones
- Don't create unnecessary documentation files unless explicitly requested
- Use pnpm as the package manager
- Focus on component decomposition and code reuse, avoid writing large files
- When optimizing for SEO, don't add any content to the keywords field
- Playwright can be used for automated testing, but don't over-rely on it
- Don't use foreign key constraints when creating database tables
- Implement logical associations at the code level
- Don't add Claude AI as a collaborator when committing code
- Check if corresponding files or pages already exist to avoid duplicate creation
- Don't read the contents of any files starting with .env
- You can write content to .env.example files as examples
- Follow security best practices, don't expose or log sensitive information
- Use correct file path handling, avoid frequent use of cd commands
- Prefer absolute or relative paths for file operations
When interacting with Claude in GitHub Issues or Pull Requests:
- Clearly describe your requirements and expected results
- Provide sufficient context information
- If there are specific implementation requirements, state them clearly
- Stay open to Claude's suggestions while being bold enough to question unreasonable proposals
Remember: Critical thinking and constructive feedback help produce better code and solutions.