Posted on :: Updated on ::

Potential use cases

  • Implement features
  • Refactor this subsystem
  • Research this library
  • Set up this service
  • Write tests, run them, fix failures
  • Compare approaches , and propose a plan
  • Troubleshoot issues and fix them

Tips

  • Always use better model for planing: Opus > Sonnet.

Skills/Tools

  • Caveman
  • spec-kit
  • For larger features, enable CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
    • 1 reviewer agent
    • 1 QE agent writes tests
  • diffity

Prompts

Research

read this folder in depth, understand how it works deeply, what it does and all its specificities. when that’s done, write a detailed report of your learnings and findings in research.md

Eg: I want to build a static website (on github pages) for my learnings, suggest a way to do so. I use obsidian to take notes. Take inspiration from similar examples: https://github.com/simonw/til, https://github.com/jbranchaud/til

Plan

I want to build a new feature [name and description] that extends the system to perform [business outcome]. write a detailed plan.md document outlining how to implement this. include code snippets

Eg:

The workdir contains two projects: til, ms-choudhary.github.io. I want to integrate the til notes in my static website (zola based), such that static site is build & released on every commit of til. Also I want to auto generate a readme (like this: https://github.com/jbranchaud/til). Take inspiration from https://github.com/simonw/til. use AskUserQuestion tool to clarify any decisions. write a detailed plan.md document outlining how to implement this. include code snippets.

Annotate

I added a few notes to the document, address all the notes and update the document accordingly. don’t implement yet

Add a todo list (for longer tasks)

add a detailed todo list to the plan, with all the phases and individual tasks necessary to complete the plan - don’t implement yet

Implement

With todo

implement it all. when you’re done with a task or phase, mark it as completed in the plan document. do not stop until all tasks and phases are completed. do not add unnecessary comments or jsdocs, do not use any or unknown types. continuously run typecheck to make sure you’re not introducing new issues.

Without todo

implement it all. do not stop until all tasks and phases are completed. do not add unnecessary comments or jsdocs, do not use any or unknown types. continuously run typecheck to make sure you’re not introducing new issues.

Sources

  • [[]]