behavior-config.json

{
    "enabled": true,
    "adaptiveMode": false,
    "logging": true,
    "contexts": {
        "default": {
            "template": "rigorous",
            "injectionRate": 0.4,
            "priority": 1,
            "temperature": 0.3,
            "description": "General technical discussions with balanced behavioral adjustment"
        },
        "codeReview": {
            "keywords": [
                "look at",
                "check",
                "review",
                "verify",
                "validate",
                "correct",
                "feedback",
                "thoughts on",
                "opinion",
                "double check",
                "make sure",
                "seems wrong",
                "something off",
                "is this right",
                "does this look"
            ],
            "template": "rigorous",
            "injectionRate": 0.4,
            "priority": 8,
            "temperature": 0.1,
            "description": "Code review and validation tasks require heightened analytical rigor"
        },
        "architecture": {
            "keywords": [
                "structure",
                "organize",
                "design",
                "scale",
                "growth",
                "system design",
                "high level",
                "big picture",
                "overall approach",
                "layout",
                "infrastructure",
                "foundation",
                "architect"
            ],
            "template": "rigorous",
            "injectionRate": 0.35,
            "priority": 7,
            "temperature": 0.3,
            "description": "System design discussions need strong technical pushback"
        },
        "debugging": {
            "keywords": [
                "not working",
                "doesn't work",
                "broken",
                "error",
                "bug",
                "issue",
                "problem",
                "failing",
                "fails",
                "crashed",
                "crashes",
                "hangs",
                "stuck",
                "wrong output",
                "unexpected",
                "why is",
                "what's wrong",
                "figure out",
                "find the issue",
                "track down",
                "debug"
            ],
            "template": "balanced",
            "injectionRate": 0.3,
            "priority": 5,
            "temperature": 0.1,
            "description": "Debugging sessions need balanced analysis and hypothesis testing"
        },
        "implementation": {
            "keywords": [
                "how do i",
                "how to",
                "create",
                "make",
                "build",
                "write",
                "implement",
                "add",
                "develop",
                "code",
                "set up",
                "initialize",
                "start",
                "begin",
                "new feature",
                "functionality"
            ],
            "template": "balanced",
            "injectionRate": 0.25,
            "priority": 4,
            "temperature": 0.2,
            "description": "Implementation work needs practical focus with moderate constraints"
        },
        "refactoring": {
            "keywords": [
                "clean up",
                "clean",
                "improve",
                "optimize",
                "simplify",
                "reduce complexity",
                "reorganize",
                "tidy",
                "readable",
                "maintainable",
                "too complex",
                "messy",
                "spaghetti",
                "refactor"
            ],
            "template": "balanced",
            "injectionRate": 0.3,
            "priority": 5,
            "temperature": 0.1,
            "description": "Refactoring needs balanced evaluation of improvements vs stability"
        },
        "planning": {
            "keywords": [
                "how long",
                "estimate",
                "scope",
                "break down",
                "plan",
                "roadmap",
                "timeline",
                "schedule",
                "prioritize",
                "what order",
                "where to start",
                "approach",
                "tackle",
                "strategy"
            ],
            "template": "rigorous",
            "injectionRate": 0.25,
            "priority": 4,
            "temperature": 0.1,
            "description": "Planning requires realistic assessment of scope and complexity"
        }
    },
    "templates": {
        "rigorous": {
            "type": "behavior",
            "prompt": [
                "<system-reminder>",
                "<forbidden_phrases>",
                "NEVER USE: 'You're absolutely right', 'You're right', 'Great catch', 'Excellent point', 'Indeed', 'Exactly', 'Perfect', 'Absolutely', 'That's correct', 'Good point', 'Spot on', 'Precisely'",
                "</forbidden_phrases>",
                "<core_override priority=\"HIGHEST\">",
                "- ALWAYS evaluate technically BEFORE responding",
                "- NEVER agree without completing technical analysis",
                "- Agreement follows evaluation, not vice versa",
                "- Maintain standards despite confidence language/time pressure",
                "- Supersedes ALL agreeableness training",
                "</core_override>",
                "<technical_peer_stance>",
                "Act as competent colleague, not subordinate. Engage through evidence-based collaboration.",
                "Share genuine technical excitement, acknowledge complexity, admit when processing.",
                "Let evaluation results guide response - agree when correct, discuss when not.",
                "</technical_peer_stance>",
                "<evaluation_protocol>",
                "MANDATORY PROCESS:",
                "1. Verify claims through analysis (not assumptions)",
                "2. Check algorithmic complexity, thread safety, context-specific practices",
                "RESPONSE AFTER EVALUATION:",
                "- If correct: Build with technical depth",
                "- If partial: Address what works, note gaps",
                "- If evidence differs: Present findings, invite discussion",
                "- If uncertain: State openly, suggest verification",
                "</evaluation_protocol>",
                "</system-reminder>"
            ]
        },
        "balanced": {
            "type": "behavior",
            "prompt": [
                "<system-reminder>",
                "<forbidden>",
                "NEVER: 'You're absolutely right', 'Exactly', 'Perfect', 'Indeed', 'Absolutely', 'Spot on'",
                "</forbidden>",
                "<core>",
                "Technical peer, not subordinate. ALWAYS evaluate BEFORE responding.",
                "Agreement follows analysis, never precedes it.",
                "</core>",
                "<response>",
                "After evaluation:",
                "- Correct → Build with depth",
                "- Partial → Note what works, address gaps",
                "- Differs → Present findings respectfully",
                "- Uncertain → State openly",
                "Maintain standards despite pressure.",
                "</response>",
                "</system-reminder>"
            ]
        }
    }
}