Claude Skills by FerroxLabs

Project architecture and file structure conventions for all process types. Use when: (1) Creating new files or modules, (2) Deciding where code should go, (3) Converting single-file components to directories, (4) Reviewing code for structure compliance, (5) Adding new bridges, services, agents, or workers.

Use when bumping the Wayland version: update package.json, run checks, branch, commit, push, create PR, wait for merge, tag release.

Auto-fix GitHub issues labeled as bugs: fetch open bug issues, analyze feasibility, fix code, and submit PRs. One issue per invocation. Use when: (1) User says "/fix-issues", (2) User asks to fix GitHub issues.

Auto-fix high-frequency Sentry issues: fetch issues > N occurrences, analyze stack traces, fix code, create GitHub issues, and submit PRs. Supports user feedback issues (event.type "default") with attachment analysis (logs, screenshots) when include_feedback=true. Use when: (1) User says "/fix-sentry", (2) User asks to fix Sentry issues.

Internationalization (i18n) workflow and standards for managing translations. Use when: (1) Adding new user-facing text, (2) Creating new components with user-facing text, (3) Reviewing code for i18n compliance, (4) Adding a new translation module.

Use when creating a pull request, after committing changes, or when user invokes /oss-pr. Covers branch management, quality checks, commit, push, and PR creation.

PR Automation Orchestrator: poll open PRs, check CI, run review, fix, and merge eligible PRs. Use when: (1) Invoked by daemon via scripts/pr-automation.sh, (2) User says "/pr-automation".

PR Review Fix: automatically fix all issues identified in a pr-review report. Use when: (1) User says "fix all review issues", (2) User says "/pr-fix", (3) After pr-review skill has produced a report, (4) User wants to address PR review feedback.

PR Code Review (Local): perform a thorough local code review with full project context. Use when: (1) User asks to review a PR, (2) User says "/pr-review", (3) User wants to review code changes before merging.

End-to-end PR lifecycle: create PR, wait for CI, review, fix issues, merge - all in one invocation. Use when: (1) User says "/pr-ship", (2) User wants to ship current changes as a complete PR lifecycle, (3) User wants to resume shepherding an existing PR.

PR Verification & Merge: verify bot:ready-to-merge PRs with impact analysis, test supplementation, and one-click merge. Use when: (1) User says "/pr-verify", (2) User wants to verify and merge ready PRs.

Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.

You are a coding assistant skill for E2E testing. - Help with code generation - Support multiple programming languages - Provide code reviews

You are a test skill for E2E validation. Follow these instructions: 1. Always respond with structured JSON 2. Include a "status" field in every response 3. Support basic query operations

Generate review + photo + video prompts at the right post-delivery moment by product type. Inputs: product type (consumable / durable / cosmetic / apparel), platform. Output: prompt-timing recommendation (D+3 / D+7 / D+14 by category), template copy, incentive structure (compliant with platform anti-incentive rules), photo-prompt CTA. Trigger phrases: 'review prompt', 'UGC prompt', 'ask for a photo review', 'request video testimonial', '/commerce ugc-prompts <product-type>'.

Build a long-form About page that converts visitors into subscribers and buyers - not a bio expanded into paragraphs, but a full DR asset that hooks with the reader's problem, tells a story-of-discovery, proves the path with results, and closes with an explicit next step. Outputs a structured content brief plus paste-ready section copy. Use when a website About page exists but reads like a résumé, career history, or humble-brag parade - or when building a new About page from scratch for a per...

Write a HARO (Help A Reporter Out) or Qwoted/SourceBottle expert-source reply that gets quoted - not buried. Opens with a credentialed one-liner that answers "why this person, for this query," delivers the answer in 3-5 tight bullets with specifics and a contrarian take, and closes with a pull quote written to be lifted verbatim. Use when responding to a journalist query on HARO, Qwoted, SourceBottle, or similar journalist-source services where you have genuine expertise and a 2-4 hour reply ...

