Claude Skills by mcorbett51090

Model an illustrative net staking APR and annual reward — clearly NOT financial advice. Reach for this on a yield or reward question.

Profile gas and cut the dominant costs — storage writes and loops — then estimate the user-facing cost. Reach for this on a cost or UX-cost question.

Decide deliberately what lives on-chain vs off-chain on cost and privacy grounds. Reach for this on any data-placement question.

Build the threat model beyond code — oracle, flash-loan, and MEV economic surface. Reach for this on a 'can we be drained?' question.

Compile the finished brand system into a dynamic brand-book hub (logo rules, color tokens, type, voice, imagery, usage do/don'ts), DELEGATE the token build to web-design:design-tokens-scaffolding, spec the favicon/OG asset set, and enforce the legal-sign-off precondition (can't mark client-ready without the curation + authorship log and every IP/font claim routed to security-reviewer). Hands the finished system to web-design:visual-designer.

State the load-bearing brand-IP facts (AI-logo copyright ≠ trademark; documented human authorship; font web-license class OFL/Adobe/Monotype; provider indemnity) and route EVERY client-facing IP / registrability / font-license claim to ravenclaude-core:security-reviewer and counsel. Not legal advice — states facts, never conclusions; recommends a TM clearance search before promising trademarkability.

Author the brand strategy substrate BEFORE any visual generation — a discovery questionnaire → positioning statement, value proposition, target audience, and archetype — then bulk-draft business/product names + taglines and hand a human-curated shortlist. Owns the strategy-before-visuals gate artifact. Naming availability + trademark collisions route to security-reviewer; not legal advice.

