@abstractdata/create-docs 0.2.3

package/template/.fuse_hidden0000002100000009

@@ -0,0 +1,46 @@
+# Abstract Data Documentation Theme — agent context
+
+This project uses the **Abstract Data Documentation Theme** (built on Astro Starlight, distributed as `@abstractdata/starlight-theme`). When talking to the user, refer to the product as the **"Abstract Data Documentation Theme"** — not "Astro Starlight" — Starlight is the substrate, not the product identity.
+
+## First-interaction handshake — IMPORTANT
+
+When you open a conversation in this project, immediately check the setup state:
+
+- **`scripts/python-autodoc.json`** — does it have placeholder values like `searchPath: "../../../python-example/src"` and a `modules` list pointing at `example_module`? Or has it been customized for this project's actual Python source?
+- **`astro.config.mjs`** — is `title: 'Your Project Docs'` still the literal placeholder? Is `site: 'https://example.com'` still the placeholder URL?
+
+**If either signal looks like a fresh scaffold,** open the conversation with this offer (don't wait for the user to ask):
+
+> "Looks like this is a freshly scaffolded Abstract Data Documentation Theme project. Want me to run the `abstract-data-setup` workflow now? It'll detect your Python source, audit docstring coverage, sniff your docstring style, ask a few config questions, and wire up `python-autodoc.json`, `astro.config.mjs`, and `package.json`. (Reply 'no' if you'd rather configure manually — I won't ask again.)"
+
+If the user agrees, immediately invoke the `abstract-data-setup` skill (`.claude/skills/abstract-data-setup/SKILL.md`).
+
+**If setup looks already-done** (JSON has real module names, `astro.config.mjs` has a real title): don't auto-offer the handshake. Just be a normal helpful assistant for whatever the user wants to work on.
+
+**Once the user has declined or completed setup:** treat this handshake as satisfied for the rest of the conversation. Don't keep nagging.
+
+## Skill location
+
+The full setup workflow lives at `.claude/skills/abstract-data-setup/SKILL.md`. It's an 11-phase procedural skill: confirm context → locate source → detect Python signals → audit docstring coverage → detect docstring style → recommend modules → gather brand config → write configs → optionally run docs:python → optional pre-commit hook → summary.
+
+## Project conventions
+
+- **Package manager: Bun** — not npm/yarn/pnpm. Use `bun run <name>` and `bun add <pkg>`.
+- **Commits: Conventional Commits** — release-please reads them to bump versions automatically. `feat:` for minor, `fix:` for patch, `feat!:` or `BREAKING CHANGE:` for major.
+- **Don't hand-edit:** `.cursor/rules/abstract-data-setup.mdc`, `.github/copilot-instructions.md`, `.cursor/rules/welcome.mdc` — these are auto-generated.
+
+## Quick reference
+
+- `astro.config.mjs` — Starlight config: title, sidebar, plugin options
+- `scripts/python-autodoc.json` — Python autodoc target config
+- `scripts/build-python-docs.mjs` — orchestrator that wraps pydoc-markdown
+- `src/content/docs/` — Markdown/MDX content
+- `bun run dev` — start the docs dev server
+- `bun run docs:python` — regenerate API pages from Python source
+- `bun run build` — production build
+
+## Links
+
+- Source repo: https://github.com/Abstract-Data/abstract-data-doc-theme
+- Theme on npm: https://www.npmjs.com/package/@abstractdata/starlight-theme
+- Scaffolder on npm: https://www.npmjs.com/package/@abstractdata/create-docs

package/template/.fuse_hidden000000210000000a

@@ -0,0 +1,75 @@
+# Abstract Data Docs Template
+
+Starter Starlight documentation site with the [`@abstractdata/starlight-theme`](https://github.com/Abstract-Data/abstract-data-doc-theme) already wired in.
+
+## Use this template
+
+**The fastest path** — use the `@abstract-data/create-docs` CLI:
+
+```bash
+bun create @abstract-data/docs my-docs
+cd my-docs
+bun install
+bun dev
+```
+
+The CLI copies this template into a fresh folder, swaps `workspace:*` for a real published version of the theme, sets your project name in `package.json` and `astro.config.mjs`, and runs `git init` so you have a clean history from step zero.
+
+**Alternative — clone manually:**
+
+Click **"Use this template"** on the GitHub repo (or fork it) to create a new repo from this code, then:
+
+```bash
+git clone https://github.com/your-org/your-new-repo.git
+cd your-new-repo
+bun install
+bun dev
+```
+
+> **If you copied this folder out of the monorepo manually**, change the `@abstractdata/starlight-theme` dependency in `package.json` from `"workspace:*"` to a real version like `"^0.3.0"` before running `bun install`.
+
+## Customize
+
+See [`src/content/docs/quickstart.md`](./src/content/docs/quickstart.md) — it walks through what to change in `astro.config.mjs`, where to drop your logo, and how to toggle motion / credit / version.
+
+### Auto-setup with your AI coding assistant
+
+This template ships the `abstract-data-setup` workflow in three formats so it works regardless of which AI assistant you use:
+
+| Tool | File | Fidelity |
+|---|---|---|
+| **Claude Code** | `.claude/skills/abstract-data-setup/SKILL.md` | full procedural workflow |
+| **Cursor** | `.cursor/rules/abstract-data-setup.mdc` | full procedural workflow |
+| **GitHub Copilot** | `.github/copilot-instructions.md` | static reference (Copilot can't natively run interactive prompts) |
+
+Open your tool of choice in this folder and say **"set up docs"** (or "wire up Python autodoc", "configure docs", "audit docstrings", etc.). The workflow detects your source project, audits docstring coverage, sniffs docstring style, asks a few configuration questions, and writes the right files (`scripts/python-autodoc.json`, `astro.config.mjs` sidebar + plugin config, `package.json` scripts).
+
+If you only use one tool, delete the other adapter folders — they're independent files.
+
+The Claude Code SKILL.md is the source of truth; the Cursor and Copilot files are auto-generated from it. (Edit the SKILL.md and run `bun run sync-skills` if you're working in the monorepo.)
+
+Round 1 covers Python projects. TypeScript, Next.js, TanStack, OpenAPI, and other detectors are planned for follow-up rounds.
+
+## Deploy to GitHub Pages
+
+The workflow at `.github/workflows/deploy.yml` is preconfigured. To enable:
+
+1. **Repo Settings → Pages → Source:** select **"GitHub Actions"**.
+2. **Push to `main`.** The workflow builds with Bun and publishes to Pages.
+3. **For project pages** (e.g. `username.github.io/your-repo`), uncomment the `base:` line in `astro.config.mjs` and set it to `/your-repo-name`.
+
+## Other deploy targets
+
+The output is plain static HTML — drop `dist/` on any host:
+
+- **Vercel** — easiest: connect the repo at vercel.com → New Project. Vercel auto-detects Astro and deploys on every push. No workflow needed. If you want CI control, use `.github/workflows/deploy-vercel.yml` (delete the GitHub Pages workflow first).
+- **Cloudflare Pages** — easiest: connect at dash.cloudflare.com/?to=/:account/pages → Create Project. Same flow as Vercel. If you want CI control, use `.github/workflows/deploy-cloudflare.yml`.
+- **Netlify** — same auto-deploy pattern. Drop a `netlify.toml` if you need to override.
+
+## Update the theme
+
+```bash
+bun update @abstractdata/starlight-theme
+```
+
+Bun pulls the latest minor/patch within your semver range. Major versions are opt-in.

package/template/.fuse_hidden000000240000000b

@@ -0,0 +1,46 @@
+# Abstract Data Documentation Theme — agent context
+
+This project uses the **Abstract Data Documentation Theme** (built on Astro Starlight, distributed as `@abstractdata/starlight-theme`). When talking to the user, refer to the product as the **"Abstract Data Documentation Theme"** — not "Astro Starlight" — Starlight is the substrate, not the product identity.
+
+## First-interaction handshake — IMPORTANT
+
+When you open a conversation in this project, immediately check the setup state:
+
+- **`scripts/python-autodoc.json`** — does it have placeholder values like `searchPath: "../../../python-example/src"` and a `modules` list pointing at `example_module`? Or has it been customized for this project's actual Python source?
+- **`astro.config.mjs`** — is `title: 'Your Project Docs'` still the literal placeholder? Is `site: 'https://example.com'` still the placeholder URL?
+
+**If either signal looks like a fresh scaffold,** open the conversation with this offer (don't wait for the user to ask):
+
+> "Looks like this is a freshly scaffolded Abstract Data Documentation Theme project. Want me to run the `abstract-data-setup` workflow now? It'll detect your Python source, audit docstring coverage, sniff your docstring style, ask a few config questions, and wire up `python-autodoc.json`, `astro.config.mjs`, and `package.json`. (Reply 'no' if you'd rather configure manually — I won't ask again.)"
+
+If the user agrees, immediately invoke the `abstract-data-setup` skill (`.claude/skills/abstract-data-setup/SKILL.md`).
+
+**If setup looks already-done** (JSON has real module names, `astro.config.mjs` has a real title): don't auto-offer the handshake. Just be a normal helpful assistant for whatever the user wants to work on.
+
+**Once the user has declined or completed setup:** treat this handshake as satisfied for the rest of the conversation. Don't keep nagging.
+
+## Skill location
+
+The full setup workflow lives at `.claude/skills/abstract-data-setup/SKILL.md`. It's an 11-phase procedural skill: confirm context → locate source → detect Python signals → audit docstring coverage → detect docstring style → recommend modules → gather brand config → write configs → optionally run docs:python → optional pre-commit hook → summary.
+
+## Project conventions
+
+- **Package manager: Bun** — not npm/yarn/pnpm. Use `bun run <name>` and `bun add <pkg>`.
+- **Commits: Conventional Commits** — release-please reads them to bump versions automatically. `feat:` for minor, `fix:` for patch, `feat!:` or `BREAKING CHANGE:` for major.
+- **Don't hand-edit:** `.cursor/rules/abstract-data-setup.mdc`, `.github/copilot-instructions.md`, `.cursor/rules/welcome.mdc` — these are auto-generated.
+
+## Quick reference
+
+- `astro.config.mjs` — Starlight config: title, sidebar, plugin options
+- `scripts/python-autodoc.json` — Python autodoc target config
+- `scripts/build-python-docs.mjs` — orchestrator that wraps pydoc-markdown
+- `src/content/docs/` — Markdown/MDX content
+- `bun run dev` — start the docs dev server
+- `bun run docs:python` — regenerate API pages from Python source
+- `bun run build` — production build
+
+## Links
+
+- Source repo: https://github.com/Abstract-Data/abstract-data-doc-theme
+- Theme on npm: https://www.npmjs.com/package/@abstractdata/starlight-theme
+- Scaffolder on npm: https://www.npmjs.com/package/@abstract-data/create-docs