onboarding

Included with Lifetime

$97 forever

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.

General

What this skill does

# Project Onboarding

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.

## Workflow

Execute all steps below. Run independent steps in parallel where possible.

### Step 1: Read Project Instructions (MANDATORY)

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:
- Tech stack and language versions
- Project conventions and rules
- Directory structure
- What tools and validators are used

Follow the instructions and rules found in these files during this session.

### Step 2: Gather State (run in parallel)

Execute these four checks concurrently:

**2a. Git Status**
Run `git status` to identify:
- Current branch
- Uncommitted changes (staged and unstaged)
- Untracked files
- Whether the branch is ahead/behind remote

**2b. Recent Git History**
Run `git log --oneline --date=short --format="%h %ad %s" -15` to see:
- What was worked on recently
- When the last commits were made
- Whether there are work-in-progress commits

**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:
- How to run tests (`just test`, `just ci`, etc.)
- How to run the project (`just run`)
- Available quality gates and CI recipes
- Any project-specific commands

### Step 3: Synthesize and Brief

Present a concise status briefing covering:

1. **Project** — What this project is, tech stack, key conventions
2. **Current state** — Branch, uncommitted work, last activity date
3. **Recent activity** — Summary of recent commits (not a raw log dump)
4. **Open work** — Ready issues and any in-progress items
5. **Build commands** — How to run tests and CI
6. **Suggested next steps** — Based on open issues, uncommitted work, or recent activity, suggest what to tackle

### Presentation Rules

- Keep the briefing concise — one short paragraph per section, not walls of text
- Lead with what matters: uncommitted work and in-progress issues take priority
- If there is uncommitted work or in-progress issues, call that out prominently
- Do not dump raw command output — synthesize it into human-readable summaries
- End with a clear question: "What would you like to work on?"

Files: 1

Size: 3.3 KB

Complexity: 14/100

Category: General

Source: https://github.com/florianbuetow/claude-code/tree/main/plugins/onboarding/skills/onboarding

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts