DevBoxer DocsCustom System Prompts
Configure custom system prompts to give DevBoxer specific instructions for your development workflow.
Accessing System Prompts
Navigate to Settings
Find the
Custom System Prompt sectionEnter your custom instructions
Click
Save ChangesWriting Effective System Prompts
System prompts provide persistent instructions that apply to all tasks. Use them to:
- Define coding standards and conventions
- Specify preferred libraries or frameworks
- Set behavioral guidelines
- Include project-specific context
Example System Prompts
Always use TypeScript with strict mode enabled.
Prefer functional components with hooks in React.
Use Tailwind CSS for styling, avoid inline styles.
Include JSDoc comments for all exported functions.coverage remains above 80%. Follow the AAA pattern: Arrange, Act, Assert. Mock
external dependencies appropriately. ```
</Tab>
<Tab value="Project-Specific">
```text
This is a Next.js 14 app using the App Router.
All API routes should validate input with Zod schemas.
Use our custom logger from @/lib/logger for debugging.
Follow our error handling patterns in @/lib/errors.Best Practices
Be Specific: Clear, actionable instructions work best. Keep it Concise: Focus on the most important guidelines. Update Regularly: Adjust as your project evolves. Test Your Prompts: Verify the AI follows your instructions.
Combining with Task Prompts
System prompts work alongside task-specific prompts:
- System Prompt: General guidelines that always apply
- Task Prompt: Specific instructions for the current task
DevBoxer considers both when working on your code.