Codebox Best Practices

Write Clear, Specific Prompts

Claude Code works best when you provide clear context about what you want to accomplish. Instead of vague instructions like “fix the bug,” describe the specific behavior you're seeing and what you expect instead.

• Reference specific files, functions, or components by name
• Describe the expected behavior alongside the current behavior
• Break large tasks into smaller, focused requests
• Provide examples of input and output when relevant

Manage Sessions Effectively

Codebox sessions are ephemeral — they spin up on demand and are cleaned up when you're done. To avoid losing work, commit and push your changes regularly. Each session can create branches and open pull requests directly.

• Push changes frequently — sessions are ephemeral and uncommitted work is lost on shutdown
• Use one session per task or feature for cleaner git history
• Review the generated pull request before merging

Leverage the Development Server

Codebox can run your application's development server and forward the port to your browser. Use this to preview changes in real time — especially useful for frontend work where you want to see visual changes immediately.

Review Before Merging

While Claude Code produces high-quality code, always review the generated pull request before merging. Pay attention to edge cases, test coverage, and whether the changes align with your project's conventions and architecture.

• Check that tests cover the new or changed behavior
• Verify the changes follow your project's coding standards
• Test the changes locally or in CI before merging to main