10. Treat Claude Code like a team member. Your team members can make lots of decisions if they understand the big picture goals. Give it a 1-2 page markdown file describing the north star and how what we’re building right now fits into it.
Comments
Log in with your Bluesky account to leave a comment
11. It isn’t great at writing microcopy. The context of coding seems to wash out its writing ability, so all the content is highly descriptive and flat. A text input for name does not need a verbose reason for why you’re inputing it.
12. Use your favorite LLM to clearly describe how your app will work and each page of the app. It doesn’t have to be perfect - Claude Code will improvise if you start a list and say “plus whatever else makes sense.” Put your description of how the app will work into a markdown file.
13. Find the right level of abstraction. I gave it a markdown describing a project step-by-step and asked it to “start with the header and footer” and it just went ahead and built out the 3 page app. Amazing!
15. Don't overdo it with context and rules: you need to give Claude Code big picture, what part of the big picture we’re working on now, and what we’re specifically doing right now. If overload Claude with a million rules and context, you make it dumber.
16. It’s early days, so nearly every day it gets an update that makes it meaningfully better. No longer do I have to type /compact to help it manage its context window.
Comments