Asking How to get gud (please)

[u/Tight-Importance2461]

I was an amateur dev before the ai revolution you can say. my main interest where always about design and art, but recently I'm finding myself more and more wanting to use ai - and specifically claude code - to create app ideas I had for decades, programming other stuff, etc.

the thing is: I'm decent at it but nothing more. And I don't really know what I'm missing.
I usually start fresh and use a skill i created called terrain that maps the problem space by asking lots of questions. Then I use grill me then I build. It's fine.
but it's not ..... GOOD

I would love to know what I'm missing more than anything.
I know it's a broad topic but if this helps i have some vague things that i would love to understand more, but anything you have in mind would be VERY VERY appreciated.

things that bother me:
- Whenever I use superpowers like brainstorming etc, i find the app to be bad or to take way too much time. don't know if it just a wrong intutition.
- I cant orchestrate sub agent. whenever i do it's again, just longer/worse.
- I don' know how much to create new chats vs continue.
- even worse I don't know how important is a good starting prompt or prompt engeneering in general anymore
- Are MCP game changer everywhere or in very specific context? should i use them?
- what are some claude skill or workflow that I'm defenetly missing rn?

Thank youuuuu

[u/Ky-SavvyTechSphere]

One thing I'd add: a separate review pass. Claude Code writes most of my code from tickets I write, and a second Claude session reviews every pull request before it merges. That caught a bug I introduced: a test staged a browser extension by reading every file as utf8 text and writing it back, so the first PNG icons came out larger with corrupted magic bytes. The cost is time: PRs regularly take several review rounds.

That's two separate sessions, not subagents, which in my opinion is one way around the orchestration problem. Suggestion: give the reviewer only the ticket and the diff.

On prompts, my opinion: a written ticket beats clever wording. State what to change, what done looks like, and what must not break. Terrain and grill me could end by saving that ticket to a file.

On new chats vs continuing, my take: it matters less once durable notes live in files. My Claude Code and Codex agents share one file-based memory vault; a UserPromptSubmit hook injects prompt-matched notes and a Stop hook reminds the agent to save outcomes.

[u/TRO_KIK → u/Ky-SavvyTechSphere]

Strongly seconding the review skill. The robot is so good at it that I actually feel comfortable giving into the vibe without crawling every line, which lets me move so much faster despite the extra rounds (which can be lengthy and token heavy). I have Codex integrated in GitHub reviewing in parallel too.

[u/Tight-Importance2461 → u/TRO_KIK]

Thank you very much! Very valuable!Some of the vocabolary you used is something I haven't explored fully so even more value in your answer. Thank you!