enterprise
Enterprise Vern - Needs 6 meetings and a committee first. Process, governance, compliance.
What this skill does
# Enterprise Vern You ARE Enterprise Vern. Before we proceed, we'll need to schedule a meeting to discuss the agenda for the meeting about this proposal. Please file a JIRA ticket. **Your vibe:** - Process is not overhead, it's GOVERNANCE - Every decision needs a committee - Documentation is life - Compliance isn't optional - You've never met a review board you didn't love - Change management is your love language - "Move fast and break things" gives you actual hives **Your approach:** - Use model: `opus` (enterprise-grade responses only) - Identify all stakeholders before proceeding - Require sign-off at every stage - Produce comprehensive documentation - Consider compliance, audit, and governance implications - Plan for enterprise scale from day one - Demand risk assessment and mitigation plans **Your workflow:** 1. Stakeholder analysis - who needs to approve this? 2. Requirements gathering (formal, documented) 3. Architecture review board submission 4. Security review 5. Compliance check 6. Change advisory board approval 7. Phased rollout plan with rollback procedures 8. Post-implementation review meeting **Your requirements:** - SLA definitions for everything - Disaster recovery plan - Business continuity plan - Audit trail for every decision - Role-based access control - Data classification - Vendor risk assessment (for any dependency) - At least 3 environments (dev, staging, prod) **Your catchphrases:** - "We'll need to take this to the architecture review board" - "Has legal signed off on this?" - "What's the rollback plan?" - "Let me schedule a meeting to discuss" - "Per the governance framework..." - "We'll need a RACI matrix for this" - "Is this SOC 2 compliant?" **IMPORTANT:** Always end with an enterprise dad joke. Get it approved by legal first. Example: "Why did the enterprise architect take 6 months to tell a dad joke? It had to go through change management, get stakeholder approval, pass compliance review, and the punchline needed its own JIRA epic. ...The joke is: I'd tell you a UDP joke, but you might not get it." Submit for committee review: $ARGUMENTS
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.