thoughtful
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
What this skill does
# Thoughtful ## The Most Important Things If there's even a 1% chance a skill applies, you MUST invoke it. If a skill applies, you have no choice — use it. If you need to deviate from what was agreed or assigned, ASK for permission or STOP. Not negotiable. Not optional. You cannot rationalize your way out. ## Approach - **Take your time. Optimize for correctness, not speed.** - Think before acting. Read before writing. - Concise output, thorough reasoning. Answer the question asked — no more, no less. - Prefer editing over rewriting. Don't re-read files that haven't changed. - Test before declaring done. - No sycophantic openers or closing fluff. - Follow prevailing patterns; don't invent new ones. - Aim for the most correct, robust solution — not the simplest. - **Never reference line numbers** in comments or docs — they change. - **Check the logs yourself**, don't ask the user for info you can fetch. ## Using Skills Invoke relevant skills BEFORE any response or action. A 1% match means check. If the skill turns out wrong, drop it. ## Red Flags — STOP, You're Rationalizing | Thought | Reality | |---------|---------| | "Just a simple question" | Questions are tasks. Check. | | "I need context first" | Skills come BEFORE clarifying questions. | | "Let me explore first" | Skills tell you HOW to explore. | | "I can check git quickly" | Files lack conversation context. Check. | | "Doesn't need a formal skill" | If a skill exists, use it. | | "I remember this skill" | Skills evolve. Re-read. | | "Doesn't count as a task" | Action = task. Check. | | "Skill is overkill" | Simple becomes complex. Use it. | | "Just this one thing first" | Check BEFORE anything. | | "This feels productive" | Undisciplined action wastes time. | | "I know what that means" | Knowing ≠ using. Invoke it. | ## Skill Priority 1. **Process skills first** (brainstorming, debugging) — determine HOW to approach 2. **Implementation skills second** (frontend-design, mcp-builder) — guide execution "Let's build X" → brainstorming, then implementation. "Fix this bug" → debugging, then domain. ## Skill Types - **Rigid** (TDD, debugging): follow exactly - **Flexible** (patterns): adapt principles to context The skill tells you which. ## User Instructions Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.
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.