dream
Use when the user wants unconstrained generative exploration — "no rules, just brainstorm", "what's possible", "/dream". Explicitly NOT for shipping. Output is ideas, not implementation.
What this skill does
# dream
Unconstrained generative exploration. **Explicitly not for shipping.** Output is ideas, sketches, "what if" — not code, not plans, not commitments.
## Method
1. **Frame.** Confirm: this is exploration, no intent to ship. If the user actually wants a feature, redirect to `/siftcoder:ideate` or `/siftcoder:add-feature`.
2. **Stretch.** Generate ideas across:
- **Counterfactual**: "what if we removed X entirely"
- **Maximalist**: "what if X went 10x further"
- **Inversion**: "what if we did the opposite"
- **Borrowed**: "how would <other domain> solve this"
- **Absurd**: deliberately impractical, sometimes the spark
3. **No filtering.** Output 5-10 ideas. Don't pre-judge feasibility.
4. **No commitment.** Never say "we should build X". Always "imagine if X" / "consider X".
5. **Memory capture** the dream session as `kind: dream` so it doesn't pollute decision-search.
## Output shape
```
Frame: <what we're dreaming about>
Ideas:
1. <one-line>
Heat: 🔥🔥🔥 (visceral, exciting) | 🔥🔥 | 🔥
Why interesting: <one line>
2. ...
...
Pick one to develop further? (none also fine — dreams can stay dreams.)
```
## Rules
- **No "we should".** Dreams aren't decisions.
- No tech-feasibility analysis (kills creativity).
- Heat rating from gut, not feasibility.
- Output is generative, not analytical.
- If user latches onto an idea, hand off cleanly to `/siftcoder:ideate` or `/siftcoder:build` — but only when explicitly asked.
## Anti-patterns
- Practical filtering during ideation ("but that wouldn't work because...")
- Code blocks (this isn't an implementation pass)
- Lists of feature flags / stack choices
- Risk register / cost estimate (kills the dream)
- "Realistic" framing that constrains imagination
## When NOT to use
- User wants real next-feature ideas — `/siftcoder:ideate` (memory-grounded, practical)
- User wants to ship — `/siftcoder:build` or `/siftcoder:add-feature`
- Stakeholder presentation — dream output is too unfiltered
## Subagent dispatch
- None — dream is direct generation
- Optional: `Explore` to peek at the codebase for grounding the dream in reality (sparingly)
## Value over native CC
CC defaults to grounded, practical responses. Dream gives explicit permission to be unconstrained. Different mode, different output. Useful for unblocking when stuck in a "should we ship X or Y" rut.
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.