Claude Skills by mcorbett51090

Model RI/Savings-Plan coverage on the rightsized baseline, balancing discount vs utilization risk. Reach for this on a commitment question.

Compute cost per customer/transaction/feature and read the trend, not the gross bill. Reach for this on a scaling-health question.

Architect money-safe payments: represent money as integer minor units + currency (never floats), keep a double-entry append-only ledger as source of truth (the PSP is an integration you reconcile against), design a money-event model, and reconcile continuously.

Step-by-step playbook for reconciling your internal double-entry ledger against the PSP's payout and transaction reports — identifying discrepancies, classifying them, and closing the books with confidence.

Minimize PCI-DSS scope (engineering posture): use PSP client-side tokenization so the raw PAN never touches your servers (SAQ-A), reduce scope ruthlessly, log money operations for audit without ever logging card data, and route attestation/regulation/verdict out.

Integrate a PSP correctly: idempotency key on every money operation (charge/refund/payout), verify webhook signatures and handle them idempotently + out-of-order, model the charge state machine explicitly, and handle 3DS/SCA and hard-vs-soft declines.

Build subscription/usage billing: model plans and prorate mid-cycle changes correctly, meter usage idempotently, run a reliable recoverable billing-cycle job, recover failed payments with smart dunning, and emit clean revenue events for finance.

Grow the margin dues can't reach: personal training, small-group/semi-private, retail, and café/juice-bar revenue per member. Read revenue-per-member and contribution margin by line, and sequence ancillary growth on the retained base. Attach and margin benchmarks are verify-at-use.

Build and read a fitness class grid: fill rate by slot and class type, the per-class break-even headcount from instructor pay plus room cost, instructor utilization, and the no-show/waitlist mechanics that reclaim held seats. Fill and instructor-pay benchmarks are verify-at-use.

Build the first-30-days onboarding and the attendance-signal early-warning system that keep members: first-visit-at-signup, an early-frequency target, a check-in cadence, and a churn-save flow that matches the offer to the cancel cause instead of reflex-discounting. Retention benchmarks are verify-at-use.

Read a fitness membership base as a subscription business: net member movement (joins minus churn), the retention/survival curve, member LTV = ARPU / churn, and the leaky-bucket diagnosis that tells you whether to fix acquisition or retention first. Churn/LTV benchmarks are verify-at-use.

Build CPM from fixed and variable components, isolating fuel and the non-fuel marginal, so the cost is visible where it lives. Reach for this on any margin question.

Read the operating ratio (expenses ÷ revenue) as the survival headline and decompose it before acting. Reach for this on any profitability question.

Read driver turnover as a quantified unit-economics cost across recruiting, training, and unseated trucks. Reach for this when turnover is high.

Read empty miles and truck utilization and build a routing/backhaul plan to lift the loaded-mile ratio. Reach for this when rate-per-mile looks fine but margin doesn't.

Run a PM program against maintenance CPM and downtime so a deferred PM doesn't become a roadside failure. Reach for this when repair costs rise.

Design the intake behind a form so triage is deterministic: request taxonomy, the fields each request type actually needs, routing rules, per-type response clocks, self-serve-vs-escalate bright lines, and abandonment read as a process defect stream. Produces a form spec, not a wireframe.

Define a form's measurement contract before instrumenting it: which events, which denominator, what counts as a defect, how per-field drop-off lies, and how to hand an individuals series to statistical process control without manufacturing false signals on a low-volume form.

Walk the trust boundary of a form submission on the server: client/server validation parity, honeypot design and its assistive-tech exemption, double-submit and submission idempotency, webhook signature verification, PII minimisation. Cites ravenclaude-core for uploads and challenge widgets; the binding verdict always routes to security-reviewer.

Make the neutral forms guidance executable on the RavenPower stack: the ordered authority chain for a public write, where the challenge check sits, which fail directions are chosen, and the four honest gaps a reader must re-verify before relying on them.

