confidence-check
Pre-implementation validation requiring ≥90% confidence before coding. Prevents wrong-direction work by assessing duplicates, architecture alignment, and root cause understanding.
What this skill does
# Confidence Check Pre-implementation validation framework. **Never code at < 90% confidence.** ## Why This Matters Wrong-direction work costs 5K-50K tokens to undo. A 2-minute confidence check saves hours of rework. ## The 90% Rule Before implementing ANY significant change: ``` Confidence < 70% → STOP. Research more. Confidence 70-89% → PAUSE. Fill gaps first. Confidence ≥ 90% → PROCEED with implementation. ``` ## Confidence Checklist ### 1. Duplicate Check (20 points) - [ ] Searched codebase for existing solution - [ ] Checked if similar pattern exists elsewhere - [ ] Verified not reinventing existing functionality ### 2. Architecture Alignment (20 points) - [ ] Understand where this fits in the system - [ ] Know which files/modules are affected - [ ] Approach matches existing patterns ### 3. Requirements Clarity (20 points) - [ ] Clear on what success looks like - [ ] Understand edge cases - [ ] Know acceptance criteria ### 4. Root Cause Understanding (20 points) - [ ] If fixing bug: know WHY it happens - [ ] If adding feature: know WHY it's needed - [ ] Understand the problem, not just symptoms ### 5. Implementation Path (20 points) - [ ] Know the steps to implement - [ ] Identified potential blockers - [ ] Have fallback approach ## Scoring ``` Score each category 0-20: - 0-5: No understanding - 6-10: Partial understanding - 11-15: Good understanding, some gaps - 16-20: Full understanding Total = sum of all categories (0-100) ``` ## Output Template ```markdown ## Confidence Check: [Task] ### Assessment | Category | Score | Notes | |----------|-------|-------| | Duplicate Check | /20 | | | Architecture | /20 | | | Requirements | /20 | | | Root Cause | /20 | | | Implementation | /20 | | | **TOTAL** | **/100** | | ### Gaps Identified - [ ] [gap 1 - how to fill] - [ ] [gap 2 - how to fill] ### Verdict **[PROCEED / RESEARCH MORE / STOP]** ### If RESEARCH MORE: 1. [specific question to answer] 2. [file to read] 3. [person to ask] ``` ## Quick Check (30 seconds) For small changes, ask yourself: 1. Have I read the code I'm changing? (Y/N) 2. Do I know why this change is needed? (Y/N) 3. Do I know how to test it works? (Y/N) All Y → Proceed Any N → Pause and fill the gap ## When to Skip - Typo fixes - Comment updates - Obvious one-liners - Explicitly requested by user with full context ## Anti-Patterns ❌ "I'll figure it out as I go" ❌ "This looks similar to something I did before" ❌ "The user asked for it so it must be right" ❌ "I'll just try this and see" ✅ "I understand the problem and solution" ✅ "I've verified no existing solution" ✅ "I know exactly what files to change"
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.