Onboarding Templates

Developer onboarding is the highest-leverage application of shared Gemini CLI configuration. A new hire clones the repo, installs Gemini CLI, runs /onboard (a custom command), and gets an interactive walkthrough of the project architecture, key conventions, build processes, and common tasks. The onboarding command reads the GEMINI.md, the directory structure, the test suite, and the CI config, then produces a personalized orientation guide. No more outdated wiki pages. No more "ask Sarah, she knows how the auth system works."

Onboarding templates go beyond project orientation. Create templates for common first tasks: "fix a bug in the API layer" (includes which files to look at, how to run tests, how to submit a PR), "add a new feature" (includes the component template, the test template, the routing pattern), and "review a PR" (includes the team's review checklist and quality standards). These templates encode tribal knowledge into executable workflows that any developer — human or AI — can follow.

[command]
description = "New developer onboarding walkthrough"
prompt = """
You are onboarding a new developer to this project. Walk them through:

1. **Project Overview**: Read GEMINI.md and summarize the project purpose, tech stack, and architecture in 5 sentences.

2. **Directory Structure**: List the top-level directories and explain what each one contains.

3. **Key Files**: Identify the 5 most important files a new developer should read first.

4. **Development Workflow**: Explain how to:
   - Start the dev server
   - Run tests
   - Create a branch and submit a PR
   - Deploy to staging

5. **Common Patterns**: Show 2-3 examples of the project's most common code patterns (component structure, API route, test file).

6. **Gotchas**: List known issues, workarounds, and things that surprise new developers.

Be concise and practical. Skip theory — focus on what they need to be productive today.
"""