Build a royalty-loaded unit-economics model for a franchise unit: revenue with royalty + ad-fund + fees taken off the top, then COGS / labor / occupancy / other opex to a unit profit and a break-even, plus total investment and months-to-ramp — so a buy/expand decision rests on bottom-up numbers, not the brand's Item-19 headline. Reach for it before any franchise buy or expansion. Used by `franchise-operations-strategist` (primary). Not investment advice.

A decision-focused read of a Franchise Disclosure Document: what the key Items mean for a buy decision — fees (Items 5-6), total investment (7), restrictions & territory (8/11/12), the Item 19 FPR's scope/cohort/exclusions, and turnover/litigation/bankruptcy (3/4/20) — as franchisee literacy, explicitly NOT legal advice (binding review -> legal-ops-clm). Reach for it when someone hands you an FDD. Used by `franchise-operations-strategist` (primary).

Run a repeatable brand-standard audit across franchise units and turn it into a coaching loop: a weighted checklist tied to the franchise agreement's operating standards, a scored audit per unit, the specific gaps framed as contract risk, and a coach-and-re-audit cadence. Reach for it to keep quality consistent across locations and protect the license. Used by `multi-unit-performance-manager` (primary).

Veteran reference for building an accurate all-in freight quote — air chargeable weight (IATA 1:6000 volumetric vs actual), ocean CBM and weight/measure ton, the full ocean + air surcharge stack (BAF, CAF, THC, LSS, GRI, PSS, ISPS, AMS/ENS, DDC), margin methods (on-cost vs on-sell), and validity/volatility handling. Consulted by freight-rate-quoter.

Veteran reference for Incoterms 2020 in a sales context — all 11 terms, the cost vs risk transfer point of each, the who-pays-what responsibility matrix, the 7 any-mode vs 4 sea-only split, named-place discipline, and the recurring quoting traps (FCA vs FOB for containers, CIP vs CIF insurance, DDP duty/VAT exposure). Consulted by trade-lane-compliance-advisor.

Veteran playbook for freight-sales pipeline and forecast discipline — stage definitions tied to buyer behavior, coverage ratio, sales velocity, weighted vs commit vs best-case forecast, the deal-inspection checklist, single-threaded-risk flags, and the long multi-stakeholder logistics cycle (6 to 18 months). Consulted by pipeline-forecast-coach.

Veteran playbook for freight new-business prospecting — ICP definition for shippers, trigger-event sourcing, the 8-touch multi-channel sequence (email / call / LinkedIn), the value-first message framework (problem to lane-proof to ask), the low-risk wedge for happy-with-current-forwarder, objection handling, and channel mix. Consulted by prospecting-outreach-strategist.

Veteran playbook for freight key-account work — the QBR agenda and deck structure (partnership recap, value delivered, honest assessment, next-quarter goals, joint action plan), the account-plan template (relationship map, whitespace, growth plays, risks), service-recovery, incumbent defense, and the account-health read. Consulted by key-account-manager.

Veteran playbook for freight RFQ/RFP/tender response — RFQ vs RFP vs RFI, the qualify-or-decline scorecard, the four operational drivers of quote win-rate (speed, accuracy, optionality, margin consistency), the lane rate-matrix format, the bid-narrative structure, give-get on price, and follow-up cadence. Consulted by rfq-tender-strategist.

Actionable checklist and fix patterns for WCAG 2.1 AA compliance in React apps — automated scanning, keyboard navigation, focus management, ARIA usage, color contrast, and the most common component-level failures.

Make a frontend fast to a budget: analyze and code-split the bundle by route, lazy-load heavy/below-the-fold, optimize images/fonts, minimize hydration (RSC/islands), kill render-blocking and request waterfalls, and tune the Core Web Vitals (LCP/INP/CLS) against field data.

Architect frontend state: treat server data as a cache (TanStack Query/SWR/RSC), place client state at the narrowest workable scope (local -> context -> store), invalidate deliberately, use optimistic updates with rollback, and derive rather than duplicate.

Build composable, accessible React components: small components with clear props (composition over a flag-laden mega-component), correct hooks (complete deps, no stale closures, effects only for external sync), controlled validated forms, and accessibility in the markup.

