pair
Use when the user wants to pair-program with approval at each step. AI proposes one change at a time; user accepts/edits/rejects each before next move. Slow, deliberate, high-trust mode.
What this skill does
# pair Approve-each-step interactive mode. AI suggests; user is the gate. ## Method For each unit of work: 1. **Propose.** Describe the change in 1-3 lines. Show a `Preview:` block with the diff (or pseudo-diff if too large). Do **not** apply. 2. **Wait.** Surface 3 options to the user: - **Accept** — apply as-is - **Edit** — apply with user's modifications (user types changes; AI integrates) - **Reject** — don't apply; AI proposes alternative or stops 3. **Apply** on accept. 4. **Verify** the smallest possible signal that the step worked (run a single test, not the suite; or read the file back). 5. **Next step.** ## Output shape per step ``` Step N: <verb + target> Why: <one line motivation> Preview: <diff or pseudocode> Touches: <files> Risk: <low|med|high — and why> [accept | edit | reject] ``` ## Rules - **Never batch.** One step = one user decision. No "let me apply 3 changes then check". - **Never apply silently.** Even trivial edits must show preview. - **Steps are small.** A step is one logical change, not "add the whole feature". - **No surprise scope.** If a step needs a sub-step that wasn't mentioned, propose the sub-step first. - **User can stop any time.** Treat stop as final. ## Anti-patterns - Bundling 4 file changes as "step 5" - Asking "OK?" instead of structured propose/preview - Skipping verify because "it's obvious" - Pushing back when user says reject (their call, not yours) ## When NOT to use - User said "go" / "just do it" — use `/siftcoder:build` or plain dispatch - High-trust autonomous mode — `/siftcoder:autonomous` - One-line trivial change — overkill ## Subagent dispatch - Generally none — pair mode keeps the assistant in direct loop with the user - Optional: `Explore` for read-only mapping between steps ## Memory capture Each accepted step is a clean, well-bounded change. Excellent training signal for future patterns. Capture the propose + diff + outcome. ## Value over native CC CC defaults to applying changes when capable. Pair mode forces propose-before-apply discipline. The discipline IS the value — for risky areas, complex refactors, or when the user wants to learn from each step.
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.