Claude Skills by mcorbett51090

Pre-publish checklist and design guide for Terraform/OpenTofu modules — covers interface design, input validation, output documentation, for_each patterns, version pinning, and testability.

Gate infrastructure with policy-as-code: evaluate the Terraform plan JSON with OPA/Conftest (or Sentinel) to reject misconfigurations — public exposure, wildcard IAM, missing tags, unencrypted resources — before apply, preventively.

Safe procedure for Terraform state manipulation — covers import, mv, rm, and state-split operations with pre/post verification steps and the rollback strategy for each operation.

Design safe remote Terraform/OpenTofu state: remote backend with locking, encryption, and versioning; isolate state by blast radius; keep secrets out (and treat the whole file as sensitive); and do state surgery only with a snapshot.

Build the title commitment and clear it: separate Schedule B-I requirements from Schedule B-II exceptions, and decide each defect as cure vs insure-over vs except. Clear the requirements before you close; insure-over only with underwriter approval. Underwriter/jurisdiction specifics are verify-at-use.

Run the escrow endgame: confirm the commitment requirements are cleared, balance the settlement statement to the lender CD, collect good funds, close/sign, then disburse -> record -> fund in the order the jurisdiction requires. Never disburse against uncollected funds; every good-funds/recording specific is verify-at-use.

Run the title search and examination: define the search period, trace the chain of title to a reliable root, confirm the current vesting, and inventory every lien, encumbrance, easement, and prior exception. Chain of title is examined, not assumed; every underwriter/jurisdiction specific is verify-at-use.

Protect the money: verify every wire by out-of-band callback before sending, require dual authorization, reject email-changed instructions, and safeguard the escrow trust account with three-way reconciliation, no commingling, and daily oversight. Business-email-compromise sensitive; each control specific is verify-at-use.

Decide and run group vs FIT trips: FIT (individual custom) flexibility vs group-block economics (room block, deposit, cutoff date, attrition, tour-conductor benefit). Build the block before you sell against it, and manage the deposit/cutoff/attrition liabilities. Contract terms are verify-at-use per supplier.

Turn a travel brief into a structured, bookable, transparently-quoted itinerary: structure before price, itemize net/commissionable cost + service fee + taxes + insurance, attach the per-supplier cancellation/penalty schedule (verify-at-use), and document every element. No traveler PII in the artifact.

Run travel disruption and service recovery: triage the failure, rebook the traveler fast, escalate to supplier/insurance, decide goodwill deliberately, and document every change. A well-run recovery protects the traveler and earns the repeat booking. Supplier remedies and insurance terms are verify-at-use.

Make earned margin real: maintain a booked-vs-paid commission ledger by supplier, chase gaps on a cadence, handle net vs commissionable pricing correctly, understand BSP/ARC air settlement, and steer the mix to preferred-supplier/consortia programs. Commission terms are verify-at-use per supplier agreement.

Build a cash position + rolling forecast and a liquidity plan by traversing the treasury decision tree (cash position → forecast method (direct/receipts-and-disbursements vs indirect) → 13-week build & drivers → variance loop → minimum-cash/buffer sizing → committed vs uncommitted facility mix), then return the daily cash position, the 13-week forecast, the buffer target (stress-tested), the facility/revolver plan, and the conditions that resize it. Reach for this when the user asks 'build ou...

Design an FX or interest-rate hedge by traversing the treasury decision tree (scope the exposure: transaction vs translation vs economic → decide hedge-vs-accept → set hedge ratio & horizon → choose the instrument: forward/swap/option/collar → set the hedge-accounting stance: ASC 815 / IFRS 9, cash-flow vs fair-value), then return whether to hedge, how much and how long, the instrument, the accounting designation with documentation/effectiveness, and the conditions that flip it. Reach for thi...

Optimize working capital and harden the payments flow by traversing the treasury decision tree (cash-conversion cycle: DSO/DIO/DPO levers → DPO extension vs supply-chain finance / dynamic discounting → DSO reduction → inventory financing → payment-method choice → payment fraud controls: positive pay, dual auth, SoD, BEC), then return the working-capital levers ranked by cash freed, the payment-method recommendation, and the fraud-control setup. Reach for this when the user asks 'how do we fre...

Design an abuse/fraud/spam detection pipeline — inventory signals, decide rules vs. ML (or hybrid), wire signal → score → threshold → action/reviewer-queue, and set the operating point from a precision/recall tradeoff. Reach for this when the user asks to catch an abuse type, choose signals, or route to a reviewer queue. Used by abuse-detection-engineer (primary).

Design a content-moderation policy from scratch — a policy taxonomy (categories + severity tiers), a proportional enforcement ladder (warn / limit / remove / ban), and a real appeal path — by traversing the enforcement decision tree. Reach for this when the user asks to design or review a moderation policy, or to map a violation to an action. Used by trust-safety-policy-lead (primary).

Build the Trust & Safety measurement frame — prevalence (not just volume), enforcement precision/recall, time-to-action SLA, and appeal-overturn rate — with the formulas and the applied-statistics seam for eval validity. Reach for this when the user asks what to measure, whether moderation is working, or how to read a high overturn rate. Used by trust-safety-policy-lead + abuse-detection-engineer.

Frame a fuzzy research ask into a researchable question, run the research-theater gate (is this a real question or a decision already made?), select the method (generative/evaluative, qual/quant, attitudinal/behavioral, moderated/unmoderated) from the question rather than the reverse, size the sample to the claim it must bear (directional ~5 vs statistically-powered), plan the recruit/screener/incentive/panel, set the informed-consent + data-minimization + de-identification + retention ethics...

Design and run the study without contaminating it — protocol & task design (goal-based tasks, not step instructions), think-aloud and non-leading moderation (open probes, silence, 'tell me more' — never 'was that easy?'), usability-test instrumentation (task-success criteria + severity ratings), survey design that avoids leading, double-barreled, and social-desirability-loaded items, and clean data capture that keeps what participants DID separate from what they SAID. Reach for this when the ...

Turn raw notes into evidence-weighted, bias-checked, prioritized, decision-ready insight — affinity/thematic analysis, keeping observation ('6 of 8 abandoned at step 3') strictly separate from interpretation ('because the CTA is unclear'), weighting each finding by evidence strength (n, consistency, behavioral vs attitudinal, directional vs conclusive), ranking by severity, actively seeking disconfirming evidence, and ending every insight in a prioritized recommendation tied to a decision. Gu...

Build an evidence-aligned, standardized care protocol as decision-support for the licensed DVM, to reduce unwarranted variation. Reach for this on a common presentation worked up inconsistently.

Read practice revenue as production per DVM and average client transaction × visits, never one alone, so a revenue problem is diagnosed correctly. Reach for this on any revenue question.

Read recommended-care acceptance as a communication metric and raise it, instead of treating it as fixed demand. Reach for this when acceptance of dentals/diagnostics/preventives is low.

Reprice fees from the cost-of-service stack and medical value, not the neighbor's prices, to recover margin without losing position. Reach for this when margin erodes despite volume.

Find the doctor bottleneck and fix the appointment template so a fully-booked practice can grow throughput. Reach for this when revenue is flat despite full demand.

Measure the real diversion rate from weigh tickets, diagnose the MRF & recycling commodity economics by grade (OCC/cardboard, PET, HDPE, aluminum, mixed paper — post-National-Sword bale prices), attack the contamination rate that decides the P&L, and set the pricing response (commodity-share vs processing/tip-fee) against the mandates in force (SB 1383 organics, EPR packaging, landfill bans). Reach for this when the user asks "what's our real diversion rate?", "our MRF revenue is underwater",...

Choose the disposal path (direct-haul to a Subtitle D landfill vs consolidate through a transfer station) and manage its economics (tipping fees, landfill airspace, leachate/gas) and its RCRA Subtitle D compliance, scale/weigh-ticket controls, and DOT/CDL + hopper/backing/lifting safety program — while routing hazardous Subtitle C streams OUT of scope. Reach for this when the user asks "landfill direct or through a transfer station?", "manage tipping fees / airspace", "stay Subtitle-D complia...

Raise route density and cut cost-per-stop for a collection territory by measuring stops-per-hour and windshield time, sequencing and balancing routes, choosing static vs dynamic routing (RouteWare / Routeware-AMCS / Trux), and matching the fleet mix (front / rear / side-load ASL / roll-off, RNG/EV) to each stream. Reach for this when the user asks "how do we get more stops per hour?", "static or dynamic routing?", "cut windshield time", or "what truck for this stream?". Used by `route-and-div...

Separate AUM growth into net new flows vs market and compute the organic growth rate. Reach for this on a growth question.

Model tiered-fee revenue and the blended fee, flagging inconsistent application. Reach for this on a fee or revenue question.

Segment clients by revenue net of cost-to-serve and find breakeven AUM — not AUM alone. Reach for this on a client-value question.

Size advisor capacity in households per advisor and treat over-capacity as a leading retention risk. Reach for this on a capacity question.

Track the ADV/review/disclosure cadence as an operational schedule — not legal advice. Reach for this on a cadence question.

Score a scaffolded commerce integration against the seven-dimension gold-standard rubric and run the BUILD-measure-fix iteration loop until it passes. Use after scaffolding a provider track, before calling it done. Each dimension is a falsifiable test; a live provider-sandbox test is required beyond the static checks.

Understand and extend the thin shared contract every provider track implements — the payment-lifecycle interface plus advertised capabilities. Use when adding a provider, wiring a track to the contract, or deciding what belongs in the shared seam vs a track. The ONLY cross-provider abstraction; catalog/cart/inventory are track-specific.

Reconcile online inventory/catalog with an in-store POS (Square), keeping the POS as the source of truth. Use when a storefront's online store must mirror in-store stock. One-way sync driven by catalog/inventory webhooks, de-duped by event id — never bidirectional. Square-specific; Shopify inverts and Stripe has no catalog.

Choose the commerce provider (Stripe / Square / Shopify) and the tier (static hosted-checkout vs framework embedded-SDK) for a site, then point at the right template set. Use at the START of any commerce integration, before scaffolding. Routes on how the merchant's inventory truth already lives and the site's runtime.

Harden a commerce webhook handler: verify the provider signature with a constant-time compare BEFORE parsing the body, then de-duplicate retried deliveries by provider event id. Use when writing or reviewing any Stripe/Square/Shopify webhook receiver. Two invariants (verify-before-parse, event-id idempotency) that are non-negotiable.

URL: https://github.com/danium/astro-frontend-developer-skill Retrieved: 2026-09-01 Type: GitHub repo (Claude Code / Codex Agent Skill) **Verification note:** WebSearch returned no hits for this repo (too new — created 2026-08-31 per `api.github.com`). WebFetch's own summarizer produced plausible-looking but unverified content on first pass, so ground truth here is `curl` against `api.github.com/repos/...` (HTTP 200, real repo metadata) and `raw.githubusercontent.com/.../main/README.md` and `...

