vision
This skill should be used when the user wants to define the north star for a project — why it exists, what problems it solves, what it would never become. Suited for the start of a project or when direction feels unclear. Triggers include "define the project vision", "what should this project become", "create a vision document", "what are we building toward".
What this skill does
# Vision
The vision is the north star. It doesn't define requirements or validate behavior — it tells you whether a decision is keeping with the spirit of the project or going against it.
If `.lore/reference/vision.html` already exists, load it and offer to review or revise.
## Two Paths
**Existing codebase**: Read broadly first — source code, `.lore/` artifacts, `CLAUDE.md`, README. Look for implicit values: what gets built, what gets rejected, what wins when things conflict. Draft from evidence. Where it's ambiguous, say so rather than inventing coherence.
**New project**: Walk through questions to pull the vision out. Adapt based on responses.
1. What is this project? Who does it serve? What problem does it solve that isn't solved elsewhere?
2. What matters most? If you had to name three things this project should always be, what are they?
3. What should this project never become? What reasonable-sounding ideas would you reject on principle?
4. Where do your values pull in opposite directions? When one conflicts with another, which wins by default?
Synthesize the user's own words into the document — don't replace their vocabulary with yours.
## Refinement
The first draft is a conversation starter. Probe:
- "Does this principle describe how you actually make decisions, or is it aspirational?"
- "Are these anti-goals things you'd genuinely reject, or just things you haven't prioritized yet?"
Principles should be behavioral guidelines, not trait aspirations. "We build for simplicity" is a trait. "Every new feature must justify the complexity it adds" is a guideline.
When the document has been reviewed at least once, offer to save. The user can keep refining or defer.
## Saving
Save to `.lore/reference/vision.html`. Load `${CLAUDE_PLUGIN_ROOT}/shared/document-schema.md` for the meta tag fields. Set `status: draft` — the user marks it approved. The document body is freeform: what the project is, what it values, what it refuses.
The output is HTML — treat this as a document worth reading, not just storing. Each principle as a styled block, anti-goals visually distinguished from values, the project's core identity prominent at the top. This is the document someone reads when a decision feels wrong. Make it feel like it matters. Inline CSS and JS are fine; no external dependencies.
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.