opendesigner-extend

Topics in the source

• OpenDesigner: extend an existing system
• 1. Start-up routine (before touching anything)
• 2. Classify the request
• 3. Locks and conflicts
• Standards
• 4. Make the change
• Add a token
• 5. End of every implementation: review

Use this skill when the project already has an OpenDesigner system and someone wants something new. That means opendesigner/state.json exists, or a root DESIGN.md made by OpenDesigner. Common requests: a new component, a new theme or platform, a token tweak, zooming deeper into an area, or "why is this blue?". The goal is harmony: new work reuses existing values, and every change is recorded. The engine is scripts/engine.py in this skill when it was installed from a release zip. Otherwise use the sibling opendesigner skill's scripts/engine.py. Run it from the project root; state lives in ./opendesigner/. Stage files, zoom levels, rules, the glossary and the Decision Cards live in /references/. Talk the way rules.md says: one idea per message, plain words first, and the person's profile.voice. The opendesigner skill's binding rules hold here too, in every round and after a context reset: tokens only; one question per call; show every round; every change ends with engine.py review and a re-read of DESIGN.md; owner corrections go to engine.py feedback " " --kind note. 1. Run engine.py status. It prints the Now line from opendesigner/PROTOCOL.md: the step, what waits for the owner and

This is an excerpt. Refer to the complete source and its current requirements.