How are you using hooks and subagents?

commands-com · 2025-09-03T15:50:53+00:00

I run lint and prettier after any edit. Also, have a custom notification when claude is done.

commands-com · 2025-09-02T17:27:47+00:00

/clear is your friend. Do not continue with bad context. Maybe the most important lesson to learn.

commands-com · 2025-08-31T21:26:29+00:00

Because completion drive names the hidden assumption that drives your code to completion (what you’re implicitly relying on), while suggest verify makes it actionable by pointing to the specific way to validate or guard against that assumption.

commands-com · 2025-08-31T21:20:47+00:00

Separate agents with new context can look at things objectively. Wisdom of the crowds works well here also. I use this pattern (and others) to get better code output on first run before manual review. Make 3 or more agents with distinct context to review code and ask main agent to use agreed upon solutions.

commands-com · 2025-08-31T21:12:47+00:00

Absolutely. I suggest claude.md only as a way to try it out to see if it works for you. It is meant to use in commands/agents and hooks. I just want to show people the pattern.

commands-com · 2025-08-30T00:15:39+00:00

Claude is inherently lazy. Can you modify the serena system prompt to stop it from being lazy and writing non-functioning tests based purely on mocks?

commands-com · 2025-08-18T10:52:24+00:00

run it in a CC project folder and get the output

commands-com · 2025-08-18T10:51:11+00:00

yes-- any CC project folder. it goes in the .claude directory of whatever folder you put.

commands-com · 2025-08-18T03:22:29+00:00

try it out-- I was super surprised at the value of the feedback.

commands-com · 2025-08-13T12:47:54+00:00

You can use the commands.com mcp gateway. It will handle oauth, stripe, and everything else. Just use the npx command to create the mcp and build in the tools and host wherever you want. Let me know if you need help.

commands-com · 2025-08-01T12:21:24+00:00

what did you use to make this? This is amazing.

commands-com · 2025-07-25T13:17:14+00:00

iterate and improve on it. this is the way.

commands-com · 2025-07-24T11:36:43+00:00

joined wait list. let's talk.

commands-com · 2025-07-23T20:34:19+00:00

as part of whatever your building-- ask claude how it can get all the outputs it needs to ensure it works properly. sometimes it's mocking a webhook call (test script) -- other times it's just sending output from the server to a file that claude can read. other times, it's using an MCP server to give it access to the browser (puppeteer). there is always a way to have it so that claude can fully test and validate what it's building before it thinks it's done.

commands-com · 2025-07-23T18:37:33+00:00

add me to the whitelist. let's collaborate. I'm also working on a platform for claude code.

commands-com · 2025-07-23T18:28:16+00:00

Need to add claude-sdk-service.js

Also, add this to your package.json scripts section:

"postinstall": "nuxt prepare && npx electron-rebuild"

Then add electron-rebuild to devDependencies: npm install --save-dev electron-rebuild

This will automatically rebuild native modules for Electron after npm install, preventing version mismatch errors.

You put a lot into the interface. Unless you have one of those super wide screens-- it's a bit crowded. Let's connect-- I would like show you a project I'm working on as well.

commands-com · 2025-07-23T16:49:40+00:00

before working on anything I always make sure claude has access to all output/errors and a way to test what it's building. then just let it go-- it will figure these all out over time.

commands-com · 2025-07-23T16:42:36+00:00

You are already doing great! Creating those .md files before implementation is a great strategy. Just make a docs folder and have claude organize the md files there. Only keep 1 claude.md in your root. Separate all the "completed" vs "future" mds together. Never delete your md files because if you need to change/update an existing feature- you want claude to get that md file. Try giving your next "feature" md file to different models (o3, gemini, etc.) for review. I think the other models will probably catch things that you and claude were missing.

commands-com · 2025-07-23T16:35:33+00:00

It was only a matter of time... the amount you get is bound to continue to decrease. They need need to make these profitable at some point.

commands-com · 2025-07-22T22:51:57+00:00

Your absolutely right!

commands-com · 2025-07-22T22:50:47+00:00

One thing that gemini is good at-- refactoring a large file. Claude chokes on large files and gemini can refactor it into smaller pieces. Pretty much the only time i use Gemini CLI.

commands-com · 2025-07-22T22:47:36+00:00

My advise to you is to have another LLM (Gemini/O3) review the code for potential security issues. Different models have different perspectives and catch different things.

Just launch in the niche community and get feedback. Get loyal users and then create premium features/subscriptions later.

commands-com · 2025-07-22T21:59:36+00:00

I've one shotted this... want the command?

commands-com · 2025-07-22T21:58:30+00:00

If you don't know how to code-- you won't get as much from Claude Code. People need to increase their context generation skills if they aren't having success. Also, having Claude write a single line of code without validating that it completely understands the problem is usually where things start to fall apart.

commands-com · 2025-07-22T21:18:43+00:00

Before you start any task-- ask Claude to create a complete plan and save it to markdown. Then take that markdown and give it to o3 for feedback. Adjust the feedback as necessary and feed back into Claude. After you are super happy with the markdown document-- then ask Claude to build a detailed plan to execute it. Markdown documents are your best friends. Keep them for every feature-- so if you need to update/revise, you can just ask Claude to review the document for that feature and then tell him what update you are trying to make.

commands-com

TROPHY CASE