zen
Use when the user wants aggressive simplification — "delete what we don't need", "minimal code", "/zen". Delete-as-default. Removes dead code, abstractions earning their keep, scaffolding from when "we might need this".
What this skill does
# zen
Less is more. Delete first; build only what's load-bearing.
## Method
1. **Inventory.** Read the target area. List every file/symbol/abstraction. Note for each:
- **Used by** how many other places?
- **Last touched** when?
- **Tested** how thoroughly?
2. **Score for deletion.** Candidates:
- 0 uses → delete
- 1 use, last touched > 6 months → delete; inline at the use site
- Abstraction with one concrete impl → delete the abstraction; use the impl directly
- Scaffolding "for future use" → delete; YAGNI
- Dead branches (unreachable code) → delete
- Defensive checks for impossible conditions (internal-only callers always pass valid input) → delete
3. **Confirm with user** for anything user-facing or that crosses a module boundary. **Internal-only** deletions can proceed.
4. **Delete.** One concept per commit.
5. **Verify.** Tests stay green. If a test was the only thing keeping the dead code alive — delete the test too (the behaviour was never used).
6. **Re-measure.** Lines deleted, abstractions removed, files removed.
## Output shape
```
Target: <module/area>
Inventory: <N symbols, M files>
Deleted:
- <file/symbol> — reason
- <file/symbol> — reason
...
Inlined:
- <abstraction> → <concrete site>
Score: <-X lines, -Y files, -Z abstractions>
Tests: <M passing, N before, P deleted>
```
## Rules
- **Defaults to delete.** Burden of proof is on keeping, not removing.
- **No "might need it later".** When you need it, you'll write it then. Memory will remember the prior version.
- **Capture deletion to memory** with full content of what was deleted, so it's recoverable from the log.
- **Public API** — confirm with user. **Internal** — proceed.
- **Test that asserts implementation detail** of deleted code → also delete.
- **Comments explaining deleted code** → delete the comment too.
## Anti-patterns
- Keeping a wrapper "for consistency" when there's only one wrapper
- Keeping a flag for a feature that's been on for 2 years
- Keeping an abstraction layer with one impl
- Keeping `_unused` parameters
- Keeping `// removed in PR #123` comments
## When NOT to use
- Active refactor in progress — finish that first
- Library/SDK code with external consumers — public API needs deprecation, not deletion
- Bug fix — different workflow
## Subagent dispatch
- `Explore` to inventory and find use counts
- `general-purpose` to perform the deletions
- `archaeologist` if "I think this used to be used" — confirms history before delete
## Memory capture
Every deleted symbol gets captured with full content + reason. The provenance edge marks the deletion. Future `mem_search` retrieves "what did we delete from <module>" — recovery is one query away.
## Value over native CC
CC won't aggressively delete on its own. CC tends toward additive suggestions ("you could also..."). This skill flips the default. The bias IS the value.
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.