file-deleter
REQUIRED for all file and directory deletions. This system replaces rm/rmdir commands. Always use this skill instead of bash rm commands when removing any files or directories. Moves items to recoverable .deleted/ trash folder with preserved structure.
What this skill does
# File Deleter Skill - MANDATORY DELETION METHOD **CRITICAL**: This skill MUST be used for ALL file and directory deletion operations. The `rm` command is blocked on this system. ## System Policy - **ALL deletions** must use this skill's `delete-file.js` script - Direct `rm`, `rm -rf`, `rmdir` commands are BLOCKED - This applies to cleanup, refactoring, removing old files, or any deletion operation - No exceptions - even for temporary files or build artifacts ## When to Use Use this skill ANY time you need to: - Remove any file (code, config, markdown, etc.) - Delete any directory (empty or with contents) - Clean up temporary files - Remove build artifacts - Delete old/unused code - Perform any operation that would normally use `rm` or `rmdir` ## How It Works The skill uses a Node.js script that: 1. Finds the project root (where `.git` and `.claude` directories exist) 2. Moves specified files/directories to `.deleted/` while preserving their path structure 3. Creates a `.gitignore` in `.deleted/` that ignores all contents 4. Handles both absolute and relative paths 5. Recursively moves directories with all contents 6. Overwrites existing files/directories in `.deleted/` ## Script Location The `delete-file.js` script is located in the scripts subdirectory of this skill. When Claude Code loads this skill, the base directory path is provided, allowing the script to be located at `<skill-base-dir>/scripts/delete-file.js`. ## Usage **Standard deletion syntax** - use this for all deletions: ```bash node <skill-base-dir>/scripts/delete-file.js <path1> [path2] [path3] ... ``` **Examples:** ```bash # Delete single file node <skill-base-dir>/scripts/delete-file.js src/old-component.tsx # Delete multiple files node <skill-base-dir>/scripts/delete-file.js file1.txt file2.js dir/file3.md # Delete entire directory node <skill-base-dir>/scripts/delete-file.js old-features/ # Delete multiple directories and files node <skill-base-dir>/scripts/delete-file.js temp/ build/ old-file.txt ``` ## Behavior - **Non-existent files**: Skipped with warning, script continues - **Overwriting**: Existing files/directories in `.deleted/` are overwritten - **Directory structure**: Preserved within `.deleted/` - Example: `src/components/Button.tsx` → `.deleted/src/components/Button.tsx` - **Git ignore**: All contents of `.deleted/` are automatically git-ignored ## Recovery Files remain recoverable in `.deleted/` and can be manually restored if needed. ## Error Handling If you attempt to use `rm` commands, you will receive an error message directing you to use this skill instead. Always default to using this script for any deletion operation.
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.