Claude Skills by mcorbett51090

Design the ROS 2 computation graph: nodes and their boundaries, topics/services/actions, the RMW/DDS layer and per-topic QoS, executors & callback groups, node composition, and the real-time vs non-real-time split. QoS and the real-time boundary are architecture decisions, not runtime flags. Distro/DDS specifics are verify-at-use.

Cross the sim-to-real gap and build the safety architecture: simulate every behavior before actuating, measure and close the reality gap (dynamics, sensor noise, latency, domain randomization), and make safety a system property — monitored safe state, bounded actuation, degraded modes, and a risk assessment. Functional-safety standard pointers (ISO 10218 / ISO 13849 / ISO 12100) are verify-at-use.

Design a demo that maps to the buyer's discovered pain instead of touring features — build a Great Demo!-style storyline (show the compelling result first, then peel back only the layers the buyer asked for), tie every moment to a discovered pain and its business impact, and script the honest shipped-vs-roadmap boundaries. Reach for this after discovery, when the user needs to build or tighten a demo. Used by `sales-engineer` (primary).

Decide if a POC is warranted and, if so, write measurable success + exit criteria a champion signs before kickoff, scope a time-boxed plan, and build the evaluation scorecard that converts a passed POC to a technical win. Reach for this when a prospect asks for a proof-of-concept or pilot, or when an SE needs to keep a POC from sprawling. Used by `poc-evaluation-lead` (primary) and `sales-engineer`.

Respond to an RFP/RFI/RFQ — decide go/no-go before committing effort, then build a compliant, scannable requirement-by-requirement response matrix (comply / partial / roadmap / no-bid), thread the win themes, and run the compliance checklist so the bid isn't disqualified on a technicality. Reach for this when a formal RFP/RFI lands. Used by `rfp-security-response-specialist` (primary).

Answer a security / vendor-risk questionnaire (SIG, CAIQ, VSA, or a bespoke one) honestly and defensibly — map every answer to an actual control and its SOC 2 / ISO 27001 evidence, state shipped vs roadmap vs not-applicable plainly, flag any unverifiable claim for security-reviewer before it ships, and capitalize answers into a reusable, freshness-dated trust-answer library. Reach for this on any inbound security questionnaire. Used by `rfp-security-response-specialist` (primary).

Run value-based technical discovery before any demo or POC — frame the deal with MEDDPICC, surface the prospect's pain and its quantified business impact, identify the decision criteria/process/champion, and capture it all in the discovery-notes template so the demo can be tailored to real pain. Reach for this when the user has (or just had) a discovery call, or is about to demo with no discovered pain. Used by `sales-engineer` (primary) and `poc-evaluation-lead`.

Build a stage-weighted, aged forecast with coverage — surface the at-risk deals. Reach for this on a forecast question.

Design quota to ramped-rep capacity and read the attainment distribution it implies. Reach for this on a quota or territory question.

Diagnose win-rate and sales-cycle stage-by-stage — find the leaking stage before adding leads. Reach for this on a conversion question.

Model sales velocity across its four levers (deals, win-rate, ACV, cycle) and show the trade-offs. Reach for this on a speed question.

Read coverage as a ratio against quota by segment and close-date, not a total pipeline number. Reach for this on a coverage question.

Build Bulk API 2.0 ingest and query jobs for high-volume data movement. Use when loading or extracting large datasets over the REST Bulk API rather than row-by-row.

A safe data-load runbook — sandbox-first, backup, dedup, and verify — for any bulk data operation. Use before loading, updating, or deleting production data at volume.

Scaffold a Lightning Web Component bundle (.html / .js / .js-meta.xml) with an FLS-aware Apex controller. Use when creating a new LWC.

Stand up a 2GP + DevOps Center release pipeline — packaging, dependency-ordered deploy, test gate, and promotion across environments. Use when designing or running a Salesforce release process.

Write selective, bulk-safe SOQL that binds its variables and avoids non-selective-query errors on large objects. Use when authoring or fixing a SOQL query, especially against high-volume objects.

Control the perishable-inventory leak: design a no-show / late-cancel policy with deposits or card-on-file, a rebook-at-checkout habit, a reminder cadence, and a waitlist that backfills cancellations. Prevent the no-show first; enforce the policy second.

Read the salon/spa as a stack of perishable chair-hours and room-hours. Compute utilization (productive hours booked / available), test whether current capacity is full before adding a chair, room, or provider, and tie utilization to the staffing model and demand pattern.

Model provider pay deliberately: commission tiers vs hourly-plus-commission vs booth rent vs hybrid. Compare risk, upside, control, and cost against the provider's book — and flag the worker-classification (employee vs 1099) consequence for a licensed professional. Economics only, not legal advice.

Lift the two margin levers the chair controls: retail attach (product sold alongside the service, on trust the provider already earned) and service mix (tilting the book toward higher-margin services). Read revenue and margin per service hour, not just bodies through the door.

Build graded relevance judgments (explicit or click-derived) and an offline harness before tuning. Reach for this when there's no eval.

Root-cause a relevance bug in tokenization/analysis/mapping before touching the ranking formula. Reach for this on a no-match or wrong-match bug.

Compute NDCG, MRR, and precision@k against the judgment list with a baseline. Reach for this before any tuning.

Set a p95 latency budget, decompose per-stage latency, and tune relevance within it. Reach for this on a speed/capacity question.

Confirm an offline relevance win with an online A/B on CTR/conversion before declaring victory. Reach for this after an offline gain.

Stand up tuned application security scanning in CI: SAST + SCA per-PR, DAST on a deployed build, secret-scanning, and triage by exploitability×blast-radius rather than raw CVSS.

