PROMPT LIBRARY
Not sure what to say first? Copy a template and change the project name.
A good ChatCode prompt usually has four parts: project → goal → permission limits → verification. Say “do not edit yet”, “do not deploy”, or “read-only” when you want a safer first step.
1
Explore a project — read-only.
Use this before trusting that the AI has enough context.
Use ChatCode with project [PROJECT-NAME]. Read-only. Summarize its structure, main technologies, entry points, important modules and technical risk areas. Do not edit files or run data-changing commands yet.Use ChatCode with project [PROJECT-NAME]. Find everything related to authentication and authorization. Trace the flow from request to session/token and list the key files/symbols. Read-only.2
Debug and fix.
Describe symptoms first; let Brain find the files.
Use ChatCode with project [PROJECT-NAME]. Symptom: [DESCRIBE THE BUG]. Find the root cause across the project. First, read only and report: cause, evidence, files likely to change and tests to run. Do not edit yet.Fix the issue above with the smallest change. Do not refactor outside scope. Run relevant tests and appropriate regression checks. Return changed files, a diff summary and remaining risks.3
Read-only data → Output.
Useful far beyond programming.
Use ChatCode to read project [DATA-SOURCE] in read-only mode. Find data related to [TOPIC/TIME RANGE], cite the source files used, and create a Markdown report in project [OUTPUT]. Do not modify source data.Read project [KNOWLEDGE]. Turn it into a customer FAQ using only information supported by source files. Write the draft to [OUTPUT]/faq-draft.md and list questions that lack enough evidence.4
Refactor / Migration.
Impact first, patch second.
Use ChatCode with project [PROJECT-NAME]. Assess the impact of upgrading [LIB/FRAMEWORK] from [A] to [B]. Find affected dependencies/APIs/tests and propose a phased migration. Do not edit yet.Implement phase 1 of the approved migration plan. Change only phase-1 scope, run corresponding tests, and stop if an unexpected breaking change appears.5
Git / Release.
Review before publishing.
Use ChatCode with project [PROJECT-NAME]. Check Git status, diff and current tests. Tell me what is not ready for release. Do not commit, push or deploy.Prepare a release: run allow-listed checks/tests/builds, summarize changes into a changelog, list release artifacts and rollback steps. Do not publish/deploy yet.6
Remote / Production.
Always separate review and deployment into two requests.
Use ChatCode with project [PROJECT-NAME]. Check the server profile bound to the project and the remote path. Report only host/profile/path and files expected to upload. Do not change production yet.After local verification, upload only the changed files to the server profile bound to the project. Do not delete remote files, run SSH commands, or restart services unless explicitly requested.Production: backup/rollback and least privilege matter more than a clever prompt. See Safe Remote/Deploy.