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.
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.
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.
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)…
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…
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…
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 /…
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…
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…
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…
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…
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…
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…
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…
594 3d agoA121 tokens
AGPL-3.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: