From onboarding
This skill should be used when starting a new session, resuming work, or when the user asks to "onboard", "get oriented", "catch me up", "what's the state of the project", "what should I work on", or "where did we leave off". Gathers project context by reading instructions, checking git state, reviewing open issues, and identifying next steps.
npx claudepluginhub florianbuetow/claude-code --plugin onboardingThis skill uses the workspace's default tool permissions.
Orient in the current project by gathering context from multiple sources: project instructions, version control state, issue tracker, and build system. Produce a concise status briefing and suggest what to tackle next.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Orient in the current project by gathering context from multiple sources: project instructions, version control state, issue tracker, and build system. Produce a concise status briefing and suggest what to tackle next.
Execute all steps below. Run independent steps in parallel where possible.
You MUST read AGENTS.md, CLAUDE.md, GEMINI.md, and COPILOT.md in the project root. Skip any that don't exist, but read all that do. If a file explicitly instructs you to read another file, read that file too. If both files contain the same content (e.g., one simply redirects to the other), only read it once. When both files exist and their rules conflict, AGENTS.md takes precedence.
Extract from these files:
Follow the instructions and rules found in these files during this session.
Execute these four checks concurrently:
2a. Git Status
Run git status to identify:
2b. Recent Git History
Run git log --oneline --date=short --format="%h %ad %s" -15 to see:
2c. Open Issues
Run bd ready to list issues with no blockers that are ready to work on.
Also run bd list --status=in_progress to check for any claimed but unfinished work.
If beads is not initialized (command fails), skip this step and note that no issue tracker is configured.
2d. Build System
Read the project's justfile (or Makefile if no justfile exists) to identify:
just test, just ci, etc.)just run)Present a concise status briefing covering: