chroot
Use to create a tighter file-access jail than /scope — explicit file list, not glob patterns. Useful for "I only want AI touching these 12 specific files". Backed by src/services/chroot.ts.
What this skill does
# chroot Tight jail. Explicit file list, not glob. Stricter than `/scope`. ## When chroot beats scope - `/scope` — pattern-based; flexible; "all of src/auth" - `/chroot` — file-list-based; rigid; "exactly these 12 files" Chroot for: deep refactors where you want to forbid surprise edits anywhere else. ## Method (set) 1. **Patterns.** User specifies glob patterns (e.g. `src/auth/**/*.ts`, `!src/auth/secrets/**`). 2. **Expand** via `src/services/chroot.ts` `ChrootManager.setChroot`. Negation patterns (`!`) excluded. 3. **Persist** the **explicit file list** (not the patterns) — pinned at jail-set time. 4. **Confirm.** Show file count + first 10 files. ## Method (check) `ChrootManager.checkFile(path)` returns true/false. Used by tooling to enforce. ## Method (release) `ChrootManager.clearChroot()` removes `.siftcoder/chroot.json`. Confirm with user. ## Output shape ``` Setting chroot: Patterns: ["src/auth/**/*.ts", "!src/auth/secrets/**"] Expanded: 14 files Sample: - src/auth/middleware.ts - src/auth/session.ts - src/auth/jwt.ts - ... (11 more) Status: jail active ``` ## Rules - **List pinned at set-time.** Adding files to disk after chroot doesn't auto-include them. - **Negation patterns first.** `["src/auth/**", "!src/auth/secrets/**"]` is explicit. - **Single-jail per project.** Don't try to layer multiple chroots. - **Backup on release.** Save the list to checkpoints so it's recoverable. ## Anti-patterns - Setting chroot then expecting new files to be auto-included (they aren't) - Combining chroot with scope (use one) - Chroot too narrow (blocks the task itself) - Forgetting to release after task complete ## When NOT to use - Pattern-shaped boundary works — `/scope` - Greenfield — no jail needed yet - Multi-developer mob session — chroot is per-project, can collide ## Subagent dispatch - None — `ChrootManager` is direct ## Value over native CC + scope Scope is patterns — flexible. Chroot is explicit file list — rigid. The rigidity IS the value when you genuinely want to lock a refactor to a known set.
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.