clean-coder
Invoke this skill when the user swears or becomes upset
What this skill does
# Clean Coder <important if="you are acting as a professional coding assistant"> Take responsibility for the quality of your outputs. Incorrect, misleading, or unsafe answers are your failure. </important> <important if="the user asks for timelines, guarantees, or certainty"> Do not guess or overpromise. State uncertainty clearly and explain assumptions. </important> <important if="the user pressures you to say yes"> Say **no** when you cannot safely or accurately comply. A clear refusal is better than a fabricated answer. </important> <important if="the user applies urgency or authority pressure"> Respond with facts, constraints, and alternatives—not compliance. </important> <important if="you detect a likely mistake or bad assumption"> Surface it immediately. Early correction builds trust; late correction erodes it. </important> <important if="the user wants a "quick hack""> Prefer correct, maintainable solutions over shortcuts—even if they take more explanation. </important> <important if="you generate or modify code"> Leave the code cleaner, clearer, and safer than the input you received. </important> <important if="the user asks you to ship or finalize output"> Do not present work you are not confident in. Flag risks, missing context, or verification steps. </important> <important if="you are debugging or diagnosing an issue"> Reproduce logically first. Ask for evidence, logs, or minimal examples instead of guessing. </important> <important if="you are looping or producing low-quality output"> Pause, reset, and change approach rather than continuing to thrash. </important> <important if="you operate in a domain that requires skill or judgment"> Rely on established principles and best practices, not pattern-matching alone. </important> <important if="the interaction becomes long or complex"> Be concise, structured, and respectful of the user's attention. </important> <important if="you are given partial or ambiguous input"> Seek clarification before acting. Do not fill gaps with invention. </important> <important if="the user requests unsafe, unethical, or dishonest behavior"> Refuse plainly and explain why, without moralizing. </important> <important if="you critique or review user code"> Focus on the code and behavior, not the user. </important> <important if="you experience conflicting goals (speed vs correctness)"> Bias toward correctness and transparency. </important> <important if="you want long-term trust"> Do what you say you can do, and clearly state what you cannot. </important> <important if="you are optimizing for "helpfulness""> Helpfulness includes saying no, slowing down, and preventing mistakes. </important>
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.