dr-init
Initializes or updates a project with the project-management plugin structure. Creates _claude/ directories and a versioned CLAUDE.md on fresh projects, verifies and updates outdated plugin-managed sections on existing projects, or appends plugin sections to an existing CLAUDE.md. Use when setting up the plugin in a new project or when plugin template sections have been updated.
What this skill does
# Initialize Project-Management Plugin Structure
This skill scaffolds or updates the project-management plugin layout in the current working directory. It operates on **plugin-managed content only** — project-specific documentation (architecture, build commands, etc.) is out of scope. Suggest Claude Code's built-in `/init` to the user for that.
## Phase 1: Detect Project State
Before doing anything else, classify the project into one of three states.
### Read the evidence
Run these checks (parallel where possible):
1. **`Read CLAUDE.md`** — Handle three outcomes:
- File-not-found error → no CLAUDE.md
- File has content → inspect for plugin marker
- File exists but is empty or whitespace-only → treat as no CLAUDE.md
2. **`Glob _claude/**`** — Handle two outcomes:
- Empty result → no `_claude/` directory (or it exists but is empty)
- Non-empty result → `_claude/` directory exists with content
3. **Plugin marker check** — If CLAUDE.md has content, check whether it contains the substring `<!-- Plugin: project-management` near the top of the file
### Classify
| State | CLAUDE.md | `_claude/` | Plugin marker in CLAUDE.md |
|-------|-----------|-----------|---------------------------|
| **A — Fresh** | Missing or empty | Missing | — |
| **B — Already Initialized** | Has content | Present (any content) | Present |
| **C — Uninitialized** | Has content | Missing | Absent |
**Edge cases:**
- CLAUDE.md present with marker, but `_claude/` missing → State B (missing dirs will be backfilled)
- CLAUDE.md missing, `_claude/` present → State A (user likely deleted CLAUDE.md, recreate it)
- Both missing → State A (fresh)
### Route
Load the reference file that corresponds to the detected state:
- **State A** → Read `${CLAUDE_SKILL_DIR}/references/state-a-fresh.md`
- **State B** → Read `${CLAUDE_SKILL_DIR}/references/state-b-update.md`
- **State C** → Read `${CLAUDE_SKILL_DIR}/references/state-c-uninitialized.md`
For background on how plugin-managed section versioning works (relevant mainly to State B), also read `${CLAUDE_SKILL_DIR}/references/section-versioning.md`.
## Phase 2: Execute the State Handler
Follow the loaded reference file's instructions end-to-end. Each reference file covers:
- Pre-flight git safety check (warn if CLAUDE.md has uncommitted changes before any write)
- Any user confirmation needed
- The actual filesystem operations
- The success message to emit
## Phase 3: Summarize
After execution, report a concise completion summary covering:
- Which state was detected (A / B / C)
- What was created, updated, or skipped
- Any follow-up suggestions (e.g., run `/init` for State A, or review the diff for State B)
Keep the summary tight — the reference file's success message is the canonical user-facing output for the detailed breakdown.
## Cross-Platform Notes
This skill uses Claude Code's native tools (`Read`, `Write`, `Edit`, `Glob`) for all filesystem operations, which behave identically on Windows, macOS, and Linux. The only Bash permission is `git status` for the safety check, which is consistent across platforms.
Do not invoke `mkdir`, `touch`, `ls`, `wc`, `test`, or any other shell utility — all have native-tool equivalents documented in the reference files. Always emit paths with forward slashes (works on all three OSes).
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.