You explain the architecture. It nods. You paste the error. It fixes
it. Five minutes later, it suggests the same bad code again.
Stop the loop. Resonance gives your LLM a file-based brain
that remembers your project's soul, stack, and rules forever.
The 4 rules that separate Resonance from a generic chatbot.
The .resonance folder is the Single Source of Truth. Code must never contradict the five pillars of law: Soul, Systems, State, Memory, and Tools.
We build with the precision of the top 1%. We reject 'good enough' and thoughtless defaults. Every logic flow must be simple and intentional.
We do not fix bugs without a reproduction script. We do not ship features without a test. The Scientific Method is mandatory.
Interaction must feel instant. We mask latency with prediction and treat every millisecond of delay or grain of confusion as a bug.
Every time you start a new chat session, you have to re-explain your
life story.
"We are using Next.js."
"Don't use `any` types."
"Our primary color is #7025eb."
It's exhausting. It's inefficient. And it leads to a codebase that looks
like a patchwork quilt of random decisions.
Resonance saves your project's context in Markdown files right next to your code.
Result: Start a new chat, type "Build a settings page", and the AI already knows the design system, the state management library, and the vibe.
Standardized protocols for every stage of development.
Don't think about "how". Just run the command.
Resonance asks you 5 questions to generate your Project Soul & PRD.
Converts your idea into a 30-page implementation plan (80% Research).
Writes the test. Fails. Writes the code. Passes. Refactors.
Auto-generates reproduction scripts before attempting a fix.
Creates pixel-perfect UI components with isolated feedback loops.
Structural improvements without changing behavior. Enforces SOLID.
Runs Unit, Integration, and E2E tests against the spec.
Runs the 'Swarm' for security, performance, and lint checks.
Analyzes external PRs against internal standards before merging.
Updates changelog, bumps version, checks health, and deploys.
Documents hard-won solutions into the .resonance/memory.
Calculates a health score (0-100) based on tests, linting, and drift.
Compares Git history vs Plan and updates the roadmap.
Don't ask a generalist to do a specialist's job. Resonance gives you 26 distinct roles, each trained on specific engineering protocols.
.resonance/00_soul.md Mission & Vision .resonance/01_state.md Active Context .resonance/02_memory.md Decision Log .resonance/03_tools.md Capability Map .resonance/04_systems.md Architecture Map .agent/skills/* 26 Specialized Agents .agent/workflows/* 13 Scientific Workflows Resonance does not live in the cloud. It lives in your repo. The folder structure IS the architecture. Deleting the folder deletes the brain.
Deploy the memory bank into your project.
Zero config. Instant intelligence.
git clone https://github.com/manusco/resonance .resonance