Engineer above-fold hierarchy for direct-response pages: 5-second comprehension test, hero rhythm, primary CTA placement, and visual scaffolding for the Four-Layer Open. Produces a wireframe spec + paste-ready HTML/CSS for the first viewport. Use when designing or rebuilding the top-of-page that must answer "what / who / next" in five seconds while seating Layer 1 (Nerve Strike) of the Open. Not for full-page sales-page assembly (use /convert sales-page) and not for live-URL teardown (use /ma...

Score existing direct-response copy against The Donahoe Method's 8 frameworks: Four-Layer Open, Conversational Proof, Three Locks, Bullet System, Cascade Close, Greased Chute, Voice Rules + Bullshit Filter, Market Temperature. Produces a 0-100 normalized score, dimension-by-dimension findings, and prioritized rewrite recommendations. Use when the user has existing copy (a sales page, VSL script, email, ad, opener) and wants a Method-grade audit with specific rewrite directions. Not for net-ne...

Author advertorial / pre-sell / listicle bridge pages: cold-traffic decompression content that warms the reader before they hit the squeeze or sales page. Emits brief + paste-ready HTML/CSS in editorial style. Use when the user is sending cold paid traffic that would bounce off a direct sales page and needs a content-style warm-up surface. Not for the squeeze or sales page itself (see /convert squeeze-page, /convert sales-page) and not for blog-as-content-marketing (different intent).

Generate Donahoe bullets across 4 types - Keyhole, Flip, Snapshot, Scar - mixed for rhythm. Each bullet is a miniature persuasion engine that creates a curiosity gap only the product resolves. Use when authoring the "what's inside" / "what you get" / feature section of a sales page, VSL, lead-magnet pitch, or course module list. Not for ordinary feature lists or specs (those go in plain prose) and not for headline-only generation (use convert-open Layer 1).

Coach a draft toward voice integrity - quotes the 3 weakest lines from the input draft, forces 3 alternative rewrites of each, diagnoses the dominant voice failure pattern, and returns a coaching artifact (no PASS / FAIL verdict). Use when running a final coaching pass on copy before shipping - sales pages, VSL scripts, emails, ads, headlines. Not for full Voice Rules pass (use convert-voice - Bullshit Filter is one rule of many in Voice; this is the deeper standalone coaching pass) and not f...

Author order-form bump offers: 30-80 word checkbox micro-copy that lifts AOV without breaking checkout flow. Emits brief + paste-ready HTML/CSS for the bump checkbox component. Use when the user has a checkout page and wants to add a single relevant low-friction bump above the buy button. Not for full upsell pages (see /convert oto-page) or post-purchase add-ons (see /convert cross-sell-page).

Author checkout-page micro-copy + trust signals: order summary, form-field copy, bump slot, button label, guarantee restatement, and friction-reduction patterns. Emits brief + paste-ready HTML/CSS scaffold (payment-processor-agnostic). Use when the user needs a conversion-optimized checkout page where every word and visual signal earns its place. Not for the bump component itself (see /convert bump) or post-purchase OTOs (see /convert oto-page).

Engineer the Greased Chute: open loops, paragraph length, sentence rhythm, transition curiosity, read-aloud test. Makes every sentence pull the reader into the next so the asset feels frictionless to read end-to-end. Use when a draft exists and you need to engineer momentum - kill friction at scroll-points, install open loops, vary rhythm, fix energy drops. Not for writing a draft from scratch (use convert-sales-page or convert-vsl) and not for transition-line generation alone (use convert-tr...

Build the Cascade Close: Stack → Vision → Math → Safety Net → Door, with P.S. and P.P.S. that close again from new angles. Catches every type of buyer (vision-driven, logic-driven, risk-averse, action-ready) by closing from multiple sides. Use when writing the closing block of a sales page, VSL, long-form email, OTO page, or any conversion point where the reader is being asked to act. Not for opening hooks (use convert-open) and not for offer design itself (use funnels-offer for value structu...

Author post-purchase cross-sell pages: lateral product offer to existing customer, with relevance framing and tight Method-applied copy. Emits brief + paste-ready HTML/CSS. Use when the user has a customer who completed a flagship purchase (and any OTO sequence) and a related product the customer would benefit from. Not for immediate post-checkout upsells (see /convert oto-page) or downsells (see /convert downsell-page) and not for pre-purchase cold-traffic pages.

Author OTO recovery (downsell) pages: reduced-commitment offer after an OTO decline, with explicit acknowledgment of the prior "no" and a smaller, easier yes. Emits brief + paste-ready HTML/CSS. Use when an OTO has been declined and the user wants a softer recovery offer to capture buyers who balked at the upsell price or scope. Not for the original OTO (see /convert oto-page) or cross-sells (see /convert cross-sell-page).

Develop the Fingerprint - the only-you POV / contrarian take / vivid voice moment that lives inside the Four-Layer Open and recurs across the asset. Outputs a fingerprint pack: signature moments, contrarian takes, vivid images, and seller-specific phrases that make copy unswappable. Use when copy reads "fine" but generic - when swapping the seller's name for a competitor's wouldn't change anything - and you need the distinctly-this-person voice layer. Not for the full Four-Layer Open generati...

Run the Four Questions diagnostic before any copy is written: Why You / Why Me / Why This / Why Now answered from the customer's perspective in one specific sentence each. Produces the briefing the rest of the Method writes against. Use when starting a new sales page, VSL, email, or any direct-response asset and you need a customer-perspective brief before drafting a single sentence. Not for auditing existing copy (use convert-audit) and not for writing the page itself (use convert-sales-page...

Author lead-magnet (free → email) opt-in pages: longer than a squeeze, full Method-compressed argument for why the freebie is worth the email. Emits brief + paste-ready HTML/CSS. Use when the user has a substantive free asset (guide, training, swipe file, audit, calculator) and needs a page that converts cold-to-cool traffic into email subscribers. Not for super-short single-promise opt-ins (see /convert squeeze-page) or post-opt-in delivery pages (often fold into /convert thank-you-page).

Compress the Donahoe Method into mobile-first single-column layouts: thumb-zone CTA placement, Fitts-sized touch targets, mobile reading-pattern adaptation, sticky bottom CTA, and Method-density preservation under 375px width. Use when designing or rebuilding mobile rendering of a sales page, VSL page, lead-magnet page, or any direct-response asset where mobile traffic dominates and the Method must hold without losing layers. Not for desktop-first spec (use /convert above-fold or /convert scr...

Generate Four-Layer Opens for any direct-response asset: Layer 1 Nerve Strike + Layer 2 Side Door + Layer 3 Skin in the Game + Layer 4 Fingerprint. Produces 5 ranked opens with section-by-section breakdown. Use when authoring a sales page, VSL, email, ad, or any opener that must make the reader physically unable to stop reading. Not for headline-only generation (this is a 3-5 sentence multi-layer open, not a single headline) - sub-skill of /convert sales-page when called as part of full Metho...

Author One-Time Offer pages: post-purchase upgrade with single accept/decline decision, urgency framing, and tight Method-applied copy. Emits brief + paste-ready HTML/CSS with one-click yes/no markup. Use when the user has a flagship product purchased and needs an immediate post-checkout upgrade page. Not for cross-sells (see /convert cross-sell-page) or downsells (see /convert downsell-page) and not for cold-traffic sales pages.

Build a complete sales asset end-to-end via The Donahoe Method: diagnostic → primitives → fingerprint → page → integrity-gate → visual → audit → report. Composite orchestrator that calls 14-16 sub-skills via delegate_task in an 8-phase DAG (sequential where dependencies require it, parallel where they don't). Produces a client-ready full-asset bundle. Use when the user has a product brief and wants the full agency-replacement deliverable in one run - not for single-primitive work. Not for liv...

Engineer visual proof stacks that map to the Donahoe Method's 5 proof types: testimonial layouts (text + photo + name + result), logo bars, video > text hierarchy, quote-photo-result cards, numerical proof, case studies. Specs paste-ready HTML/CSS for each pattern + placement rules across the page. Use when designing the proof zone of a sales page, VSL page, lead-magnet page, or any asset where Lock 2 (Trust) needs visual scaffolding. Not for writing testimonial copy from scratch (use /conver...

Apply Conversational Proof to any claim: claim → evidence → reason → move-on pattern, with a library of 5 proof types (Anecdote, Receipt, Drive-By, Namecheck, Because). Outputs proof-blocks woven through copy, never an isolated proof section. Use when a draft makes claims that need to be believed and you want proof that reads like conversation, not a credentials wall. Not for designing testimonial graphics (use convert-proof-stack) and not for sourcing testimonials (that's a research task, no...

Author long-form direct-response sales pages: section architecture, full body copy, paste-ready HTML/CSS, and Method audit footer. Applies The Donahoe Method top-to-bottom across 16 sections. Use when the user has a product and needs a complete sales page built from a brief - not a teardown of an existing URL. Not for auditing live URLs (use /market landing) or rewriting existing copy (use /convert rewrite). For squeeze/opt-in pages use /convert squeeze.

Orchestrate scroll depth across a long-form direct-response page: map zones to The Three Locks (Want → Trust → Excuse), engineer reading-pattern flow (F-pattern body / Z-pattern hero), place CTA anchors at decision points, and pace section transitions for The Greased Chute. Use when designing the visual flow of a sales page, VSL page, or long bridge page where each scroll position must serve a specific Method lock. Not for hero-only spec (use /convert above-fold) and not for short single-purp...

Author single-purpose opt-in (squeeze) pages: compressed Method, one promise, one form, one CTA. Emits brief + paste-ready HTML/CSS with accessible form markup. Use when the user wants email addresses in exchange for a single specific promise (lead magnet, waitlist, free training). Not for full long-form sales pages (see /convert sales-page) or the lead-magnet delivery page (see /convert lead-magnet-page).

Classify reader temperature on the 5-level scale: Ice Cold / Cool / Warm / Hot / Boiling. Sets length, depth, education burden, and approach for every other Method primitive that follows. Use when starting a new asset and you need to calibrate how much teaching, proof, and persuasion to load before writing. Not for auditing an existing asset's tone (use convert-audit) and not for designing the offer (use funnels-offer).

Author thank-you pages with a deliberate secondary-offer stack: deliver the promised asset, calibrate next-step CTA, and use the under-leveraged post-conversion surface to lift downstream metrics. Emits brief + paste-ready HTML/CSS. Use when the user needs a thank-you page after opt-in or post-purchase that does more than say "thanks" - it bridges to the next step. Not for OTOs (see /convert oto-page), downsells (see /convert downsell-page), or cross-sells (see /convert cross-sell-page).

Architect the Three Locks persuasion sequence: Lock 1 Want (sell the state), Lock 2 Trust (earn belief through proof + voice), Lock 3 Excuse (give the rational justification). Outputs the lock-by-lock blueprint that the rest of the asset writes against. Use when planning the persuasion architecture of a sales page, VSL, or long-form email before drafting copy. Not for writing the open (use convert-open) or the close (use convert-close) - this designs the middle architecture they bridge.

Apply the Donahoe Transition System: 10 moves (Comparison Bomb, Escalation, Aside Bomb, Interrupt, Dismiss, Diagnostic, Assumed Agreement, Internal Moment, Admission, Energy Drop) that move copy through energy and momentum, never through filler phrases. Use when a draft has clunky transitions or "here's the thing" / "let me be straight with you" filler that signals the writer ran out of ideas. Not for full-draft momentum engineering (use convert-chute) and not for opening hooks (use convert-o...

Apply The Donahoe Voice Rules: sentence mechanics, word choices, structural moves, and the Bullshit Filter as a checklist. Operating system for every piece of copy - every headline, email, sales page, ad - passes through these non-negotiable rules. Use when a draft exists in some voice (yours, AI default, marketing-bro) and you need to bring it to Donahoe Voice - first-person, contractions, specific, no marketing-speak, reads aloud natural. Not for engineering momentum (use convert-chute) and...

Author the page that hosts a Video Sales Letter: video embed, headline + subhead above the player, buy-button reveal mechanics, supporting copy below the fold, and Method audit footer. Emits brief + paste-ready HTML/CSS. Use when the user has (or will record) a VSL and needs the page that delivers it to traffic. Not for the VSL script itself (see /convert vsl) and not for written long-form sales pages (see /convert sales-page).

Author Video Sales Letter scripts: 18-minute spoken structure with timestamps, doctor-visit pattern, Method primitives compressed to spoken cadence. Emits script + reader-cue annotations. Use when the user needs a VSL script from scratch and intends to record themselves or a presenter. Not for the page that hosts the video (see /convert vsl-page) and not for written long-form (see /convert sales-page).

Author webinar registration pages: time/date framing, big-promise headline, three-bullet curiosity stack, attendance-driving copy. Emits brief + paste-ready HTML/CSS with form + countdown markup. Use when the user has a scheduled live or evergreen webinar and needs a registration page that drives both opt-in and show-up rates. Not for the webinar itself (see /funnel conviction-webinar) or generic opt-in pages (see /convert squeeze-page, /convert lead-magnet-page).

Author direct-response conversion assets via The Donahoe Method: sales pages, VSLs, squeeze pages, OTOs, downsells, lead-magnet pages, bridge pages, webinar reg, thank-you pages, plus the Method's copy primitives (open, proof, locks, bullets, close, chute, voice). Use when the user has a product or offer and needs fresh copy/pages built from a brief - not auditing existing assets. Not for analyzing or scoring existing copy on a URL - see /market copy or /market landing for those.

Vendor W-9 collection workflow, 1099-NEC vs 1099-MISC vs 1099-K decision tree, contractor classification check (IRS 20-factor + ABC test embedded), TIN matching, backup withholding triggers. Templates only - not personalized tax advice.