onboard-our-stacklisted

Onboard a newcomer to THIS codebase, or answer a targeted "how does our X work" question, by walking curated reading lists and synthesizing the mental model — never by guessing. Works out of the box: if a maintainer has committed .onboard/topics.yaml it uses that curated path; if not, it cold-starts from the repo's own authoritative docs (README, CLAUDE.md / AGENTS.md, ARCHITECTURE.md, docs/, the dependency manifest, the entry point) and is explicit about what curated knowledge is still missing. The newcomer never has to create files, run setup, or change code. Use this for "I'm new, help me understand this project", "where do I start", "onboard me", and for "explain our auth flow", "how does our scheduler work", "walk me through our X". Do NOT use for: generic programming or public-library questions, debugging a specific error or stack trace, or writing/modifying code. This skill teaches an existing system; it does not generate documentation or code, and it does not invent gotchas or assert which files are l
Osipchuk/agent-skills · ★ 5 · AI & Automation · score 78

Install: claude install-skill Osipchuk/agent-skills

# onboard-our-stack Two jobs, one skill: - **Broad onboarding** — "I'm new, help me understand this project." The reader needs a *route through* the system, in order. - **Targeted** — "explain our scheduler." The reader needs *one subsystem*, on demand. Tell them apart from the request: a named subsystem -> targeted; "new", "onboard me", "where do I start", "understand the project" -> broad. The institutional knowledge — which files are load-bearing, in what order, and the gotchas that live only in people's heads — is curated in `.onboard/topics.yaml` by a maintainer, ONCE, and committed. A newcomer just asks; they never author it and never change code to make this skill work. ## Availability ladder — the "works out of the box" guarantee Pick the highest tier the repo supports. Never block the newcomer on setup, and never demand maintainer input from someone who came here to learn. 1. **Curated config present** (`.onboard/topics.yaml` at repo root) -> use it. Best tier: real ordering, real gotchas. See Broad / Targeted below. 2. **No config -> COLD START.** Do NOT refuse, and do NOT drop into config authoring (that is a maintainer-only flow, below). Orient the newcomer from the repo's own authoritative sources, in this order if present: README.md, CLAUDE.md / AGENTS.md, ARCHITECTURE.md, docs/ (a product doc and a runbook if they exist), the dependency manifest (pyproject.toml / requirements.txt), and the entry point (main.py / app). Synthesize a