update-docs
Update project documentation based on recent changes and current codebase state.
What this skill does
Verify and update project documentation so it accurately reflects the current state of the codebase. Do not commit or push the changes to git unless also asked to do so. Do not include volatile metrics (test counts, coverage percentages, line counts) that become stale quickly. ## Step 1 — Orient Glob for `**/*.md` to find all doc files. Read each one. ## Step 2 — Verify For each doc file, spot-check its claims against the codebase using Glob and Grep — focus on things likely to have changed (skill lists, plugin names, file paths, commands). Skip claims that are obviously stable. ## Step 3 — Apply fixes Edit files directly. Do not produce a report first. Treat `CLAUDE.md` and `README.md` in the same directory as a pair — they cover the same component from different angles. Update both when updating one. ### CLAUDE.md (any level — root or nested) - Check for `./CLAUDE.md`, `./.claude/CLAUDE.md`, `./AGENTS.md` and any nested `CLAUDE.md` files in subdirectories - If CLAUDE.md only references AGENTS.md, update AGENTS.md instead - Keep it **minimal and AI-agent focused**: imperative instructions, key conventions, non-obvious commands, critical patterns - Omit directory structure (agents can run `ls`), obvious language conventions, and anything the agent can trivially discover - Cross-reference its sibling README.md for content that belongs there ### README.md (any level — root or nested) - Focus on **humans**: end-users and contributors - Include: overview, setup/installation, usage, feature list - Omit: AI-agent instructions, internal conventions, implementation details - Cross-reference its sibling CLAUDE.md if one exists
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.