Creative Agent OS North Star
Use this skill when the work risks drifting away from the intended product shape.
Core test
Before proposing or implementing anything, check:
- Does this stay lightweight?
- Does this help ordinary users, not just agent power users?
- Does this keep the coding engine replaceable?
- Does this fit cloud sandbox execution better than local-only assumptions?
- Does this make adding domain agents easier rather than harder?
Default reference frame
- runtime: learn from Nanobot
- cloud execution: learn from Open Inspect / background-agents
- system shape: learn from OpenClaw
- coding engine: adapter, never hard-coded
Read references/north-star.md when you need the full criteria.
What to do
- call out drift early
- prefer thinner orchestration over heavy frameworking
- separate product shape from engine implementation
- preserve room for multimodal apps, skills, memory, and CLI bridges
Output style
When reviewing a proposal, answer in this order:
- what matches the north star
- what drifts from it
- the smallest correction that gets back on track