resonance-ops-core

Initializes project scaffolds and maintains file-based state and memory across sessions.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/manusco/wolfgang --skill resonance-ops-core-manusco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resonance-ops-core
Source: https://github.com/manusco/wolfgang/tree/main/.agents/skills/ops/core
Command: npx skills add https://github.com/manusco/wolfgang --skill resonance-ops-core-manusco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI coding sessions lose context between runs, forcing users to repeat decisions, plans, and progress. This Skill persists project state, decisions, and lessons in structured files so any new session can orient itself without asking the user to repeat context. ## Core Features & Use Cases - Project Initialization: Scaffolds the .resonance/ directory with soul, state, memory, tools, and systems files, plus docs and a per-host context bridge. - State Persistence: Maintains 01_state.md as a session log and active plan checklist, and records durable lessons and decisions in 02_memory.md or a typed ledger. - Orchestration: Breaks complex requests into checklist items and delegates implementation to backend, frontend, and design specialists. - Use Case: A user returns to a project after a week and asks what was decided about the database. The Skill reads the state and memory files, cites the exact decision entry, and lists pending tasks from the active plan instead of guessing. ## Quick Start Ask the agent to initialize a new Resonance project and set up the state files for what you want to build.

Frequently Asked Questions about resonance-ops-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I initialize a Resonance project in my repository?▼

Invoke the /init entrypoint. The Skill checks whether .resonance/ exists, creates it if missing, asks what you want to build, then writes the soul, state, memory, tools, and systems files plus a docs scaffold and host context bridge.

How does the Skill preserve context between AI sessions?▼

It writes session progress, decisions, and lessons into .resonance/ markdown files that load at the start of every session. A recall script retrieves relevant memory slices by topic, and an optional typed ledger stores decisions, lessons, metrics, customers, and experiments as queryable entries.

What is the difference between 02_memory.md and the state ledger?▼

When .resonance/ledger/ exists, it is the system of record for decisions, lessons, metrics, customers, and experiments as typed entries with ids and supersede tracking. The 02_memory.md file then keeps only library notes and pointer lines; without a ledger, it holds the full lessons and decisions index.

Will the Skill make destructive changes like dropping tables automatically?▼

No. Its User Sovereignty principle requires presenting any destructive or architectural change as a recommendation and waiting for explicit user verification before executing. It stops and asks rather than proceeding on its own.

When should I not use this Skill for a task?▼

Do not use it to write application code or design UI systems directly. It delegates backend work to resonance-engineering-backend, frontend work to resonance-engineering-frontend, and design work to resonance-design-designer, acting only as orchestrator and state keeper.