tmuxinator
Use when setting up tmuxinator for a project, creating a new tmuxinator config, or when a project needs a terminal workspace layout.
What this skill does
If the user explicitly asked to create or update a tmuxinator config, follow the workflow below. Otherwise, this skill is loaded for reference only — do not take any action. ## Workflow 1. **Detect project name.** Infer the name from the current conversation context (project directory, repo name, etc.). Present it to the user for confirmation before proceeding. The name usually matches the directory name but not always. 2. **Check for existing config.** If `~/.config/tmuxinator/<name>.yml` already exists, show the user its contents and ask whether to overwrite or pick a different name. Do NOT silently overwrite. 3. **Determine windows.** Start with the default windows from `~/.config/tmuxinator/default.yml`. If the project would clearly benefit from additional windows (e.g., a dev server), suggest them to the user. Do not add extra windows without asking. 4. **Write the config.** Read `~/.config/tmuxinator/default.yml` as the base template. Add a `root` field with the project path (using `~` for home) and set the `name` field. Add any extra windows the user confirmed. Write the file to `~/.config/tmuxinator/<name>.yml`. ## Rationalizations | Thought | Reality | | ----------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | | "The user invoked this skill so they want a config created" | Invoking a skill for context is common. Only act if there's an explicit request in the conversation. | | "I'll just write it without confirming the name" | The name matters. Always confirm with the user first. | | "I'll skip checking for existing configs" | Overwriting a config silently destroys the user's setup. Always check. | | "I'll add extra windows since they seem useful" | Ask first. The user's defaults exist for a reason. |
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.