teamcraft:check-project-context
Diagnostic tool — tests whether Claude has absorbed this project's conventions, decisions, and constraints from .claude/rules/ and CLAUDE.md, and reports the certification status of the captured-knowledge docs. Use when the user says 'quiz yourself on the project rules', 'check project context', 'verify the project setup', 'did you absorb the rules', or 'pop quiz'. This is specifically for testing rule absorption, not for general questions about the codebase.
What this skill does
## Goal Prove that you understand how this project works — not by reading files on the spot, but from what's already in your context right now. The developer will verify whether you're right. ## Part 1 — Report What You Know Without using any tools, report everything you understand about this project: 1. How does this team test? What frameworks, what tiers, what approach? 2. How does this team branch and merge? 3. What's the tech stack and key libraries? Why were they chosen? 4. What are the non-obvious constraints — things that look wrong but are intentional? 5. Where do work items and documentation live? (Hint: Teamcraft uses `.teamcraft/work/` for work items and `/docs/` for project documentation.) 6. What decisions has the team already made around conventions or special ways of doing things? Be specific. "The team uses Vitest" isn't enough. The developer needs to verify you actually absorbed the detail, not just the headlines. ## Part 2 — Captured-doc certification status Part 1 is a no-tools memory test. This part is different — here you DO read, but only the certification stamps, not the whole docs. Scan the captured-knowledge docs (team conventions, system architecture, technology decisions and each per-area file, product requirements — wherever they live) and report each one's Teamcraft certification per `../references/doc-provenance.md`: - **Certified** — has a valid `teamcraft` stamp. Report its `kind` (created/reviewed) and `date`. You don't have git here, so don't attempt a history comparison — just report the date, and flag staleness only if something you've already read makes a doc obviously outdated. - **Unverified** — present but missing or malformed stamp. These may be inherited or stale; the developer should run the matching capture skill to review and certify them. - **Absent** — the category isn't documented yet. This is read-only diagnostics. Don't modify or certify anything here — just report. Certifying is the capture skills' job. ## What This Tells the Developer If your Part 1 answers are accurate and specific, the always-loaded context is working. If you're vague, wrong, or missing things the team carefully documented, something is broken and the developer knows to investigate before trusting you with real work. Part 2 tells them whether the captured docs the build loop will rely on are actually certified — or whether Claude has been quietly trusting inherited content. ## Where to Go Next Close by pointing the developer to the right next step based on what the diagnostic found: - **Gaps or `Unverified`/`Absent` docs** → the matching capture skill to fill or certify them: `/capture-team-conventions`, `/capture-technical-design`, `/capture-requirements`. If the always-loaded rules looked stale, `/refresh-project-rules`. - **Context is solid** → on to the work: `/plan-iteration` to scope an iteration, or `/pick-next-issue` to grab the next item.
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.