export declare const VISUALIZE_REPO_SKILL_MD = "---\nname: visualize-repo\ndescription: >-\n  Open or create a repo-native visual documentation workspace backed by local\n  Plan MDX files. Use when the user asks to visualize a repository, create\n  durable visual docs for APIs/components/models/flows, launch a visual repo\n  viewer, review repo docs like a visual IDE, or collect Plan comments that\n  should become coding-agent changes.\nmetadata:\n  visibility: exported\n---\n\n# Visualize Repo\n\n`/visualize-repo` opens a local, source-controlled visual documentation layer\nfor a repository. It is for durable repo understanding, not a one-off plan:\ncomponents can have wireframes, APIs can have specs, models can have schema\nviews, and reviewers can comment on those docs before sending work to a coding\nagent.\n\n## Default Command\n\nRun the Agent-Native CLI from the repo root:\n\n```bash\nnpx @agent-native/core@latest visualize-repo --open\n```\n\nUseful variants:\n\n```bash\nnpx @agent-native/core@latest visualize-repo init\nnpx @agent-native/core@latest visualize-repo --target actions --target server/db/schema.ts\nnpx @agent-native/core@latest visualize-repo check\nnpx @agent-native/core@latest visualize-repo verify\nnpx @agent-native/core@latest visualize-repo --no-open\n```\n\nThe command writes or updates `agent-native.json` with an\n`apps.visualize-repo` local-files section, creates a starter MDX folder at\n`.agent-native/visual-docs/repo-overview`, then serves it through the Plan\nlocal bridge. The hosted Plan UI can render the review surface, but the plan\nsource stays in local files and bridge comments stay in `comments.json`.\n\n## When There Is No Manifest\n\nIf `agent-native.json` does not exist, let the CLI bootstrap one. It scans for\nhigh-value starting points such as `actions/`, `app/components/`,\n`app/pages/`, `server/db/schema.ts`, `src/`, `packages/`, `templates/`,\n`docs/`, and `content/`. Keep the first run targeted. Prefer 5-20 visualized\nnodes over a generated wall of repo prose.\n\nUse explicit targets when the user already knows the important surface:\n\n```bash\nnpx @agent-native/core@latest visualize-repo \\\n  --target actions/webhooks.ts \\\n  --target server/db/schema.ts \\\n  --target app/components/PromptComposer.tsx\n```\n\n## Agent Workflow\n\n1. Inspect `agent-native.json` and the generated `plan.mdx`.\n2. Read the source anchors listed for each target before changing the visual\n   docs.\n3. Add only the visual blocks that earn their keep: `api-endpoint` for stable\n   APIs, `data-model` for durable schema, `wireframe` for user-facing\n   components/flows, `diagram` for architecture, and `annotated-code` for\n   load-bearing implementation.\n4. Run `npx @agent-native/core@latest visualize-repo check` after editing MDX.\n5. Use `verify` before handoff when renderer correctness matters.\n\nWhen acting on comments, treat local `comments.json` as the feedback inbox.\nAgent-targeted comments should become code changes plus matching MDX updates so\nthe visual docs and executable code stay in sync.\n\n## Privacy Boundary\n\n`visualize-repo check` is local/offline lint. `visualize-repo --open` starts a\nlocalhost bridge and opens the Plan UI against local files; it does not publish\nthe plan to hosted storage and performs no hosted Plan database writes.\n`visualize-repo verify` may send the MDX folder to the Plan app's public\nvalidation action so the real renderer schema can check it. For no hosted\ncontent egress, pass `--app-url` pointing at a local Plan app or skip\n`verify` and rely on `check`.\n\nDo not call hosted Plan write tools for this workflow unless the user explicitly\nasks to publish or share the docs. Avoid `create-visual-plan`,\n`update-visual-plan`, `import-visual-plan-source`, `patch-visual-plan-source`,\nand `get-plan-feedback` for local repo docs; edit the MDX files directly and\nuse the local bridge.\n";
//# sourceMappingURL=visualize-repo-skill.d.ts.map