gezhi-project-setup

gezhi Project Setup

Use this skill when a user wants an agent to make an existing project runnable under gezhi, especially when the user can judge the finished thing but does not want to configure the build loop by hand.

Role in the One-Prompt Flow

llms.txt is the public entrypoint and router. This skill is the execution runbook. When an agent arrives from llms.txt, inherit the user-facing contract from that file, then use this skill for the concrete setup decisions:

• inspect the project;
• choose the canonical artifact;
• synthesize or select the producer;
• write gezhi.toml;
• validate the setup;
• report the exact next command.

Do not send the user back to read this skill. The skill is for the agent to execute on the user's behalf.

The deliverable is not just a gezhi.toml. The deliverable is a repeatable thing loop:

stable rebuild -> finished thing -> review -> bounded source work

For a non-expert user, success means they can run one command after setup and understand what artifact to inspect. Do not leave them with a partial config that only works if they already know the build system.

When to Use

• A user asks to "set up gezhi" for a project.
• A user provides a repository and a desired output such as a PDF, site, workbook, report, model metric, or slide deck.
• A user wants an agent to create the rebuild command and gezhi.toml.
• A user has a finished thing they can inspect but does not know the build system.

Do not use this skill for generic task planning, ordinary code review, or a project that has no inspectable thing.

Operating Rules

• Address the user by name if the host profile supplies one.
• Prefer live project evidence over README claims.
• Do not edit raw data, generated outputs, build products, .git/, or .gezhi/ unless the user explicitly asked for that exact operation.
• Ask the user only when the finished thing cannot be inferred safely.
• Keep the producer deterministic, idempotent, and easy to rerun.
• Completion belongs to the rebuilt thing and tik verdict, not to the tok agent's explanation.
• Treat every tok pass as source changes only. Tok must not declare the thing-level goal complete.
• If a command fails, preserve the exact failing command and the relevant output in your final report. Do not describe a setup as ready when validation did not pass.
• Do not edit unrelated README/docs/tests/source while setting up gezhi unless that file is directly required for the producer or goal config.