Choose the rendering strategy per route: SSG/ISR for static content, SSR/RSC for personalized or SEO-critical pages, CSR for behind-login interactive shells; default to server components and hydrate only interactive islands to minimize shipped JavaScript.

Audit a funeral home's pricing and disclosures against the FTC Funeral Rule and clear the cremation-authorization and vital-records gates. Check the General Price List, Casket Price List, and Outer Burial Container list for required disclosures and itemization (no forced packages, embalming-not-required, telephone-price disclosure, no misrepresentation); confirm the cremation authorizing agent, positive ID, written authorization, and unbroken chain-of-custody before any irreversible step; and...

Read and manage the funeral-home case-flow pipeline (first call → removal/transfer → arrangement → preparation → services → billing → aftercare), find the constraint stage that gates throughput, size staffing and on-call/removal capacity against call volume, decide build-vs-contract for removals or preparation, and produce the fulfillment plan for the arranged services — all while protecting the family experience, not just the margin. Reach for this when the user asks "why are families waitin...

Run a grief-aware, FTC-Funeral-Rule-compliant arrangement — from first-call intake through the arrangement conference to documented, itemized selections and disposition. Traverse the deathcare-compliance decision tree so the right disclosures (GPL, CPL, Outer Burial Container list, telephone-price, embalming-not-required, no-misrepresentation) are given at the right moment, itemize without forcing a package, select the disposition and its requirements, and capture it in the arrangement worksh...

Design the economy as a system of sources, sinks, and progression pacing, not a price list, so it doesn't inflate or starve. Reach for this on an economy question.

Track and burn down the riskiest unknowns (fun, tech, content cost) first, not just a task list, since scope kills games. Reach for this on the production plan.

Design the second-to-second and session-to-session core loop before features, since retention lives there. Reach for this at the start of design.

Read retention (D1/D7/D30) and monetization together, gating monetization on retention, to operate the live game. Reach for this post-launch.

Scope the project to a vertical slice that proves the core loop is fun before scaling content, to de-risk the build. Reach for this at greenlight.

Choose GCP compute by operational burden: Cloud Run (default for stateless containers/HTTP, scale-to-zero), GKE/Autopilot (k8s/portability), Cloud Run functions (small event handlers), GCE (legacy); design Pub/Sub integration with idempotency + dead-letter topics.

Playbook for setting up GCP billing visibility and cost controls — billing export to BigQuery, budget alerts, label-based attribution, committed-use discounts, and the common cost leaks to eliminate first.

Write least-privilege GCP IAM: predefined/custom roles over primitive (Owner/Editor/Viewer), service accounts + Workload Identity Federation instead of exported key files, IAM Conditions, and binding at the correct hierarchy level.

Design private-by-default GCP networking: Shared VPC for multi-project, default-deny firewall targeted by tag/service-account, Private Google Access + Private Service Connect, and Cloud NAT for controlled egress.

Design the GCP resource hierarchy: organization -> folders (env/dept) -> projects (app/workload), and set org-policy constraints (allowed regions, disable SA key creation, no external IP, OS Login) high in the tree for inheritance.

Condition generation on a brand: consume brand tokens from whatever source is present (a DTCG design-token file OR ravenclaude-core:brand-extraction's brand.json), assemble a 3-10 image style-reference / Recraft brand-style upload, then post-overlay the exact brand hex rather than trusting the model's color memory. Style-reference beats seed-pinning. This plugin CONSUMES tokens; it does not produce them.

The mandatory ship gate: brand-hex/style conformance, anti-slop QA (garbled in-image text, hands/anatomy, off-brand drift, no baked-in text), AI-drafted + human-reviewed WCAG 2.2 alt text (decorative -> alt=\"\"), and a mandatory human curation sign-off. No asset reaches production without a curation artifact — this gate is a hard blocker, not a suggestion.

Keep generation spend a design input, not a surprise: route a cheap draft before a premium final, set a per-project generation budget cap, log each spend line (you supply the unit price — every provider price is [unverified]), and fail loudly when the cap is exceeded. Backed by gen-budget.py (stdlib, no baked-in prices) and /check-generation-budget.