onboarding-companionlisted

Create a newcomer onboarding companion — a "buddy" guide plus a mentor voice — that takes a brand-new joiner, fresh graduate, or non-expert contributor from zero to productive on a software project. Covers setting up, running it end to end, reading the codebase in the right order, working day to day, getting unstuck, and the senior-engineer habits that matter when building with an AI coding agent. Produces Markdown (repo-first, an ONBOARDING.md plus a CONTRIBUTING section). Use this whenever the user wants onboarding docs, a contributor guide, a "getting started for new team members", a buddy guide, developer onboarding, or wants to help someone new start contributing. Use it even if the user only says "help new people get up to speed", "write a guide for new contributors", or "onboard a junior to this repo". This is for contributors, distinct from an end-user usage guide; it is not a multi-audience concepts course (use learning-track).
imrohitagrawal/project-doc-skills · ★ 0 · AI & Automation · score 58

Install: claude install-skill imrohitagrawal/project-doc-skills

# Onboarding Companion Builder Version: 1.1.0 · see `CHANGELOG.md`. Build the **newcomer's companion**: the guide that turns a brand-new joiner into a confident contributor, not just a reader. It has two voices that work together — a patient **buddy** who walks the reader from zero, and a **mentor** who passes on the senior-engineer judgement that keeps a project healthy (especially when building with an AI coding agent). Read `references/house-style.md` first. Default scope is `internal`, so naming the real workflow, tools, and commands is expected and wanted. **Diátaxis mode:** primarily *tutorial* (learning-by-doing), with the mentor section as *explanation*. **This is not the usage guide.** The usage guide is for an end user who wants to *use* the product. This is for a contributor who needs to *work on* it — set it up, read the code, and ship a change safely. --- ## Before you start (inputs, when to run, where it sits) **What this skill needs.** A repository that already **runs end to end** — a real one-command (or near) quickstart — plus the project profile (`assets/project-profile.md`, filled), and knowing where the project keeps its requirements, docs, ADRs/decision log, and conventions. If the project already has an architecture walkthrough, a usage guide, or an operations runbook, link to them from here rather than re-deriving them — this companion points a newcomer at them, it does not replace them. **When to run it in a Claude-Code build.** **Late, not ear