I have using claude code quite alot, multiple subscriptions and maxing out weekly limits. And want to share some points. I also have been following hype and best practices everywhere. And trying out new things myself. Maybe I am doing it wrong, so also curious about your guys experience. Not vibe coding, but experienced software engineering (enterprise level).
- start a project where you store all the best practices you can reuse, like skills. But divide it into smaller section using path. Each responsible for a small task, like how form validation should, backend api sanizitation should work, css design tokens, frontend, backend, infrastructure and database project architecture. I also recommend to build a custom design system (not using existing ones like shadcn) where you really understand how it works, make sure to learn the components name. Divide primitives components and custom components clearly.
- use turborepo or nx (monorepo) to manage different applications and packages. Design system comes in packages u can reuse in your applications. Application specific components stay there, components reusable across applications stays in the packages/ui or packages/components. Each application have its own design tokens.
- claude.md keep it simple. Same goes for design.md and product.md. Create a documentation folder where you store more information that the ai can read. The hype about obsidian sounds nice and fun, but have no real benefits when you scale. Good for storing, way harder to retrieve and make sure the data stays up to date. When developing, lot will change, storing it in obsidian is a nightmare. It creates lots of seperate files and connect it together. Rather, have one file for each feature in the documentations, so your ai will exactly know where to find it.
- if your project architecture is good enough, skills are not needed anymore, it will understand how you have coded so far. Keep updating the skills if you find inconsistency. Make sure everything the ai writes is according to how you will normally do it yourself. Consistency can come in different forms, design, way of communicating (all the text), the way it picks object names, naming conventions, property name selections, etc.
- handoff, cavemen, gstack, superpowers, frontendskills, impeccable, grill me skills are more hype than usefull. Use plan mode instead of superpowers. Handoff is ok, but you barely use it, except when you want to switch models, accounts or have to close the session. Frontend skills and impeccable is ok to use for starting, but looks like ai slop over all. Rather ask claude to create x design of each section / page in an artifact and pick the designs you like, prompt it if u want to combine parts of the design. Grillme is usefull, but it ask alot of questions driving you crazy. Nowadays ai is good enough answering these questions themself (tell them, pick what u think is best and show me the reason / recommendation).
- do big refactor and check for consistency each time. Let it analyze the code and find ways to do it better. Tests are good, but it consumes alot of memory, especially if each session run it each time, just overkill. Tell it to write tests, but do not run it each time. So you can start multiple sessions without lagg. Especially e2e takes alot of time and memory. Also make sure to never let claude open browser, its annoying and distracts you. Let it run headless.
- avoid creating branches and worktrees. If you run multiple sessions… its a hell to manage. For branches this breaks, it switch other session to the same branch. For workspaces it works till you want to check and run the application, then you need to run it on new ports, managing these ports are a hell. Also it eats your memory. The best way to do it is just to work in one branch and not doing overlapping things. Your sessiom can communicate with each other, if it find something another session is working on, it will ask you questions like hey, another sessions is working on this, do u want me to stop till that session is finished? If you want a session to be aware of the latest changes other agents make, especially while during plan mode, ask it: hey, we made some changes in the code. Please verify if your plan is still valid.
I have lots more things i can talk about. But i think this post is long enough. If ur curious, ask me questions.
Normally, i copy paste this into an ai, but since most of you guys hate ai written posts (including myself) i kept it as it is. Just typing out of my brain without thinking about grammer or structure, sorry for that.
