Fast org bootstrap

Fast path for forge identity and public surface: GitHub org About, logo, public .github profile, website, one docs hub, news vs blog split, then optional transfers. It does not replace the capability-area pages (email, vault, scheduling, design, chat, funding, org infra). Use those when the session reaches mail, secrets, or DNS-as-code.

Cursor skill (named SDL profile, or profile pasted in the prompt)

skills/bootstrap-org (~/.cursor/skills/bootstrap-org/ when installed)

House site/docs defaults (overridable per profile): SolidStart static + solid-ui, pnpm, Antora + Valentus v2, GitHub Pages, Cloudflare DNS-only in front of github.io.

Named profiles

Pass a name, @-mention a .sdl file, or paste a profile "…" { } block. Catalog: profiles/catalog.sdl. Public selector: https://devcentr.org/skills/?cat=bootstrap.

Name Typical job

oss-collective

OSS GitHub org hub + docs; skip mail/infra

product-org

Company hub + docs; email/infra when a domain exists

nonprofit

Public-good hub + optional donate/sponsors ask

web-app

Standalone SolidStart product site (Netlify overlay if login)

library

Publishable library; docs into the org hub; optional marketing site

cli

Command-line tool (--version / --help); optional marketing site

desktop

Tauri + solid-ui GUI; Band A Product Essentials

docs-hub

Docs as the public face; marketing site optional stub

forks-org

Supplemental/splinter org; license first; thin hub

If the first prompt names a profile, attaches .sdl, or pastes a profile "…" { } block, the agent loads it and only polls leftovers. Implied jobs (new CLI, Tauri app) map to the catalog. If none of those apply, it asks before scaffolding.

When to use this instead of walking the hub

Use this tutorial / skill when the job is “make this org look real on GitHub and the web.” Walk Business Bootstrap capability areas when the job is inboxes, vaults, chat, funding, or Pulumi infra.

A new org pays off when there is a name that belongs on a landing page, a handful of projects that belong under that banner, and a reason outsiders follow the org rather than a person. Otherwise keep the work on a personal account.

Goal

An org that is not vacant: Settings filled, avatar ready, public profile README, and (if in scope) a site + docs hub whose copy is written for visitors.

Steps

These match the skill phases. Skip anything the org does not need yet (no domain → no custom CNAME; no mail → stop before email lanes).

  1. Pick a named SDL profile (oss-collective, cli, desktop, …) — or pass/paste one in the first prompt. Confirm split and partners (org) or owner/repo (project).

  2. Fill org identity with gh (display name, description, website = public site, not docs). The empty org is often created in the GitHub UI first.

  3. Design or copy a mark; export a 256×256 PNG for Settings → General (upload is UI-bound).

  4. Create public {org}/.github with profile/README.md (Markdown). Do not put the profile in the repo root. Skip .github-private unless member-only text actually differs.

  5. Public site: {org}.github.io until a custom domain is bought and verified. Grey-cloud DNS if you CNAME github.io — see GitHub Pages custom domain. Do not invent a second homepage if a canonical site already exists.

  6. One public docs hub per org; product repos contribute docs/ instead of publishing a second docs site.

  7. Split news (dated chronicle) from blog/essays (stance). Do not publish philosophy as a news item or as the GitHub profile.

  8. Transfer candidate repos; update remotes and the personal hub. Remove leftover personal-account stubs.

  9. Only if a domain or repeating DNS exists: email lanes and {org}/infra — start at Bootstrap org email and Org infra repo pattern. Follow Defaults by org stage; do not self-host chat or design on day one.

    Profile recipe (keep it short)

    centered logo; rule; 1–3 pitch lines; no H1 restating the org name; no notable-repo list (GitHub Settings + the site already do that).

Related