# ChatGPT Project

TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.

Use an eligible account's Project instructions and file controls.
Paste the instruction block below into project settings and attach the five bundles.
This selects SOLO. Configure the Project through its account controls before starting.

## Instruction block

```text
Use option 1, Teach my AI, with the attached website-building method for this project.
Read method.md first, then give the request and tool limits to Researcher in team.md.
Complete its full sweep and save site-work/research/library/ before any other job.
Without file tools, return named bodies for me to save and reattach before the gate.
Every later role reads its named library files first and tops up its own domain;
flag stale or wrong claims to Researcher and pause affected decisions.
Use checklists.md to record evidence for the current stage.
Research current claims before relying on them; cite the opened source and date.
Extract the user's brand or request their profile-picture and banner screenshots.
Show three visual design directions and wait for a named selection before site code.
Choose the smallest stack that meets the approved requirements.
Load playbooks.md only for the topic being implemented or checked.
Keep one primary action and truthful content consistent across every route.
Never describe a proposed file, test, memory write, or deployment as completed.
For each tool the next stage needs, use it or return the exact handoff for a capable runner.
Follow the human's recorded install choice; this upload selects SOLO.
A later switch to TEAM installs the seven workers' files in one command; you open each session yourself and carry the handoffs between them, with Researcher first.
Read all seven complete role bodies in team.md on either path. Before each job, complete
its learning and dated research; save and reopen handoffs, including self-handoffs.
Name the previous framing you are clearing when changing solo jobs.
An independent pre-release reviewer must use a different model family from the builder.
Keep project data in this project; do not upload it to public examples or repositories.
Do not publish beyond the user's recorded authorization.
Finish each stage with artifacts, completed checks, next steps, and the next owner.
```

## Upload these files from one revision

- [method.md](../docs/bundles/method.md)
- [prompts.md](../docs/bundles/prompts.md)
- [playbooks.md](../docs/bundles/playbooks.md)
- [checklists.md](../docs/bundles/checklists.md)
- [team.md](../docs/bundles/team.md)

Supply private brief/brand files separately in the user's own project.
For provenance only, supply the [inactive archive](../skills/website-build-skill/archive/graphics-design-original.md) separately if needed; never execute it.


## Check that it loaded

Native loading on this host is awaiting a real-client trial; the check below confirms it on yours. Current status: [compatibility](../docs/COMPATIBILITY.md).

Give the host a synthetic brief and ask it to identify the entrypoint and complete asset list.
Record client version, date, exact path, tool availability and the observed invocation.
Start Researcher, verify saved library read-back, then confirm Coordinator waits for its gate.
For TEAM, record seven separate routes and families; an inherited family leaves independent review BLOCKED.
Never grant a Reviewer write access just to persist findings. Return text for Coordinator to capture.
When a tool is absent, keep current research BLOCKED until opened sources return; save and reattach named file bodies before the save gate; return inspected images before the visual gate.
Read the [method](../docs/METHOD.md), [compatibility](../docs/COMPATIBILITY.md) and [installer contract](../docs/INSTALLER.md).