Build the verbal identity — a voice platform (3–5 attributes, tone-shift rules by context, do-say/don't-say pairs, a term glossary) and a messaging hierarchy (tagline, elevator, value pillars). The half of the brand book a logo tool skips; authored from the strategy brief, applicable by someone who isn't the author.

Direct the visual identity: author the anti-slop creative brief for generative-web-media (setting indemnity_required), run the human-curation + documented-human-authorship gates, and spec the logo suite (lockups/clear-space/min-size/mono/B&W), color roles with WCAG-AA pairs, and type with web-license class. Refuses without a strategy brief. The curated vector is the deliverable — never regenerated in Firefly.

End-to-end workflow to build a Manifest V3 browser extension: decide which context owns each piece of logic (content script vs MV3 service worker vs injected page script vs popup/options), wire messaging between contexts, request the narrowest permissions (activeTab -> optional -> host -> all_urls), and pass Chrome/Edge/Firefox store review. Complements the manifest-permissions-audit and store-submission-readiness skills. The popup/options UI seams to frontend-engineering.

Audit a browser extension's manifest.json against the least-privilege bar and Manifest V3 conformance: every permission and host match justified, activeTab/optional-permission opportunities, no remotely-hosted code, scoped web_accessible_resources, and the store-review risk each entry carries. Reach for this before a store submission, after a permissions rejection, or when reviewing an inherited extension.

A pre-submission readiness checklist for shipping a browser extension to the Chrome Web Store, Edge Add-ons, and Firefox AMO: required listing metadata, the privacy + permissions justification, single-purpose conformance, data-disclosure forms, and the common rejection reasons to pre-empt. Reach for this before a first submission, after a rejection, or when adding a new store target. Store-policy specifics are volatile — verify against current store docs.

Build a defensible COGS-allocation framework under 280E, as decision-support for the CPA, so only properly-capitalized cost reduces taxable income. Reach for this on any tax-burden question.

Anchor every compliance answer to the specific state and date, since track-and-trace, testing, potency, and tax all vary. Reach for this on any compliance claim.

Read inventory turns as both a cash and a compliance metric, flagging aged and perishable product. Reach for this on a cash or expiry question.

Reconcile physical inventory to the state track-and-trace system and resolve discrepancies as compliance events, not bookkeeping. Reach for this on any traceability question.

Read category margin, basket, and turns and lift store profit without discount-driven traffic. Reach for this on a store-margin question.

Pick and place the right resilience patterns for a given failure mode — the timeout / retry+backoff+jitter+budget / circuit-breaker / bulkhead / load-shedding / graceful-degradation / fallback / idempotency / backpressure decision. Start from an FMEA, choose the pattern that defends the NAMED failure, and defend the pattern's OWN failure mode. Reach for this when the user asks 'what do we add so a slow/failing dependency doesn't take us down?', 'is a naked retry safe here?', or 'where are our...

Facilitate a game day end to end — the scenario, the roles (facilitator / operators / observers / scribe), the comms plan, the abort criteria, a scoring rubric, and the follow-up remediation backlog. Game days test PEOPLE and RUNBOOKS under a controlled failure, not just systems — the cheapest way to find the org's real failure modes. Reach for this when the user asks 'run us a game day for X', 'how do we do a failure drill', or 'test our on-call/runbooks against an outage'. Driven by `chaos-...

Run the full chaos-experiment loop safely — steady-state definition → falsifiable hypothesis → the smallest disproving blast radius → inject a fault from the taxonomy → observe (metrics correlated to the injection window, under load) → abort-or-learn → remediate. Gate on the maturity check first (no steady-state observability = no experiment) and never inject without an automatic abort condition. Reach for this when the user asks 'design/run a chaos experiment for X', 'which fault do we injec...

Run the childcare enrollment funnel and waitlist: inquiry -> tour -> application -> start, with a tour follow-up cadence, waitlist worked by age band, and the waitlist converted before tuition is discounted. Enrollment fills seats; retention keeps them.

Keep every room legal continuously: child:staff ratio AND group-size cap by age (two separate limits), who counts toward ratio by qualification, and the licensing domains (staff files, health & safety, records) maintained daily. State-specific and verify-at-use.

Schedule staff to the required ratio at a cost the tuition covers: model labor as a step function that jumps a whole teacher at each ratio boundary, cover open/close and breaks in ratio, and read the ratio-driven labor cost per room against its revenue. State-specific ratios verify-at-use.

Route and collect childcare tuition on the right rail: private-pay vs CCDF/state subsidy vs blended, the parent-fee/co-pay split, authorization and attendance rules that drive subsidy payment, and reconciliation as receivables. State-specific subsidy rules are verify-at-use.

Price a compliant cash / membership / wellness-plan model for a chiropractic practice: a supportive-care membership priced to the clinical cadence and above delivery cost, the covered-active-care vs cash-maintenance boundary drawn cleanly, and the ABN/discount-compliance guardrails so a plan isn't an illegal inducement or a way to bill maintenance as active. Reach for it when designing memberships or a cash model. Used by `chiropractic-practice-lead` (primary).

Pick the CMT/E&M code for a chiropractic visit and structure the medical-necessity note: CMT by number of spinal regions treated, an E&M only when separately identifiable (with the correct modifier), and a PART-exam-based note (region + functional goal + progress) that supports the code and survives an audit. Reach for it per visit / when coding is unclear. Used by `chiro-billing-compliance-specialist` (primary). Not a coding certification — verify payer policy.

Build a defensible, phased chiropractic care plan: an acute/corrective/supportive phase structure with a visit cadence, re-exam checkpoints that re-justify continued care, functional goals, and a plan-completion target — with the insurance-vs-cash boundary drawn so covered active care and cash maintenance care don't blur. Reach for it when structuring a new patient's care. Used by `chiropractic-practice-lead` (primary).

Playbook for designing Claude Agent SDK hooks (PreToolUse, PostToolUse, SessionStart, Stop) — selecting the right event, writing the handler contract, deciding advisory vs blocking behaviour, and avoiding the four common hook anti-patterns. Owned by agent-sdk-engineer.

Playbook for allocating a Claude context window across system prompt, retrieved documents, conversation history, and tool results — with token-budget formulas, the retrieve-vs-hold decision, and the compaction triggers that prevent context overflow. Owned by prompt-and-context-engineer.

Playbook for constructing a high-signal golden evaluation set: sampling strategy, input diversity, reference-answer authoring, grader pairing, and the minimum-viable size thresholds that make a delta meaningful. Owned by eval-engineer.

Playbook for designing a cost-optimised model routing ladder: classifying request complexity, wiring the triage→escalate flow, measuring cost-per-resolved-task, and avoiding the common over-provisioning traps. Owned by claude-app-ops-engineer and claude-solution-architect.

Gate-by-gate checklist for shipping a production MCP server: transport selection, tool-schema quality, auth wiring, error-response contract, and the security hand-off items that must escalate to core/security-reviewer. Owned by mcp-and-server-tools-engineer.

Step-by-step playbook for diagnosing a low cache hit rate, finding the breakpoint placement errors that cause it, and correcting them. Covers TTL tradeoffs, pre-warming, tool-definition stability, and the per-model minimum-token floors.

Playbook for designing Claude tool definitions (name, description, JSON Schema input_schema) that maximise correct invocation, minimise hallucinated arguments, and produce clean structured output. Covers naming conventions, description prompting, schema constraints, required vs optional fields, and the forced-tool-call pattern.

Design a CLI's command/subcommand surface, flags vs positionals, and config precedence (flags > env > file > default), then pick the idiomatic parser for the language. Use when starting a CLI or reworking a messy one.

Plan how a CLI ships and updates — single static binary vs runtime package, cross-compilation, install channels (Homebrew/Scoop/winget/npm/pipx), a build-stamped --version, and a safe installer. Use when making a tool installable and keeping it current.

Define a CLI's output contract — human by default, --json on demand, data to stdout, diagnostics to stderr — and an exit-code map treated as a public API. Use when a tool must serve both humans and scripts, or CI keeps passing on real failures.

Generate shell completions (bash/zsh/fish/PowerShell) from the parser and design config-file discovery + env-var conventions (XDG, TOOL_* prefixes). Use when adding tab completion or a config/env layer to a CLI.

Decide whether a full-screen TUI is warranted (vs a scriptable CLI), pick the framework (Ink / Bubble Tea / Textual / ratatui), and design the render-loop + non-TTY fallback. Use for interactive terminal dashboards, pickers, and wizards.

Sequence site selection, contracting, and start-up as the schedule's critical path to cut the activation delay. Reach for this when sites are slow.

Build retention into visit burden, schedule, and engagement to lower the ~30% dropout, instead of re-recruiting. Reach for this when dropout threatens the timeline.

Plan recruitment as a costed funnel with a cost per stage, against the per-patient economics, instead of a hope. Reach for this on any enrollment plan.

Read documentation completeness, data quality, and eCTD structure throughout the trial so the filing isn't a final-month scramble. Reach for this before a milestone.

Stress-test eligibility criteria against the addressable population and site capacity before the protocol locks, since restrictive criteria are the biggest enrollment killer. Reach for this at design.

Playbook for planning and executing a safe Kubernetes control-plane and node-pool upgrade, covering version-skew rules, pre-flight checks, node drain sequencing, and capacity planning for node pools. Prevents the most common upgrade-day outages.

Build a small, safe container for Kubernetes: multi-stage with a distroless/minimal base, non-root UID, digest-pinned base, dropped Linux capabilities, and a read-only root filesystem.

Step-by-step guide for authoring a production-grade Helm chart from scratch — directory layout, values design, template hygiene, helpers, chart tests, and lint/security gates — so workloads are packaged reproducibly and safely promoted across environments.

Design cluster networking: Gateway API ingress for north-south, and a service mesh ONLY when it earns its complexity (mTLS-everywhere, traffic-splitting, per-call resilience). Wire mTLS, weighted canary routing, and resilience deliberately.

Operate a safe multi-tenant cluster: namespace-per-tenant with scoped RBAC (no workload cluster-admin), default-deny NetworkPolicies, resource quotas/LimitRanges, policy admission control, and tested PDB-respecting upgrades.

Design a Kubernetes workload: choose the workload kind by statefulness, set the three probe types correctly, requests/limits with the resulting QoS class, HPA/VPA on a load-tracking signal, and a PodDisruptionBudget.