scope
Use to define/show/modify the .siftcoder/scope.json file that the boundary-enforcer hook reads. Bounds where AI can write. "Limit to these files", "lock down scope", "show current scope".
What this skill does
# scope
Manage `.siftcoder/scope.json` — the allow/deny list the `boundary-enforcer.mjs` hook enforces.
## Schema
```json
{
"allow": ["src/auth/**", "tests/auth/**"],
"deny": ["src/auth/secrets/**"]
}
```
- **No scope file** → all writes allowed (only blocked by Claude Code's own permissions)
- **Scope set** → writes only to `allow` patterns; `deny` always wins over `allow`
## Method (set)
1. **Patterns.** User specifies allow + (optional) deny.
2. **Validate.** Each pattern must be syntactically valid; warn on patterns that match nothing.
3. **Persist** via `src/services/state.ts` `StateManager.saveScope`.
4. **Confirm.** Show what's currently in scope.
## Method (show)
1. Load scope.
2. Render allow + deny patterns.
3. Optionally expand patterns to file count.
## Method (clear)
1. Confirm with user (clearing scope removes all bounds).
2. Delete `.siftcoder/scope.json`.
## Method (add / remove)
Mutate the file via `StateManager`.
## Output shape
```
Current scope (.siftcoder/scope.json):
Allow:
- src/auth/**
- tests/auth/**
Deny:
- src/auth/secrets/**
Effective files: 142 allowed, 3 denied
Hook status: boundary-enforcer.mjs active in PreToolUse Write|Edit
```
## Rules
- **Deny wins over allow.** A path matching both is denied.
- **Pattern syntax is glob.** `**` for recursive, `*.ext` for extension.
- **Validate before save.** Warn if a pattern matches nothing (likely typo).
- **Backup on clear.** Save the cleared scope to `.siftcoder/checkpoints/scope-cleared-<ts>.json` so it can be recovered.
## Anti-patterns
- Allow `**` (defeats the point of scope)
- Forgetting to set deny for secrets
- Setting overly narrow scope that blocks legit work
- Ignoring "matches nothing" warnings
## When NOT to use
- Greenfield (no scope needed yet)
- Single-file edit (use Claude Code's own `--allowed-file` if available)
- Pre-merge review (different concern)
## Subagent dispatch
- None — uses `StateManager` directly
- Optional: `Explore` to validate patterns by listing matches
## Value over native CC
CC has its own permission system but doesn't natively support per-project allow/deny scope files enforced via hook. Scope IS the value — explicit project-scoped boundaries.
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.