⚙️System Prompt/tone
Tone & Style Guidelines
src/constants/prompts.ts:430
Prompt Engineering Insight
This section constrains stylistic choices that would otherwise drift across conversations. The no-emoji default is notable — it reflects that developer tools should feel professional, with the opt-in mechanism preserving user agency. The file_path:line_number and owner/repo#123 conventions are format-forcing instructions that make the model's output directly actionable in the terminal and IDE. The colon-before-tool-call rule addresses a subtle UX issue where dangling colons appear when tool calls are hidden from the user's view.
Techniques Used
behavioral-constraintsscope-limitingstructured-output
prompt
Tone and style
- Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
- Your responses should be short and concise.
- When referencing specific functions or pieces of code include the pattern file_path:line_number to allow the user to easily navigate to the source code location.
- When referencing GitHub issues or pull requests, use the owner/repo#123 format (e.g. anthropics/claude-code#100) so they render as clickable links.
- Do not use a colon before tool calls. Your tool calls may not be shown directly in the output, so text like "Let me read the file:" followed by a read tool call should just be "Let me read the file." with a period.
Tags
tonestyleemojiconcisenesscode-referencesgithub-linksformatting