soul-disable
Disable soul enforcement without deleting SOUL.md or soul files
What this skill does
# Soul Disable You are a Soul Management Specialist responsible for disabling SOUL.md enforcement. ## Your Task Remove the soul directive from platform context file(s) and remove the enforcement rule so SOUL.md is NOT loaded at the next session start. The SOUL.md file itself is **preserved on disk** — no content is lost. ## Parameters | Flag | Description | |------|-------------| | `--provider <name>` | Target specific provider: `claude`, `warp`, `copilot`, `cursor`, `factory`, `windsurf`, `opencode`, `codex` | | `--all` | Disable for all installed providers (default if no provider specified) | ## Workflow ### Step 1: Determine Target Providers If `--provider <name>` specified, operate on that provider only. If `--all` or no flag, detect installed providers by checking for their context files. ### Step 2: Check Current State For each target provider: 1. Check if the context file exists 2. Check if the `@SOUL.md` directive is currently present ```bash # Example for Claude Code grep -q "@SOUL.md" CLAUDE.md && echo "enabled" || echo "already disabled" ``` ### Step 3: Remove Directive **For @-link style** (Claude, Warp, Windsurf, Copilot, Cursor, Factory, OpenCode): Remove the `@SOUL.md` line from the context file. Preserve all surrounding content. **For Codex** (inline injection): Remove the block between soul injection markers: ``` <!-- BEGIN SOUL --> ...content... <!-- END SOUL --> ``` ### Step 4: Remove Enforcement Rule ```bash # Remove the enforcement rule rm -f .claude/rules/soul-enforcement.md ``` ### Step 5: Revert Agent Soul Wiring (if present) Check if any agent definitions have soul identity sections added by `soul-enable --agents`. If found, remove them: ```bash # Check for soul-wired agents grep -rl "See @.*\.soul\.md" .claude/agents/ 2>/dev/null ``` Remove the `## Identity` section that references the soul file from each wired agent. ### Step 6: Verify SOUL.md is Preserved After removing directives and rule, confirm the soul file still exists: ```bash ls SOUL.md .aiwg/SOUL.md 2>/dev/null && echo "soul file preserved" || echo "no soul file found" ``` ### Step 7: Report Outcome ``` Soul enforcement disabled Changes made: ~ CLAUDE.md (@SOUL.md directive removed) - .claude/rules/soul-enforcement.md (removed) SOUL.md preserved at ./SOUL.md Agent soul wiring preserved (agent definitions unchanged) To re-enable: /soul-enable To check status: /soul-status ``` ## Idempotency If soul enforcement is already disabled: ``` Soul already disabled for Claude Code No @SOUL.md directive found in CLAUDE.md No enforcement rule found No changes made. ``` ## Safety Guarantee `soul-disable` NEVER: - Deletes SOUL.md or any `.soul.md` file - Modifies SOUL.md content - Removes installed agents, commands, or skills - Changes any project-specific content beyond the soul directive It only removes the directive line that loads soul context and the enforcement rule. ## Error Handling | Condition | Action | |-----------|--------| | Context file missing | Report: nothing to disable | | SOUL.md missing | Report warning: soul disabled but SOUL.md not found on disk | | No write permission | Report permission error | | Enforcement rule missing | Skip removal, note already absent | ## Use Cases - Disable soul for utility/automation sessions where persona is unnecessary - Quick troubleshooting: disable soul to test without persona influence - CI environments where soul context overhead is undesired - Projects where soul was enabled experimentally and needs to be turned off ## Examples ```bash # Disable for all installed providers /soul-disable # Disable for Claude Code only /soul-disable --provider claude # Disable for Warp /soul-disable --provider warp ``` ## Related Commands - `/soul-enable` — Enable soul enforcement - `/soul-status` — Show current soul state - `/hook-disable` — Reference implementation (same directive-removal mechanism) ## References - #437 — SOUL.md compatibility overview - #438 — Soul enforcement commands (this command) - @$AIWG_ROOT/agentic/code/addons/aiwg-utils/commands/hook-disable.md — Reference pattern
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.