Prompting Guide
Write prompts that help December finish refactors, test fixes, and new projects.
This page helps you write prompts that December can finish without extra questions.
Effective Prompting Strategies
Tell December what to change and how to check the result.
1. Give Clear Verification Criteria
Say what “done” means. Give the command that proves it.
Change auth.service.ts to use argon2 instead of bcrypt. Run bun test test/auth and make sure all tests pass.
2. Point to Context Files
If you know where the problem is, name the file or the function. Type @ and a file name to add the file to the prompt.
In @packages/database/schema.prisma, add a SessionStatus enum. Generate the Prisma client and update session.service.ts.
3. Let the Agent Explore First
If you do not know the cause of a bug, ask December to find it before it changes code.
Find out why the tests in test/api fail with a 401 error. Run the tests, read the output, and fix the cause.
Plan large changes first
For a large change, type /plan and your goal. December writes a plan first. You approve or reject the plan before December changes code.
/plan move the session store from memory to Redis
Prompts from the terminal
To run one prompt without the interactive session, pass it to december with --print. December prints the result and exits.
december --print "Fix the failing unit tests in packages/server"