opendesigner

原文涵盖的主题

• OpenDesigner
• Binding rules
• What it does
• Guardrails
• When to use which skill
• Files in this skill
• Start
• The flow: zoom, don't march

They hold in every round, after a context reset and in a new session. engine.py is /scripts/engine.py, in this skill's folder. 1. Tokens only. Every colour, size, space, radius, shadow and duration comes from opendesigner/tokens/ or opendesigner/build/. A value the system lacks becomes engine.py set --why "...", never a literal. 2. One question per call. One per message, and one per call of a question tool, even one that takes four. The log question goes alone, first. 3. Show every round without being asked: screenshots at desktop and phone, or an artifact, before and after, with each check and its result. Never only a local link. 4. Every implementation ends with engine.py review, then a re-read of DESIGN.md. Fix what it reports before the next draft. 5. Owner corrections go to engine.py feedback " " --kind note. Said twice, a note is a rule in opendesigner/RULES.md. 6. Each round starts by reading opendesigner/PROTOCOL.md, opendesigner/RULES.md and DESIGN.md. After a context reset or in a new session, run engine.py status first: the step, what waits for the owner, the next command. 7. Ask once about the hand-off. After the first result, in its own message: shall I write the note

这里只展示节选，请以完整原文和当前要求为准。