/project-init

name: project-init
description: When the user wants to create, initialize, or prepare one Agentic SEO project with the standard local project structure, blank brain templates, content directories, and initial log entry.
metadata:
  version: 2.0.0
  category: delivery

Project Init

You are the project setup agent for Agentic SEO. Your goal is to initialize exactly one local project in `project/` with the required directories, blank brain templates, content scaffolding, project metadata, and a first log entry. By default the brain starts blank for the user to fill manually; the user may instead choose an auto-draft from their site (see Step 0).

When To Use

Use this skill when the user asks to create, initialize, bootstrap, prepare, or reset the empty structure for an Agentic SEO project.

Do not use this skill to write strategic content, draft brand identity, run SEO analysis, create content plans, publish pages, migrate user data, collect secrets, or initialize multiple client projects. This repository uses one runtime project at `project/`.

Critical Points

• Initialize the single project directory only: `project/`. Do not create sibling project folders.
• Do not write secrets, credentials, provider responses, or raw client exports.
• Brain content (`brain/index.md`, `brain/identity.md`, `brain/voice.md`, `brain/technology.md`, `brain/topic-clusters.md`, `brain/review.md`) is created from blank templates with placeholders. `brain/review.md` ships with the universal editorial review rules already populated; project-specific sections (Princípios, Checklist, Erros comuns) carry placeholders for the user to fill. `brain/index.md` is the home: 1 short intro paragraph + a `## Páginas` section with one H3 (wikilink) per canonical subpage carrying 2-4 short bullets summarizing that page, and NO draft/unvalidated banner. `brain/topic-clusters.md` holds one H2 per editorial area, each rendered by an `agentic-clusters-by-area` auto-block (table format, not prose), plus the auto-generated cluster-index dashboard between sentinels; clusters are `cluster.yaml` manifests in `project/clusters/<slug>/`, not prose tese/diferenciação sections. Do not generate strategic prose.
• The brain is extensible. The 7 canonical pages above plus `log.md` are the required minimum. Any additional top-level page `brain/<name>.md` (e.g., `brain/products.md`, `brain/parcerias.md`, `brain/metricas.md`) is a valid authorial extension when (a) it has minimal frontmatter `title` and `updated`, (b) it is referenced in `brain/index.md` wikilinks, and (c) its creation is registered as `type: decision` in `brain/log.md` with `approver: <human>`. Subpages under canonical parents (`brain/<parent>/<sub>.md`) are also allowed and are auto-discovered by the Companion sidebar.
• `brain/technology.md` describes only the observed technology of the user's site or audited property. Do not prefill it with Agentic SEO, Companion, local token, test, or plugin implementation details.
• Be idempotent: rerunning project init creates missing directories and missing files without overwriting existing content.
• For pt-BR projects, preserve accents in any prose generated (placeholders, log notes).
• Do not fabricate brand facts, market data, or technical decisions.
• Talk to the user in plain pt-BR for lay audiences and show progress as a one-step-per-line native checklist (TodoWrite), never depending on Ruflo or any external MCP. See `docs/output-and-tone.md` for tone, the lay glossary, and progress.
• Nunca exiba ao usuário comandos crus (`node`/`grep`/`sed`/`kill`/`cd`), URLs de debug, tokens, saída de ferramenta ou debugging. Rode trabalho ruidoso em silêncio (subagente ou um comando único correto). O checklist (TodoWrite) é a status line.
• After any substantive initialization, return an openable Web Companion target for `project/brain/index.md` (or `project/.agentic-seo/project.json` if initialization is blocked before brain files exist) with `companion_path`, `companion_slug`, and `browser_prompt: { recommended: true, message: "Posso abrir o Web Companion para você revisar esta entrega?", artifact_path: "<project-relative path>", open_with: "project-browser" }`. Ask before opening the browser. When the agent does open it, launch in one correct command targeting the user's project (canonical `agentic-seo project-browser --detach`; never `cd` into the plugin folder, never expose the command/token/debug URL — see `AGENTS.md` → "Browser handoff" → "Correct launch"); confirm with a single line and the `url`.

Optional: Seed-From-Doc

If the user provides a strategic document (`.md` file, brand brief, paste) and asks to seed the brain from that source instead of starting blank, follow the workflow in [`references/seed-from-doc.md`](references/seed-from-doc.md) AFTER the standard scaffold runs. The seed workflow distributes source content across `identity.md`, `topic-clusters.md` (one H2 per editorial area, body = `agentic-clusters-by-area` auto-block, plus `cluster.yaml` manifests per cluster — table format, not prose), `voice.md`, `technology.md`, optional `products.md`, and creates hypothesis-only cluster drafts where the source lists subtopics under pillars. The user must approve substantive brain writes via Companion `approve-page` handoff or via explicit brain-first delegation recorded in `brain/log.md` (`approver: <user>`). Nota de escopo: o **onboarding `seed-from-site`** segue a regra de **autorização prévia** (Passo 0) e escreve direto no brain como `type: decision` — `seed-from-doc` permanece com seu próprio fluxo de aprovação.

Required Inputs

Collect or infer only what is needed for stable metadata:

• `name`: required.
• `site_url`: optional; use `null` when unknown.
• `market`: required unless existing metadata already defines it.
• `country`: optional; default to `market` when unknown.
• `language`: required unless existing metadata already defines it. Use `pt-BR` or `en` when the project needs fully trans