init-repo
Initialize a git repository with spec-kit and beads configuration.
What this skill does
# Initialize Repository with Spec-Kit and Beads Initialize the current repository with spec-kit (specify) and beads configuration for Claude. ## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). ## Argument Parsing Parse `$ARGUMENTS` for: - `--no-commit` - Initialize without prompting to commit ## Outline ### 1. Check Prerequisites Verify required tools and environment: ```bash git rev-parse --is-inside-work-tree command -v specify command -v bd ``` > [!CAUTION] > - ERROR if not a git repository → Instruct user to run `git init` first > - ERROR if `specify` not found → Instruct user to install spec-kit > - ERROR if `bd` not found → Instruct user to install beads ### 2. Initialize Spec-Kit Determine the shell script type based on platform: - **macOS/Linux/WSL2** (`uname` returns Darwin or Linux): use `--script sh` - **Windows** (no uname or returns Windows): use `--script ps` ```bash # macOS/Linux specify init . --ai claude --script sh --force # Windows specify init . --ai claude --script ps --force ``` > [!NOTE] > This command requires network access. If sandbox blocks it, retry with sandbox disabled. ### 3. Initialize Beads ```bash bd init --quiet ``` Next, check if `CLAUDE.md` exists in the repository root: - **If `CLAUDE.md` does NOT exist**: run `bd setup claude --output CLAUDE.md` - **If `CLAUDE.md` exists**: STOP and ask the user what they want to do (e.g., overwrite, pick a different filename, or skip). Do NOT proceed until the user responds. ### 4. Report and Prompt for Commit Report what was set up: ``` Repository initialized with spec-kit and beads. Files created/modified: - .specify/ (spec-kit configuration) - .beads/ (beads configuration) - CLAUDE.md (beads workflow instructions) Close and re-open claude to start using spec-kit and beads. ``` Unless `--no-commit` was specified, ask the user if they want to commit these changes. If yes: ```bash git add -A git commit -m "Initialize spec-kit and beads" ``` ## Error Handling - If prerequisite checks fail, stop and report clearly - If `specify init` fails due to sandbox, instruct to retry with sandbox disabled - If commit fails with "nothing to commit", repo was likely already initialized
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.