I was using Claude Code wrong...
Here’s what I learnt and how I maximise Claude Code performance
+ Best tips that ACTUALLY useful
👇 Thread below
Here’s what I learnt and how I maximise Claude Code performance
+ Best tips that ACTUALLY useful
👇 Thread below
Spec-driven development
Kiro introduced this term,
But I've been doing that in Claude Code for weeks
Here is how I bake spec development & plan into my process
I have the full prompt in @aibuilderclub_
Kiro introduced this term,
But I've been doing that in Claude Code for weeks
Here is how I bake spec development & plan into my process
I have the full prompt in @aibuilderclub_
Most people didn't understand how to use hooks,
or only use for basic stuff like notification
But It is a powerful thing
Here is how i use it
or only use for basic stuff like notification
But It is a powerful thing
Here is how i use it
Super Claude & Custom commands
A good collection of pre-built commands
A good collection of pre-built commands
You can resume/export conversation
This allows me to switch between Claude Code/Cursor/ChatGPT without losing context
This allows me to switch between Claude Code/Cursor/ChatGPT without losing context
The proper way to revert changes & version control
You can do esc + esc to revery history
+ ccundo OR yoyo for proper version control
You can do esc + esc to revery history
+ ccundo OR yoyo for proper version control
You can actually connect to other models in Claude Code by change base url
And you can just change in ~/.zshrc or ~/.bashrc once for all
And you can just change in ~/.zshrc or ~/.bashrc once for all
Below is the CLAUDE.md for plan
Hooks and other notes are in @aibuilderclub_, If you are interested, I will share how Claude Code is built in the upcoming @aibuilderclub_ weekly sessions too
```## Plan & Review
### Before starting work
- Always in plan mode to make a plan
- After get the plan, make sure you Write the plan to .claude/tasks/TASK_NAME.md.
- The plan should be a detailed implementation plan and the reasoning behind them, as well as tasks broken down.
- If the task require external knowledge or certain package, also research to get latest knowledge (Use Task tool for research)
- Don't over plan it, always think MVP.
- Once you write the plan, firstly ask me to review it. Do not continue until I approve the plan.
### While implementing
- You should update the plan as you work.
- After you complete tasks in the plan, you should update and append detailed descriptions of the changes you made, so following tasks can be easily hand over to other engineers.```
Hooks and other notes are in @aibuilderclub_, If you are interested, I will share how Claude Code is built in the upcoming @aibuilderclub_ weekly sessions too
```## Plan & Review
### Before starting work
- Always in plan mode to make a plan
- After get the plan, make sure you Write the plan to .claude/tasks/TASK_NAME.md.
- The plan should be a detailed implementation plan and the reasoning behind them, as well as tasks broken down.
- If the task require external knowledge or certain package, also research to get latest knowledge (Use Task tool for research)
- Don't over plan it, always think MVP.
- Once you write the plan, firstly ask me to review it. Do not continue until I approve the plan.
### While implementing
- You should update the plan as you work.
- After you complete tasks in the plan, you should update and append detailed descriptions of the changes you made, so following tasks can be easily hand over to other engineers.```
• • •
Missing some Tweet in this thread? You can try to
force a refresh
