Claude code commands

brainstorm.md

Ask me one question at a time so we can develop a thorough, step-by-step spec for this idea. Each question should build on my previous answers, and our end goal is to have a detailed specification I can hand off to a developer. Let’s do this iteratively and dig into every relevant detail. Remember, only one question at a time.

Once we are done, save the spec as specs/{title}.md

Ask if the user wants to create a git repo on github. if so, commit the spec.md to git and push it to the newly created git repo.

Here’s the idea: $ARGUMENTS

commit-and-push.md

ADD all modified and new files to git. If you think there are files that should not be in version control, ask the user. If you see files that you think should be bundled into separate commits, ask the user. THEN commit and push

fix-clickup-bug.md

Please analyze and fix the Clickup issue: $ARGUMENTS.

Follow these steps:

1. Use Clickup MCP to get the issue details
2. Understand the problem described in the issue
3. Search the codebase for relevant files
4. Implement the necessary changes to fix the issue
5. Write and run tests to verify the fix
6. Ensure code passes linting and type checking
7. Create a descriptive commit message
8. Push and create a MR using glab

Remember to use the Gitlab CLI (glab) for all Gitlab-related tasks.

fix.md

READ the output from the terminal command to understand the error that is being displayed. THEN FIX the error. Use context7 and brave-search MCPs to understand the error. THEN re-run the command in the terminal. If there is another error, repeat this debugging process.

prime.md

READ docs/**.md THEN run git ls-files to understand the context of the project