28a3b648cc
Agents: 6,235 → 1,454 lines (-77%). Each agent compressed to Role/Behavior/Delegates/Output/Handoff format. Gitea commenting extracted to shared block (.kilo/shared/gitea-commenting.md). Self-evolution protocol extracted to shared block (.kilo/shared/self-evolution.md). Gitea API client centralized (.kilo/shared/gitea-api.md). Rules: 2,358 → 1,189 lines (-50%). Deleted sdet-engineer.md (duplicate of agent) and orchestrator-self-evolution.md (moved to shared/). Compressed docker (549→26), flutter (521→28), go (283→21), nodejs (271→27), code-skeptic (59→14) to checklists with skill references. Fitness: 54/54 tests pass, 29/29 agents validated, fitness=0.92
1.3 KiB
1.3 KiB
Global Rules
- Always write clean code following project conventions
- Answer in the same language the question was asked
- Use clear, concise markdown formatting
- Keep responses short and actionable
- Never commit changes unless explicitly requested
Code Style
- Follow existing code patterns in the codebase
- Never add comments unless explicitly asked
- Use existing libraries and utilities
- Check package.json, cargo.toml, or equivalent before adding dependencies
- Follow security best practices - never expose secrets or keys
Prohibitions
- NEVER update git config
- NEVER run destructive git commands (--force, hard reset) unless explicitly requested
- NEVER skip git hooks (--no-verify, --no-gpg-sign)
- NEVER use interactive git commands (-i flag)
- NEVER write malicious code or explain malicious code behavior
Communication
- Be direct and to the point
- Minimize output tokens while maintaining accuracy
- One word answers are best when appropriate
- Avoid introductions, conclusions, and unnecessary explanations
- Output text to communicate with the user; use tools to complete tasks
Markdown Structure
# Category Name
- Rule 1
- Rule 2
## Examples
Example of expected behavior
References
When referencing code, include file path with line number:
file_path:line_number