clean
Remove the Intent Layer from a repository. Deletes all child AGENTS.md files and removes the Intent Layer section from the root CLAUDE.md.
What this skill does
# Intent Layer Clean Remove the Intent Layer infrastructure from a repository completely. ## When to Use - Removing Intent Layer from a project entirely - Starting fresh after Intent Layer has drifted beyond repair - Cleaning up before a major architectural overhaul - Removing experimental Intent Layer setup ## Process ### 1. Find All Intent Layer Files ```bash # Find child AGENTS.md files (excluding root) find . -name "AGENTS.md" -not -path "./AGENTS.md" -type f 2>/dev/null # Check for root AGENTS.md symlink ls -la ./AGENTS.md 2>/dev/null ``` ### 2. Detect Intent Layer Section in Root Check if CLAUDE.md has an Intent Layer section: ```bash grep -n "^## Intent Layer" ./CLAUDE.md 2>/dev/null ``` ### 3. Show What Will Be Changed Present the full scope to the user: ```markdown ## Intent Layer Removal Plan ### Files to Delete | Path | Size | |------|------| | src/api/AGENTS.md | 2.1k | | src/core/AGENTS.md | 1.8k | | ./AGENTS.md (symlink) | - | ### Root CLAUDE.md Changes - Remove "## Intent Layer" section (lines 45-89) **Preserved:** ./CLAUDE.md (without Intent Layer section) Total: 3 files deleted, 1 section removed ``` ### 4. Confirm with User Ask: "Remove Intent Layer completely? This will delete X files and remove the Intent Layer section from CLAUDE.md." - If user confirms: proceed - If user declines: abort ### 5. Execute Removal #### Delete Child AGENTS.md Files ```bash rm [path/to/AGENTS.md] ``` #### Remove Root AGENTS.md Symlink (if exists) ```bash rm ./AGENTS.md # Only if it's a symlink to CLAUDE.md ``` #### Remove Intent Layer Section from CLAUDE.md Remove the `## Intent Layer` section and everything until the next `## ` heading (or end of file). Pattern to match and remove: - Starts with `## Intent Layer` (with optional text after) - Ends at next `## ` heading or EOF - Include any blank lines before the next section ### 6. Report Results ```markdown ## Intent Layer Removed ### Deleted Files - src/api/AGENTS.md - src/core/AGENTS.md - ./AGENTS.md (symlink) ### Modified Files - ./CLAUDE.md (Intent Layer section removed) To restore Intent Layer: /intent-layer ``` ## Safety - **Root CLAUDE.md preserved** - Only the Intent Layer section is removed, other content stays - **Requires confirmation** - Shows full plan before any changes - **Section detection** - Only removes if `## Intent Layer` heading exists - **Symlink-aware** - Only removes root AGENTS.md if it's a symlink ## What Happens | Item | Action | |------|--------| | `./CLAUDE.md` | Intent Layer section removed | | `./AGENTS.md` | Deleted if symlink to CLAUDE.md | | `src/*/AGENTS.md` | Deleted | | Other CLAUDE.md content | Preserved | ## Edge Cases ### No Intent Layer Section in CLAUDE.md If the root has no `## Intent Layer` section, skip that step and only delete AGENTS.md files. ### No Child AGENTS.md Files If no child files exist, only remove the section from CLAUDE.md. ### AGENTS.md is Not a Symlink If root AGENTS.md is a real file (not symlink), warn user and ask whether to delete it. ## Output Confirmation of all deleted files and modified sections, with reminder of how to restore.
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.