Help us improve
Share bugs, ideas, or general feedback.
From team-brain
Generates structured onboarding guide from team brain knowledge base covering project overview, coding conventions, architecture decisions, lessons learned, and contributors.
npx claudepluginhub manavarya09/team-brain --plugin team-brainHow this skill is triggered — by the user, by Claude, or both
Slash command
/team-brain:team-brain-onboardThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a comprehensive onboarding document from all team brain entries.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.
Share bugs, ideas, or general feedback.
Generate a comprehensive onboarding document from all team brain entries.
node "${CLAUDE_SKILL_DIR}/../../scripts/store.js" list
node "${CLAUDE_SKILL_DIR}/../../scripts/store.js" list "" conventions
node "${CLAUDE_SKILL_DIR}/../../scripts/store.js" list "" decisions
node "${CLAUDE_SKILL_DIR}/../../scripts/store.js" list "" lessons
node "${CLAUDE_SKILL_DIR}/../../scripts/store.js" list "" knowledge
Read the full content of key entries using the Read tool on their file paths.
Generate a structured onboarding document with these sections:
# Onboarding Guide
> Auto-generated from Team Brain on DATE
## Project Overview
[Synthesized from knowledge entries]
## Coding Conventions
[All active conventions, clearly stated]
## Architecture Decisions
[Key decisions with brief context on WHY]
## Lessons Learned
[Important gotchas and insights the team has discovered]
## Key Things to Know
[Anything else a new developer should know on day 1]
## Contributors
[Who to ask about what, based on contributor data]