CLAUDE[.]md is one of the most important files in any Claude Code project. Think of it as project memory + execution guidelines. It tells Claude what your project is, how the codebase is structured, what design rules to follow, and what patterns to avoid. Here are 8 practical tips for writing a better CLAUDE[.]md: 1. Know the difference between project and global CLAUDE[.]md: A project-based CLAUDE[.]md lives in your project root and is specific to that product. A global CLAUDE[.]md lives in your Claude env and defines reusable preferences across all projects. Project CLAUDE[.]md: = project contextGlobal CLAUDE[.]md:= personal working style 2. Structure it properly Claude performs better when information is grouped semantically. Thats why don’t write random instructions. Use clear sections like: ✅ Project Overview ✅ Tech Stack ✅ Folder Structure ✅ UI/UX Principles ✅ Component Rules ✅ Accessibility Requirements ✅ Testing Strategy ✅ Content Guidelines ✅ Deployment Notes 3. Use [/]init to create the first draft You don’t need to start from a blank page. Run [/]initso Claude Code will scan your project and generate a first version of CLAUDE[.]md It won’t be perfect, but it gives you a solid starting point. 4. Keep it short CLAUDE[.]md is loaded into every Claude Code session, so it consumes context. My rule of thumb: Keep it under 200 lines. Ideally, under 100. For detailed documentation, use routing rules 5. Be specific Bad instruction: “Write clean code.” Better instruction: “Use descriptive prop names, no abbreviations” and “Prefer composition over inheritance.” The more precise your instructions are, the more deterministic Claude’s output becomes. 6. Treat CLAUDE[.]md: as a living document Don’t create it once and forget it. Update it when: ✅ Claude repeats the same mistake ✅ You introduce a new pattern ✅ Your product requirements change ✅ Your design system evolves ✅ Your team agrees on new rules The best CLAUDE[.]md: files are built from real usage, not theory.

DESIGN[.]mdis quickly becoming one of the most useful files for AI-assisted UI design because it help AI understand your design system well enough to create UI that actually feels like your product. A good DESIGN[.]md usually includes your design tokens, brand style, color rules, typography, spacing, and component guidance. 3 best practices for creating a strong DESIGN[.]md: 1. Treat tokens as decisions: A token is not just a variable. It defines the role something plays in the interface. 2. Add reasoning. Don’t just say what a style is. Explain why it exists, when to use it, and when not to use it. This helps AI make better design decisions. 3. Build components on top of tokens. Components should reference your tokens and design rules. Complete guide to DESIGN[.]md: https://medium.com/ux-planet/design-md-best-practices-c00325e8b23a?sk=6e97ad8d6c6fc014f45bb7db864a554b

Fable 5 is Anthropic’s new Mythos-class Claude model, available to the general audience; the company positions it as a tier above Opus in capability. Here are 3 popular questions about this model Q: Is Fable 5 really better than Opus? A: Yes. It performs better than Opus, especially for complex tasks like prototyping and coding (link to performance test below) Q: Is Fable 5 not very token-efficient? A: No. The model consumes more tokens than Opus, but it also produces much better results (in my experience, you spend 3x more tokens but get 5x better output generated by AI) Q: Is Fable 5 available to everyone? A: Yes, it’s available at no extra cost for Pro, Max, Team, and seat-based Enterprise plans until Jun 22 but starting from Jun 23, it will require usage credits. 👉 Claude Opus 4.8 vs Fable 5 for product design task: https://medium.com/ux-planet/claude-opus-4-8-vs-fable-5-2b0a442ccdcb?sk=3ba4768a81ebc5dd094a9e21734002e9

Claude skill is a reusable set of instructions that teaches Claude how to perform a specific task. In product design, skills can teach Claude to follow your exact brand style guidelines or execute a complex workflow that is relevant to your specific organization. Below is essential collection of 5 guides that will help you improve your Skill creation abilities: ✅ Introduction to Claude Skills: https://uxplanet.org/claude-skills-for-product-designers-a453a7a8faa7?sk=f7f7c081ad565150731d4ddaf57a64ec ✅ Popular mistakes to avoid when creating Claude Skills: https://uxplanet.org/7-common-mistakes-to-avoid-when-creating-claude-skills-7bd99dc85e2f?sk=088486170d5937dd4cc038cd9edd73be ✅ How to use Claude's Skill Creator Meta-skill: https://uxplanet.org/claude-skills-2-0-for-product-designers-a86f4518b3ba?sk=c9bef60bcd4d69ea915f1e9194613aff ✅ Practical tips for using skills listed in the cheatsheet: https://uxplanet.org/must-have-ux-ui-design-skills-for-claude-code-364e93e3a614?sk=f6b3b6c4abc437cd4e0301d275fd9476 ✅ Troubleshooting Claude Skill (very handy if your skill is not working as expected): https://uxplanet.org/troubleshooting-claude-code-skills-bf29c8383abd?sk=107a18aae3b87a1804abeeaa57d8376a

CLAUDE[.]md is the most critical file for Claude Code as it provides project-specific context to Claude Code. It serves as an onboarding guide for AI to your project requirements & codebase. Whenever Claude’s AI model writes new or modifies existing code in your project, the first thing it will do is check the Claude[.]md file. Here is a collection of practical resources that will help you craft super valuable CLAUDE[.]md file for your project: ✅ Comprehensive Guide to CLAUDE[.]md Introduction guide to CLAUDE[.]md, the role it serves and essential tips for creating a first version of the file for your project. https://medium.com/ux-planet/comprehensive-guide-to-the-claude-md-8e60f860d9f9?sk=483f0911c3b20bc2c76d6af4a59eebe3 ✅ CLAUDE[.]md best practices A set of best practices for creating CLAUDE[.]md for product design projects - specific sections to include along with examples of the sections https://uxplanet.org/claude-md-best-practices-1ef4f861ce7c?sk=527be6c932389dafdb9f7550d4458ac3 ✅ CLAUDE[.]md vs Claude Skills Difference between CLAUDE[.]md and skills; practical recommendations on when to use each. https://medium.com/ux-planet/claude-code-claude-md-vs-skills-35685676b367?sk=770b7690ec0507d62f10349c93f8e6df ✅ CLAUDE[.]md tips and tricks for product designers Practical recommendations for CLAUDE[.]md optimisation https://medium.com/ux-planet/claude-md-tips-tricks-for-product-designers-4cc47f2084c1?sk=d4e914854ce51528aeccc22eb6de88a5 ✅ 7 Advanced CLAUDE[.]md Tips for Claude Code CLAUDE[.]md optimization for better performance (including writing anti-patterns and success criteria)