Post #792

Claude Code Shu kunlarda Claude Code juda ommalashyapti. Ayniqsa, X/Twitter’da juda qiziq misollarni ko’rish mumkin: kimdir telefonda SSH orqali serverga kirib kod yozyapti, kimdir aqlli soati bilan gapirib kod yozyapti va hokazo. Hozir men uchta agent bilan ishlayapman: Claude Code, Codex (OpenAI) va Cursor. Lekin, X’dagi shov-shuvlarga qaraganda, Claude Code - eng yaxshi mahsulot (model sifatida unga savol yo’q). Agar Claude Code asoschisi - Boris Cherny’ning videosini ko’rmagan bo’lsangiz, zudlik bilan yarim soat vaqt sarflashni maslahat beraman. Ko’p narsalar umumiy qilib juda yaxshi tushuntirilgan. Mastering Claude Code in 30 minutes Video bergan yaxshi tajribalardan biri - butun tizim uchun ko’rsatmalar berib qo’yish. macOS’da ~/.claude/CLAUDE.md fayli tizimdagi hamma loyihalar uchun ishlaydi. Bu faylga umumiy qoidalar, shaxsiy stil, loyihadan agnostik bo’lgan ko’rsatmalarni yozib qo’yish mumkin. Quyidagi ko’rsatmalar Chris Dzombak blogidan olindi. Menimcha, juda yaxshi prompt. Shuni yaxshilab boraman. Sizga ham asqotadi, degan umiddaman. # Development Guidelines ## Philosophy ### Core Beliefs - **Incremental progress over big bangs** - Small changes that compile and pass tests - **Learning from existing code** - Study and plan before implementing - **Pragmatic over dogmatic** - Adapt to project reality - **Clear intent over clever code** - Be boring and obvious ### Simplicity - **Single responsibility** per function/class - **Avoid premature abstractions** - **No clever tricks** - choose the boring solution - If you need to explain it, it's too complex ## Technical Standards ### Architecture Principles - **Composition over inheritance** - Use dependency injection - **Interfaces over singletons** - Enable testing and flexibility - **Explicit over implicit** - Clear data flow and dependencies - **Test-driven when possible** - Never disable tests, fix them ### Error Handling - **Fail fast** with descriptive messages - **Include context** for debugging - **Handle errors** at appropriate level - **Never** silently swallow exceptions ## Project Integration ### Learn the Codebase - Find similar features/components - Identify common patterns and conventions - Use same libraries/utilities when possible - Follow existing test patterns ### Tooling - Use project's existing build system - Use project's existing test framework - Use project's formatter/linter settings - Don't introduce new tools without strong justification ### Code Style - Follow existing conventions in the project - Refer to linter configurations and .editorconfig, if present - Text files should always end with an empty line ## MCP Tool Use - Use Context7 to validate current documentation about software libraries - Use searxng if your primary Web Search or Fetch tools fail - Use Tavily ONLY when searxng doesn't give you enough information ## Important Reminders **NEVER**: - Use `--no-verify` to bypass commit hooks - Disable tests instead of fixing them - Commit code that doesn't compile - Make assumptions - verify with existing code **ALWAYS**: - Commit working code incrementally - Update plan documentation as you go - Learn from existing implementations - Stop after 3 failed attempts and reassess Loyihaning o’zi uchun Claude’ga bunaqa prompt berish yetarli: Scan the project and create a CLAUDE.md with build/test commands and code style guidelines based on what you find. Happy vibe coding! 🧑‍💻 @farhodjon#ai#vibecoding