session-start
Session context loading.
What this skill does
# Session Start Load critical context and recent history at the start of each session or after `/clear`. ## Contract Inputs: - Project root - Current date - Existing `.agents/memory/` and `.agents/SESSIONS/` files Outputs: - Loaded repo memory summary - Today's session context (if any) - Open next-steps surfaced from the latest session log Creates/Modifies: - No required writes - May create today's session file only through `session-documenter` External Side Effects: - None Confirmation Required: - Before creating or rewriting session files when paths are ambiguous Delegates To: - `session-documenter` to track the active session - `rules-capture` if startup reveals uncaptured preferences ## Workflow ### 1. Read Repo Memory (CRITICAL — source of truth) Read the repo's memory files at `.agents/memory/`. These are the source of truth for current project context: architecture, deployment state, migrations, known gotchas, and operating decisions. - Each memory file carries `last_verified: YYYY-MM-DD`. If that date is >30 days old, re-verify before citing. - Files with `status: temporary`: always check whether they are still valid before relying on them. Critical rules, communication preferences, and quality standards live in `CLAUDE.md` (repo + global) and global memory — already loaded by the harness. Do not look for a separate preferences file. ### 2. Read Today's Session File Read today's session to understand what was already done before `/clear`: Read today's session file at `.agents/SESSIONS/YYYY-MM-DD.md` (where YYYY-MM-DD is today's date). If the file exists, it shows tasks completed, decisions made, files changed, mistakes, and next steps. If it doesn't exist yet, this is a fresh session day. ### 3. Activate Session Documenter Run the `session-documenter` skill to track all work throughout the session. ### 4. Confirmation After reading memory and the session file, provide a brief confirmation (5-7 bullet points max): - Critical rules understood - Repo memory loaded (flag any stale `last_verified` or `status: temporary` files) - Today's session context loaded (if it exists) - Session documenter active - Open next-steps surfaced from the latest session log (if any) ## Related Skills - **session-end** — Document session before clearing context - **session-documenter** — Tracks work throughout the session
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.