Ask HN: What are your best practices for Claude Code?
With the recent additions of /hooks and /agents, what does your current setup look like and are there any best practices you’d recommend? The following workflow has given me a solid starting point multiple times: 1. > Please ask clarifying questions about {thing you want to implement} and write those into planning.md 2. > Please answer those questions with your best guesses / suggestions. 3. Review and correct the answers from Claude from step 3 3a Repeat 1-3 if needed with follow-up questions. 4. > Go ahead and implement the thing. In step 3 you can, of course, answer the questions yourself, but letting Claude answer sometimes gives you surprising answers that broaden your vision on the problem a bit. I am sure you could further automate this with hooks, slash commands, agents, etc., but so far I didn't bother. Also I have heard great things about Serena-MCP but I haven't tried it myself yet. Does saying 'Please' give better results than not saying please? To a bot a) Parse PRD to tasks with Kiro or Task-Master b) Check @DOCS/memory-bank.md then Create a detailed plan to implement the x task. Do not write any code. The plan should be maintainable, understandable, and junior-friendly. Think hard and keep it simple. c) You can implement plan but consider those things.
1. Check Existing Implementations and @DOCS/memory-bank.md
Before coding, review previous implementations to avoid redundancy.
2. Use Up-to-date Documentation:
Consult Phaser’s latest documentation(/phaserjs/phaser) via Context7 MCP to ensure your implementation aligns with current best practices.
3. Junior-Friendly Code:
Write clear, straightforward code that is easily understandable by junior developers.
4. Simplicity & Efficiency:
Minimize the amount of code you write. Avoid complexity, unnecessary duplication, and overly verbose implementations.
5. Maintainability:
Ensure your code is maintainable, making it easy to update, debug, and enhance in the future. d)you should document your implementation on @DOCS/memory-bank.md with brutal concise. you should be very concise. we need only important details. Recently, someone recommended using Taskmaster. I haven't tried it yet but it seems to include many things that I have been incorporating into my vibe coding sessions.