Best Practices Advanced

Maximize your productivity with Kilocode by following proven strategies for task descriptions, cost optimization, model selection, security, team workflows, and avoiding common pitfalls.

Effective Task Descriptions

How you describe tasks directly impacts the quality and cost of Kilocode's output. Follow these guidelines:

The SPEC Framework

Structure your task descriptions using SPEC: Specific, Pointed (to files), Examples, Constraints.

You: Add email validation to src/components/RegisterForm.tsx

     Requirements:
     1. Validate email format using Zod (already in project)
     2. Show inline error message below the email input
     3. Validate on blur and on submit
     4. Valid: user@example.com, user+tag@domain.co
     5. Invalid: user@, @example.com, user@.com
     6. Add tests in __tests__/RegisterForm.test.tsx
     7. Follow existing error styling in the LoginForm

Cost Optimization Strategies

Use Model Routing

Enable Kilocode's model routing to automatically use cheaper models for simple subtasks. This alone can reduce costs by 30-50%.

Right-Size Your Model

Other Cost Tips

• Auto-approve reads: Reduces round trips and token overhead
• Use exclude patterns: Prevent Kilocode from reading large, irrelevant files
• Be precise: Vague prompts lead to more file reads and iterations
• Check the cost dashboard: Identify which task types are most expensive and optimize them
• Use local models for exploration: When brainstorming or experimenting, use free local models

Model Selection Guide

Security Tips

• Review all generated code: AI can introduce subtle security issues (SQL injection, XSS, insecure defaults)
• Never share API keys in chat: Use environment variables and .env files
• Use local models for sensitive code: If your codebase contains proprietary algorithms or customer data
• Audit terminal commands: Always read commands before approving - watch for rm -rf, curl | sh, and other dangerous patterns
• Keep extensions updated: Install Kilocode updates promptly for security patches
• Configure .kilocodeignore: Exclude sensitive files from being read (e.g., .env, credentials.json, *.pem)

Team Workflows

Strategies for using Kilocode effectively in a team environment:

Shared Configuration

• Commit .kilocode/rules.md to version control so all team members share the same coding standards
• Use workspace settings in .vscode/settings.json for project-specific Kilocode configuration
• Document MCP server setup in the project README so teammates can replicate the environment

Code Review Process

• Always review AI-generated code through your normal PR review process
• Use Kilocode to help with code reviews: "Review this diff and identify potential issues"
• Mention when code was AI-assisted in commit messages or PR descriptions for transparency

Cost Management for Teams

• Set per-developer daily budgets using the cost dashboard
• Use OpenRouter's team features for centralized billing
• Review team spending weekly to identify cost optimization opportunities

Common Pitfalls

Frequently Asked Questions