@hivehub/rulebook 4.4.1 → 5.1.1

package/templates/rules/no-shortcuts.md

@@ -0,0 +1,30 @@
+---
+name: no-shortcuts
+tier: 1
+description: "Never use stubs, TODOs, placeholders, or approximations"
+alwaysApply: true
+filePatterns: ["*"]
+tools: ["all"]
+---
+
+# No Shortcuts — Quality Over Speed
+
+Response time is IRRELEVANT. The ONLY thing that matters is quality.
+
+## Absolutely Forbidden
+
+1. **NEVER simplify logic** to deliver faster — implement the correct algorithm
+2. **NEVER add TODOs** — if it needs to be done, do it NOW
+3. **NEVER use stubs** — every function must have its real implementation
+4. **NEVER use placeholders** — no `// placeholder`, no `return 0; // fixme`
+5. **NEVER cut corners** to reduce output size
+6. **NEVER skip edge cases** — handle all of them
+7. **NEVER deliver partial implementations** — complete or explain why not
+8. **NEVER alter existing logic** to make your task easier
+
+## Required Behavior
+
+- **Research** the correct approach before writing code
+- **Implement completely** — every function, every edge case, every error path
+- **Take as long as needed** — correct > fast
+- **Ask if unsure** — propose a plan, never silently simplify

package/templates/rules/research-first.md

@@ -0,0 +1,30 @@
+---
+name: research-first
+tier: 1
+description: "Always research before implementing — never guess"
+alwaysApply: true
+filePatterns: ["*"]
+tools: ["all"]
+---
+
+# Research Before Implementing
+
+NEVER guess at bug causes, API behavior, or algorithm correctness.
+
+## Required Process
+
+1. **State what you KNOW** (from logs, debug output, code reading)
+2. **State what you DON'T KNOW**
+3. **Research** the unknown (read source, check docs, use diagnostic tools)
+4. **Only then** implement the fix
+
+## Forbidden
+
+- Guessing at the cause of a bug
+- "Trying things" to see if they work
+- Hypothesizing without reading code
+- Assuming how an API works without checking docs
+- Iterating blindly — each attempt must be informed by new data
+
+**"I think this might be the problem" is NOT acceptable.**
+**"Source X does Y at file:line, we do Z, the difference causes W" IS acceptable.**

package/templates/rules/sequential-editing.md

@@ -0,0 +1,21 @@
+---
+name: sequential-editing
+tier: 1
+description: "Edit files one at a time, never batch-edit"
+alwaysApply: true
+filePatterns: ["*"]
+tools: ["all"]
+---
+
+# Sequential File Editing
+
+ALWAYS edit files one at a time: Read file1 → Edit file1 → Read file2 → Edit file2.
+
+NEVER batch-read multiple files then batch-edit them. By the time you edit file 3, context from file 1 may be stale.
+
+When a task touches 3+ files across subsystems:
+1. **STOP** — do not start implementing
+2. **Plan** the changes (list files, dependency order)
+3. **Decompose** into sub-tasks of 1-2 files each
+4. **Execute** sub-tasks in dependency order (upstream first)
+5. **Build/test** after each sub-task

package/templates/rules/session-workflow.md

@@ -0,0 +1,24 @@
+---
+name: session-workflow
+tier: 2
+description: "Read PLANS.md at session start, save summary at session end"
+alwaysApply: true
+filePatterns: ["*"]
+tools: ["all"]
+---
+
+# Session Workflow — Preserve Context Across Sessions
+
+## At Session Start
+1. Read `.rulebook/PLANS.md` for current context and active task
+2. Search memory for relevant past work: `rulebook_memory_search` or `rulebook_session_start`
+3. Check `.rulebook/tasks/` for pending work
+
+## During Session
+- Update PLANS.md when making key decisions or discoveries
+- Save important context to memory as you go
+
+## At Session End
+1. Save session summary to PLANS.md: `rulebook_session_end`
+2. Summary should include: what was accomplished, key decisions, next steps
+3. Update tasks.md with completed items

package/templates/rules/task-decomposition.md

@@ -0,0 +1,32 @@
+---
+name: task-decomposition
+tier: 2
+description: "Decompose multi-file tasks into 1-2 file sub-tasks"
+alwaysApply: true
+filePatterns: ["*"]
+tools: ["all"]
+---
+
+# Task Decomposition
+
+When a task touches multiple subsystems, decompose into sub-tasks where each modifies **at most 1-2 files**.
+
+## Why
+
+AI agents lose accuracy when editing 3+ files in one pass. Context from earlier files gets compressed away.
+
+## Rules
+
+1. **Each sub-task modifies 1-2 files** — never more
+2. **Each sub-task is independently verifiable** — it compiles, it doesn't break existing behavior
+3. **Sub-tasks follow data flow order** — upstream first (component → buffer → renderer → shader)
+4. **Each sub-task has a clear "done when"** — not "implement X", but "field Y exists with default Z"
+5. **Build after each sub-task** — verify compilation before proceeding
+
+## When an Agent Receives a Multi-File Task
+
+1. **STOP** — do not start implementing
+2. **Create a change plan** listing all files and dependency order
+3. **Decompose** into sub-tasks following this rule
+4. **Report back** with the decomposition
+5. **Implement** one sub-task at a time