Playbook for detecting secrets committed to Git — pre-commit hooks, CI scanning, historical repo scanning — and the full remediation procedure when a secret is found: rotation, history rewrite, and the post-incident checklist.

Manage secrets safely: detect them in code/config/logs, vault them, federate with short-lived credentials, rotate on a schedule, and treat any committed secret as compromised (rotate, don't just delete).

Secure the software supply chain from the consume side: ingest the SBOM, triage CVEs by reachability, pin dependencies with a deliberate update cadence, verify SLSA provenance, and defend against malicious packages.

Threat-model a design with STRIDE: draw the data-flow diagram and trust boundaries, walk STRIDE per element, rank threats by likelihood×impact, and map each to a mitigation or a routed accepted-risk.

Run a self-storage facility's operations — choose the operating model (staffed vs hybrid vs remote-unmanned + kiosk) against the site's volume and labor market, set the staffing, harden security and access control (gate/keypad, individual door alarms, cameras with retention, lighting, overlock discipline), keep climate control, maintenance, and curb appeal to standard, protect the move-in/move-out flow (agreement, protection-plan and autopay offer, gate-code provisioning, overlock-release), a...

Turn a self-storage facility's occupancy and rate picture into a revenue plan by reading physical vs economic occupancy, comparing street rate to in-place rate by unit type, designing the ECRI program (existing-customer rate increases — cadence, increase size by tenure and gap, churn guardrail), setting dynamic-pricing floors and ceilings, rebalancing the unit mix, and pricing promotions against the ECRI that recovers them — returning the recommended moves with projected NOI lift and the cond...

Run a self-storage tenant from first missed payment to lien auction as a disciplined, state-specific process — start with prevention (autopay enrolment, late-fee discipline), then walk the statutory lien timeline (late fees → gate lockout/overlock → pre-lien and lien notices → advertising/public notice → auction via StorageTreasures/Lockerfox → sale of goods → surplus handling), flagging at every step that lien law varies by US state, attaching the state and a retrieval date, and marking the ...

Read census as a flow of move-ins, move-outs, and length of stay, not a point number, so the right lever is pulled. Reach for this on any occupancy question.

Build acuity-based pricing that captures the care cost by level, instead of a flat rate, to protect margin. Reach for this on a pricing question.

Read labor cost, agency reliance, and turnover as quantified unit economics, since they drive both margin and quality. Reach for this on a cost question.

Read survey readiness, incidents/falls, and quality measures as existential operational risk, as decision-support. Reach for this on a quality question.

Build a staffing model on acuity-weighted hours-per-resident-day, not a fixed ratio, so labor matches need. Reach for this on a labor question.

Decompose a workload into functions and events for a serverless/event-driven design — the serverless-vs-container-vs-managed-service call (and where serverless is the WRONG choice: steady high-throughput, long-running, tight-latency, pooled-RDBMS), sync-vs-async boundaries per interaction, orchestration (state machine/saga) vs choreography (event bus), the event schemas & contracts, serverless-friendly storage vs a connection-pool-hostile RDBMS, and the dual-write/outbox fix — designed around...

Harden a serverless function/pipeline for the runtime & ops realities — cold starts (causes, the provisioned/warm-concurrency vs package-slimming trade-off against the latency budget, and what NOT to over-provision), concurrency & account/region limits & throttling with downstream (RDBMS) protection, idempotency keys + exactly-once-EFFECT (delivery is at-least-once), DLQ + poison-message policy, and retry/backoff/visibility-timeout so a queue is never an infinite-retry outage. Reach for this ...

Model serverless cost and scale — a per-invocation cost model (invocations × duration × memory + requests + data-transfer + downstream), the serverless-vs-container crossover point where steady high-throughput makes always-on cheaper (and 'serverless is cheaper' stops being true at scale), and concurrency/quota/limit planning (account/region caps, reserved/provisioned concurrency, throttle headroom). Reach for this on 'is serverless actually cheaper here?', 'where do we cross over to containe...

Design a Shopify build from who-uses-it and does-it-ship-to-the-App-Store backward: the app type (custom vs public vs theme/extension), the integration surface (Admin GraphQL API, webhooks, App Bridge/Polaris embedded UI, extensions), the current-generation customization path (Shopify Functions + checkout UI extensions, never script tags / checkout.liquid), the metafields/metaobjects data model, the storefront choice (Online Store 2.0 theme — the default — vs Hydrogen/Storefront API headless)...

Make a Shopify build correct, secure, and App-Store-review-ready: HMAC-verify every webhook + process idempotently + fast-200-async, implement the mandatory GDPR/data webhooks (customers/redact, shop/redact, customers/data_request), authenticate embedded requests with session tokens (not cookies) over OAuth, charge through the Billing API, handle GraphQL cost-based rate limits with back-off + bulk operations (never a hot pagination loop), pin the Admin API version, and build the current-gener...

**Status:** Pattern **Domain:** Skilled trades contracting / field operations **Applies to:** `skilled-trades-contracting` ---

Build a flat-rate price book from loaded labor and real material cost with good/better/best options, so service pricing protects margin. Reach for this on service pricing.

Build a billable labor rate that absorbs wage, burden, vehicle, tools, insurance, and overhead, so every hour sold makes money. Reach for this before any estimate or flat-rate book.

Read first-time-fix and quantify the callback labor cost, then fix truck stocking and diagnosis, since a callback is a free truck roll. Reach for this when callbacks are high.

Read the billable-hour ratio and cut non-billable drive, restock, and rework time, since billable efficiency is the field's master number. Reach for this on a productivity question.

Read close rate and average ticket and option-presentation, since they move revenue more than lead volume. Reach for this before spending on marketing.