website-team-setuplisted

Turn a one-owner new-website repo into one several people and AI assistants (Codex, Claude Code) can work on at once without overwriting each other: invite collaborators, set the repo settings, prove the CI workflow starts on its own (the fix for a silent one is bundled), block direct pushes to `main`, connect Cloudflare Pages to GitHub without the known traps, write rights, merge rule and who publishes live into `AGENTS.md`, hand the team a one-page guide. Run once, when a second person joins. Use it whenever the user mentions a colleague, client or second assistant joining a site repo, inviting someone to GitHub, "Update branch", pull requests not running CI, or connecting Cloudflare to the repo, even without the word "team". Trigger phrases: "set up the team", "my colleague will work on the site", "invite a collaborator", "block pushes to main", "CI is not running on pull requests".
karero/website-builder · ★ 4 · AI & Automation · score 74

Install: claude install-skill karero/website-builder

# Website team setup — from one owner to a team, once `new-website` scaffolds every site with an `AGENTS.md` (the working rules: fetch the latest state first, pull request instead of a direct push, when a merge is allowed, never invent facts, the new-page checklist) and a `CLAUDE.md` that imports it. Those rules already work for one person. This skill does the part that only a **team** needs, in the order we had to do it on a real site, with the traps we hit written in. > **Human-in-the-loop.** Inviting people, accepting invitations, the Cloudflare > dashboard, and any plan-dependent GitHub setting are the owner's clicks. You draft > every value and run every command that `gh` can run; you never handle the owner's > credentials or 2FA, and never drive a dashboard through blind screen control. > **Language.** Talk to the owner in their language. The files stay English unless the > owner's language is another one; then translate `AGENTS.md` and `TEAM-GUIDE.md` > in-session (rules and commands intact), as `new-website` does for `PUBLISHING.md`. Prerequisites: the site is on GitHub with `.github/workflows/ci.yml` from the kit, and `AGENTS.md` exists. If it does not (a site scaffolded before the template existed), copy `new-website/templates/AGENTS.md` + `templates/CLAUDE.md` in first and fill the `[BRACKET]` slots per the note at its top, then continue here. Work on a branch and finish with a pull request — the rule the setup installs applies to the setup itself. Say in the