prime
Load project context before implementing features or making architectural decisions. Invoke proactively at the start of significant work on any project. Scans CLAUDE.md, README, specs/, docs/, and source structure to build a context summary. Supports optional domain hints to focus on specific areas of the codebase. Use when you need project conventions, architecture understanding, or domain context before coding.
What this skill does
# Prime - Project Context Loader
When this skill is invoked, IMMEDIATELY output the banner below before doing anything else.
Pick ONE tagline at random — vary your choice each time.
CRITICAL: Reproduce the banner EXACTLY character-for-character. The first line of the art has 4 leading spaces — you MUST preserve them.
```
{tagline}
⠀ ██╗██████╗ ██████╗ ██╗███╗ ███╗███████╗
██╔╝██╔══██╗██╔══██╗██║████╗ ████║██╔════╝
██╔╝ ██████╔╝██████╔╝██║██╔████╔██║█████╗
██╔╝ ██╔═══╝ ██╔══██╗██║██║╚██╔╝██║██╔══╝
██╔╝ ██║ ██║ ██║██║██║ ╚═╝ ██║███████╗
╚═╝ ╚═╝ ╚═╝ ╚═╝╚═╝╚═╝ ╚═╝╚══════╝
```
Taglines:
- 🔋 Loading the arsenal...
- 📚 Knowledge is power!
- 📖 Absorbing the sacred texts...
- 📡 Context loading... please stand by!
- 💣 Priming the knowledge cannon!
- 🤓 Time to do my homework!
- 📜 Downloading the lore...
- 🧠 Brain cells: ACTIVATING
---
## Output Formatting
After the banner, display parsed input:
```
┌─ Input ────────────────────────────────────────
│ {Field}: {value}
│ Flags: {parsed flags or "none"}
└────────────────────────────────────────────────
```
Pre-flight results:
```
── Pre-flight ───────────────────────────────────
✅ {dep} {version or "found"}
⚠️ {dep} not found → {fallback detail}
❌ {dep} missing → stopping
──────────────────────────────────────────────────
```
Stage/phase headers: `━━ {N} · {Name} ━━━━━━━━━━━━━━━━━━━━━━━━━`
Status icons: ✅ done · ❌ failed · ⚠️ degraded · ⏳ working · ⏭️ skipped
---
Load project context to inform agent decisions. Raw file contents stay in a
subagent — the primary thread only sees a structured PRIME_REPORT.
## Step 1: Parse Arguments
Extract domain hints from the request (comma-separated). These are directory
names or topic keywords to focus the context scan on. If no domain specified,
load core context only (CLAUDE.md, README, specs/).
## Step 2: Load Context via Subagent
Launch a **general-purpose subagent** to read files and build the report:
```
Task(
subagent_type: "general-purpose",
description: "Load and summarise project context",
prompt: <see below>
)
```
### Subagent Prompt
```
Load project context and return a structured summary. Raw file contents must
NOT appear in the report — summarise only.
Limit PRIME_REPORT to 30 lines maximum.
## Core Files (always load)
1. CLAUDE.md — Project conventions, architecture, instructions
2. README.md — Project overview, setup, usage
3. specs/ — Project specifications and roadmap (scan directory if present)
4. docs/ — Documentation directory (scan if present)
If a file is missing, record as NOT FOUND and continue.
## Domain Files
{For each requested domain hint, use Glob to find relevant files:}
- Search for directories matching the hint name (e.g., "auth" → src/auth/, lib/auth/)
- Search for files matching *{hint}*.md, *{hint}*.yaml, *{hint}*.json
- Read the most relevant matches (max 5 files per domain)
For each file:
- If it exists: read and summarise (2-3 lines max per domain)
- If it doesn't exist: record as NOT FOUND and continue
## Output Format
PRIME_REPORT:
- core_files_loaded: {count}/{total}
- missing_files: {list or "none"}
- domains_loaded: {list}
- per_domain_summary:
- {domain}: {2-3 line summary}
- branch: {current branch from git branch --show-current}
- ready_for: {inferred from loaded context}
```
## Step 3: Present Summary
Parse PRIME_REPORT and present a clean summary to the user:
```
┌─ Prime · Report ───────────────────────────────
│
│ ✅ Context loaded
│
│ 📚 Core: {count}/{total} files loaded
│ 🌐 Branch: {branch}
│
│ 📝 Domains
│ {domain}: {2-3 line summary}
│ {domain}: {2-3 line summary}
│
│ ⚠️ Missing: {list or "none"}
│
│ 🎯 Ready to assist with: {ready_for}
│
└─────────────────────────────────────────────────
```
If CLAUDE.md was missing, warn the user and note that only domain context
was loaded.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce 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).
relationship-science-coach
IncludedUse 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.
building-sf-integrations
IncludedSalesforce 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).
venue-templates
IncludedAccess 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.
let-fate-decide
IncludedDraws 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.
net-ops
IncludedCross-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.