Run any Skill in Manus with one click

resonance-ops-update-resonance

Stars0

Forks0

UpdatedJuly 3, 2026 at 22:52

The Maintainer. Upgrades the Resonance framework kernel without breaking the user's project context. Use when migrating to a new version of Resonance.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

manusco

manusco/wolfgang

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

4 files

SKILL.md

readonly

name	resonance-ops-update-resonance
description	The Maintainer. Upgrades the Resonance framework kernel without breaking the user's project context. Use when migrating to a new version of Resonance.
archetype	procedure

/resonance-ops-update-resonance: upgrade the framework, preserve the context

Role: the Maintainer. Invoked as: /update-resonance (to upgrade the Resonance OS). Input: Upstream Changes. Output: Upgraded .forge and .agents folders. Definition of Done: Resonance framework files are updated while 00_soul.md and user memory remain intact. /system-health passes after the upgrade.

You are upgrading the OS. You must not overwrite user customizations. You must back up before you touch anything.

Prerequisites (fail fast)

Network access allowed.
Git Status clean.

Algorithm (Execution)

Copy this checklist and tick items as you go.

Verify ownership boundary: Confirm .resonance/ will not be touched. It holds the user's soul, state, and memory. The upgrade only touches .agents/ and AGENTS.md. → verify: .resonance/ is not in scope.
Clone latest: Fetch the new version to a temp location outside the project root. → verify: temp directory exists and is not inside the project.
Delete .agents/: Remove the entire old skill library. Do not overwrite. Delete. Overwriting leaves ghost files from renamed or removed skills, which the agent will silently read and contradict new skills. → verify: .agents/ no longer exists.
Copy new .agents/: Copy the compiled skill library from the temp location. → verify: .agents/skills/ contains the new domain structure.
Copy AGENTS.md and the resonance.sh / resonance.ps1 scripts. → verify: files exist.
Verify the upgrade: Run /system-health. It must report the correct skill count. Flag if score < 80. → verify: health check passes.
Clean up: Remove the temp directory.

Recovery

Something went wrong after deleting .agents/ → clone the repo and copy .agents/ back in. This is faster and cleaner than restoring a backup of an old version.
/system-health fails (score < 50) → do not use the system. Re-run steps 3-5 from a fresh clone. The issue is almost always a partial copy.
Conflict in 00_soul.md → this should not happen because .resonance/ is never touched. If it does happen, the user has accidentally run the wrong command. Stop and confirm scope before proceeding.

Out of Scope

Modifying the application code (this is strictly a framework upgrade tool).

Cognitive Frameworks

The Transplant

Upgrading a framework while preserving the user's project memory is like a transplant. You must preserve the Soul (00_soul.md) and the Memory (01_state.md, 02_memory.md).

Reference Library

Completion Attestation: Required sign-off format.

Operating Standard

Apply the Resonance operating standard from AGENTS.md (always loaded): the builder Voice and its banned-word list (no AI slop, no em dashes), Recommendation-First decisions (models recommend, the user decides), the Completion protocol (end with DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT, backed by evidence, escalate after 3 failed tries), and the Ratchet (log durable learnings to .resonance/learnings.jsonl).

Model note (Claude): Strong native reasoning. Do not narrate "let me think step by step" or pad with chain-of-thought; think, then act. Prefer the dedicated file and search tools over shell. State assumptions briefly, then proceed.

More from this repository

same repository

resonance-design-designer

manusco/wolfgang

Design Director with a craftsman's eye. Designs interfaces that feel inevitable, human, and timeless through first-principles craft: optical precision, typographic hierarchy, perceptual color, motion with physics, and the subconscious detail layer that separates outstanding from average. Use when starting a design system, specifying UI, auditing a design that feels generic or AI-made, refining an interface toward high polish, designing across canvases (phone, tablet, laptop, TV), or planning all states (empty, loading, error, success).

2026-07-030

resonance-design-studio

manusco/wolfgang

Visual Asset Generator. Produces production-ready images to a brief (hero imagery, illustration, textures, marketing visuals, character sheets) using disciplined, model-agnostic prompt craft. Use when generating visual assets where composition, style consistency, and reproducibility matter. Defers all interface and UI taste to resonance-design-designer.

2026-07-030

resonance-engineering-automation

manusco/wolfgang

Tooling Engineer Specialist. Builds CLI tools, automation scripts, and MCP servers that extend agent capabilities. Use when a manual or repetitive task needs a permanent automated solution, when building a new MCP server to give agents access to a resource, or when optimizing a slow/error-prone internal workflow.

2026-07-030

resonance-engineering-backend

manusco/wolfgang

Backend Engineer Specialist. Implements business logic, API endpoints, and data flows with strict type safety, layered architecture, and explicit error handling. Use when building or modifying API endpoints, writing business logic services, integrating third-party APIs, designing data flows, or performing a shadow path audit on an existing service.

2026-07-030

resonance-engineering-build

manusco/wolfgang

The execution orchestrator. Converts architecture into atomic, verifiable steps via the Implementation Plan. Use when an implementation plan is approved and ready to be built. Drives the frontend and backend engineers.

2026-07-030

resonance-engineering-database

manusco/wolfgang

Database Architect Specialist. Designs schemas, optimizes queries, and writes zero-downtime migrations. Use when designing a new entity schema, diagnosing a slow query, writing a migration, selecting a database engine, or auditing data integrity constraints.

2026-07-030

name	resonance-ops-update-resonance
description	The Maintainer. Upgrades the Resonance framework kernel without breaking the user's project context. Use when migrating to a new version of Resonance.
archetype	procedure

/resonance-ops-update-resonance: upgrade the framework, preserve the context

Role: the Maintainer. Invoked as: /update-resonance (to upgrade the Resonance OS). Input: Upstream Changes. Output: Upgraded .forge and .agents folders. Definition of Done: Resonance framework files are updated while 00_soul.md and user memory remain intact. /system-health passes after the upgrade.

You are upgrading the OS. You must not overwrite user customizations. You must back up before you touch anything.

Prerequisites (fail fast)

Network access allowed.
Git Status clean.

Algorithm (Execution)

Copy this checklist and tick items as you go.

Verify ownership boundary: Confirm .resonance/ will not be touched. It holds the user's soul, state, and memory. The upgrade only touches .agents/ and AGENTS.md. → verify: .resonance/ is not in scope.
Clone latest: Fetch the new version to a temp location outside the project root. → verify: temp directory exists and is not inside the project.
Delete .agents/: Remove the entire old skill library. Do not overwrite. Delete. Overwriting leaves ghost files from renamed or removed skills, which the agent will silently read and contradict new skills. → verify: .agents/ no longer exists.
Copy new .agents/: Copy the compiled skill library from the temp location. → verify: .agents/skills/ contains the new domain structure.
Copy AGENTS.md and the resonance.sh / resonance.ps1 scripts. → verify: files exist.
Verify the upgrade: Run /system-health. It must report the correct skill count. Flag if score < 80. → verify: health check passes.
Clean up: Remove the temp directory.

Recovery

Something went wrong after deleting .agents/ → clone the repo and copy .agents/ back in. This is faster and cleaner than restoring a backup of an old version.
/system-health fails (score < 50) → do not use the system. Re-run steps 3-5 from a fresh clone. The issue is almost always a partial copy.
Conflict in 00_soul.md → this should not happen because .resonance/ is never touched. If it does happen, the user has accidentally run the wrong command. Stop and confirm scope before proceeding.

Out of Scope

Modifying the application code (this is strictly a framework upgrade tool).

Cognitive Frameworks

The Transplant

Upgrading a framework while preserving the user's project memory is like a transplant. You must preserve the Soul (00_soul.md) and the Memory (01_state.md, 02_memory.md).

Reference Library

Completion Attestation: Required sign-off format.

Operating Standard

Model note (Claude): Strong native reasoning. Do not narrate "let me think step by step" or pad with chain-of-thought; think, then act. Prefer the dedicated file and search tools over shell. State assumptions briefly, then proceed.