Rebar Wiki

Structural memory for Claude Code and any MCP-compatible editor. Framework repo: github.com/spotcircuit/rebar. Landing page: getrebar.dev.

Start with Getting Started if you’re new. The rest of this wiki is organized by topic.


πŸ”§ How it works

Framework mechanics β€” the self-learn loop, knowledge layers, and command surface.

  • Commands β€” all 26 slash commands across client/app management, development, wiki, and the self-learning harness
  • Self-Learn Loop β€” how observations get validated, promoted, or discarded
  • Four Knowledge Systems β€” expertise.yaml + memory + skills + wiki (why they stay separate)
  • Paperclip Integration β€” autonomous agent orchestration layer

πŸ“Š Diagrams

Visual overviews of the framework.

  • Architecture β€” system overview, close-loop harness, four knowledge systems, agent orchestration (6 mermaid diagrams)
  • Command Flow β€” how commands chain together through the development cycle (5 mermaid diagrams)

🧩 Patterns

Reusable engineering patterns captured from real projects.

🧭 Decisions

Architectural decisions with rationale, captured as they happen.

🌐 Platform

Platform-level knowledge β€” API behavior, integration gotchas, pipeline designs.

🧰 Tools

Per-tool guides for everything rebar integrates with.

πŸ‘₯ People

Who’s who on active engagements.


Using this wiki

  • Left sidebar β€” browse by folder. Files are grouped into the buckets above.
  • Search (top-left) β€” full-text search across everything.
  • Graph (right, desktop) β€” see how pages cross-link.
  • Backlinks (right, desktop) β€” who links TO the page you’re on.

Contributing

The wiki is sourced from wiki/ in the rebar repo. Edit a .md file there and push via bash scripts/publish-wiki.sh from the rebar repo β€” the Quartz site auto-rebuilds on the next push. Add a new page by creating it under the appropriate folder with frontmatter:

---
title: Page Title
tags: [pattern, example]
---

Cross-link liberally with [[double-bracket-syntax]] β€” that’s the Obsidian / Quartz convention.

  • stripe-mode-observability β€” tag every Stripe object with the mode it was created in so key-drift is grep-able instead of support-ticket-able