meta-testing
Validates specs are workable through PoC tests and validation questions
What this skill does
# Meta-Testing Skill Validates specifications before full implementation (Stage A). ## Purpose Catch bad specs BEFORE writing production code: - Is this spec actually implementable? - Does it fulfill the requirements? - Is the design unnecessarily complex? - Will this work at scale? ## Two Approaches (Both Used) ### 1. Auto-Generated PoC Tests **Generate minimal proof-of-concept code:** ``` Spec: Use Stripe for payments PoC Test: → Generate: Minimal Stripe client → Test: Can we connect to API? → Test: Can we create test charge? → Run and verify Results: ✅ Connection works ✅ Test charge succeeds → Spec is viable ``` **When to use:** - Technical integration questions - "Can we connect to X?" - "Does this API do what we need?" - "Will this pattern work?" ### 2. Manual Validation Questions **Ask critical questions user must answer:** ``` Spec: Multi-tenant with database-per-tenant Questions: ? Does this scale to 1000 tenants? → User answer → Might not (connection limits) → Recommendation: Use shared schema instead ? Is this complexity justified? → User answer → Maybe not for MVP → Recommendation: Start simpler Updated spec based on answers ``` **When to use:** - Scalability questions - Complexity tradeoffs - Business decisions - "What if" scenarios ## Case-by-Case Decision **System decides which approach:** ``` Technical validation → Auto PoC Business/scale validation → Manual Questions Both often needed → Use both ``` ## PoC Test Generation **Template:** ```python # PoC Test: [What we're validating] # Generated: [timestamp] # Spec: [spec-reference] [Minimal test code] # Expected: [what should happen] # Actual: [what happened] # Result: PASS/FAIL ``` **Run and report:** ``` Meta-Test Results: ✅ PoC-1: API connection (PASS) ✅ PoC-2: Basic operation (PASS) ⚠️ PoC-3: Load test (SLOW - 500ms, expected <100ms) Recommendations: - Consider caching for PoC-3 - Otherwise spec validated ``` ## Complexity Check **Red flags for over-complexity:** - >10 components for simple feature - >5 integration points - Custom solution when standard exists - "Microservices" for small app **Suggest simplification:** ``` ⚠️ Complexity Alert Spec proposes: 8 microservices for email notifications Recommendation: Start with single service - Can always split later - Easier to debug - Faster to implement Simplify spec? [Y/n] ``` ## Iteration Loop ``` 1. Create spec 2. Run meta-tests (auto + manual) 3. Identify issues 4. Update spec 5. Re-test 6. Repeat until validated 7. Finalize ``` ## Success Criteria Spec is ready when: - ✅ All PoC tests pass - ✅ Critical questions answered - ✅ Complexity justified - ✅ No obvious blockers - ✅ Requirements fulfilled Then move to Stage B for implementation.
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.