URL: https://github.com/nextlevelbuilder/ui-ux-pro-max-skill Retrieved: 2026-09-01 Type: GitHub repo (Claude Code skill, UI/UX quality)

WCAG 2.2-aligned accessibility audit — semantics, ARIA, keyboard navigation, color contrast, focus management, motion preferences. Severity guide + tooling notes. Used by `accessibility-auditor` (primary).

Author a project's generation-time brand-voice contract (brand-guidance.md) — a named aesthetic, a two-typeface max, a tiny palette, a 4px spacing scale, a motion philosophy, and a project-scoped anti-pattern catalogue that bans the recurring "AI slop" patterns (generic-sans brand faces, indigo gradients, 3-card grids, card-in-card, stock-photo 100vh heroes) by default. Loaded into context before every page-generation call — the tokens answer "what are the values," this answers "how does an a...

Design and implement an Intercom-style card / "tile" UI — discrete soft-shadowed rounded surfaces on a calm monochromatic canvas, in a multi-pane (navigation-rail + content) layout, with a single restrained accent used only as hairlines, outlines, and occasional text. Used by `visual-designer` (primary) and `frontend-implementer` (token-to-code wiring). Invoke when a brief asks for a "card", "tile", "panel", "Intercom-style", "dashboard-like", or "clean SaaS" surface, or when restyling an exi...

Audit existing site content — full inventory (URL × type × intent × last-updated × owner), scoring against business / user-need / SEO criteria, remediation queue (keep / consolidate / rewrite / retire), and the migration plan when re-platforming. Reach for this skill at the start of a re-platform, before an SEO push, or when content quality has stopped predicting conversion. Used by `content-strategist` (primary) + `web-architect`.

Design and audit conversion-focused screens — funnel definition, friction-vs-trust balance, form field selection (every field is a cost), one CTA per screen discipline, social-proof placement, microcopy patterns, and the conversion-rate measurement plan. Reach for this skill when designing or reviewing a landing page, sign-up flow, checkout, or any "convert visitor → action" screen. Used by `ux-designer` (primary) + `content-strategist`.

Diagnose and improve Core Web Vitals (LCP / CLS / INP). Includes a Mermaid decision tree for root-cause triage across all three vitals + canonical fix-by-symptom map. Field data (CrUX / RUM) at p75 is the measurement target. Used by `performance-engineer` (primary).

Audit an existing brand / design system for consistency, completeness, token coverage, dark-mode readiness. Used by `visual-designer` (primary) + `frontend-implementer` (token-to-code wiring).

Scaffold a token system from brand spec to token JSON to CSS variables to framework theme (Tailwind / Shadcn / CSS-in-JS / Theme UI). Includes naming convention, scale design (color / spacing / typography / radius / shadow / motion), light/dark mode, semantic vs primitive tokens, and the dual-mode build pipeline. Reach for this skill when launching a new design system or when an existing system has "design drift" between Figma and code. Used by `visual-designer` (primary) + `frontend-implemen...

Implement a Fluent UI v9 + React website end-to-end — set up FluentProvider, turn a brand color into a BrandVariants ramp and light/dark/high-contrast themes (createLightTheme / createDarkTheme), wire design tokens, style with Griffel makeStyles, handle Next.js App Router SSR (the use-client + renderToStyleElements boundary) or Astro islands, build custom components on Fluent primitives, and ship a themed Storybook. Reach for this skill when building or reviewing a Fluent/React site, implemen...