Creovator · creator.skill

简体中文

Help your coding agent understand the project, finish the task, and carry the right knowledge into the next session.

Creovator is a project workflow for Codex and Claude Code. Describe the result you want; the agent uses your existing requirements, design conventions, and release practices to choose the work and verification that fit.

• Less re-explaining. Explicit project decisions become part of the relevant project documents, with their scope and source.
• Work that fits the task. A small fix stays small. Independent work can be delegated; consequential changes receive independent review.
• Continuity you can inspect. Current work, retired requirements, and verification evidence stay distinguishable when a new session takes over.

For example:

AIWorker was removed from this product. Retire its unfinished verification tasks and update the current project notes. Keep the historical evidence. Also keep our design rule: settings changes use an inline save action.

The expected outcome is an updated current plan and design guidance. The removed feature's historical tests do not become today's work again. See the illustrative walkthrough.

Install 1.7.0

Download creator-workflow.zip and creator-gateway.zip from release 1.7.0. Extract the gateway ZIP into a creator-gateway directory next to the workflow ZIP. The gateway directory should directly contain SKILL.md and scripts/.

From that download directory, with Python 3.10+ available:

python creator-gateway/scripts/install_workflow.py --root "C:/path/to/your-project" --package "creator-workflow.zip"

Read the proposed changes, then apply the same operation:

python creator-gateway/scripts/install_workflow.py --root "C:/path/to/your-project" --package "creator-workflow.zip" --apply

The project directory must already exist. The installer previews by default and stops on unresolved customization conflicts. To upgrade from 1.6.0, download both new ZIPs and use the 1.7.0 gateway installer: the old installer can mistake Windows Git line-ending conversion for customization. A valid installation receipt supplies ownership without an old baseline ZIP; a 1.5 upgrade still needs its matching old official ZIP. See the quickstart for upgrades, Claude compatibility, and the optional personal gateway skill.

Start a new agent session in the project and try:

Read this project's current context and conventions. Add a CSV export to the existing results page using its current permissions. Make the normal implementation choices, ask me only about unresolved user experience or authorization boundaries, and show how you verified the result.

For an existing project, you can also request documentation alignment:

Align the existing project documents with this workflow. Reuse the current entry document, preserve history, and distinguish current requirements from retired work.

Design adaptation

The 1.7.0 gateway includes a scenario reference library and an adaptation task: create project-specific design rules or fill gaps in existing ones while preserving local choices. Everyday UI work reads only the adopted project rules and their relevant local references. The library ships with the gateway, not the project workflow.

See the usage guide for new and existing projects. Installation and design adaptation are separate operations; upgrading the workflow does not rewrite project design documents.

What is included

The release includes one creator-workflow.zip for project installation and one creator-gateway.zip containing the installer and optional personal skill. Both hosts share AGENTS.md and the canonical skills under .agents/skills/. Claude uses thin discovery adapters under .claude/skills/; there is no second translated policy tree or generated CLAUDE.md.

Public setup and examples are available in English and Chinese. The agent follows your conversation language and the language of existing project documents. The rules have one canonical source; bilingual documentation does not create two competing sets of instructions.

Scope and evidence

Creovator supplies instructions, project knowledge practices, and local checking/install tools. It depends on the host agent's available tools and permissions. Installing files does not prove that a host has loaded them or that a real task will succeed.

The walkthrough is illustrative. Current validation and remaining host or behavior gaps are reported in project status; no adoption figures or productivity gains are claimed. Publishing, deploying, or changing another project requires the corresponding user authorization.

MIT License