wayland

Wayland's own how-to guide: explains what Wayland can do and gives the exact steps to operate it. Covers what can Wayland do, connecting an AI provider or model, creating an assistant, building and launching a workflow, setting up a team, scheduling a task, connecting an MCP server or outside tool, and switching models or using Flux Auto. Use when the user asks what Wayland can do, what features exist, how do I connect a provider or model, how do I add Claude or OpenAI or Gemini, how do I create or edit an assistant, how do I build or run a workflow, how do I set up a team of assistants, how do I schedule a task or set up a recurring job, how do I connect an MCP server or outside tool, or how do I switch models or turn on Flux Auto automatic model routing. Do NOT use when the user wants help with a non-Wayland task (writing, coding, research, document creation) — those have their own skills; this skill is only about operating Wayland itself.

Security operations center expertise covering SIEM query writing, alert triage workflows, incident investigation procedures, IOC analysis, threat hunting techniques, playbook design, log analysis patterns, Splunk and Elastic SIEM queries, alert fatigue reduction, escalation procedures, and shift handoff practices. Use when the user asks about soc analyst, soc analyst best practices, or needs guidance on soc analyst implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.

Orchestrates the process of deploying a software application to production, from CI pipeline verification through monitoring confirmation, chaining six software-development skills into a structured release workflow. Use when the user needs to deploy an application to production with a repeatable, safe process that includes database migration, monitoring, and rollback planning. Do NOT use for local development setup, staging-only deployments, or infrastructure provisioning without application deployment.

End-to-end workflow for building a complete DevOps pipeline from an empty repository through CI/CD, infrastructure as code, monitoring, alerting, and incident response. Covers the full lifecycle from first commit to production-grade operations. Use when the user wants to devops pipeline from scratch or needs a structured multi-step process for this goal. Do NOT use when the request is a single-step task or requires professional advice beyond educational guidance.

Orchestrates end-to-end production incident management from detection through resolution and retrospective, chaining five skills into a complete incident lifecycle pipeline. Covers triage, log investigation, monitoring verification, documentation, and team retrospective. Use when handling a production incident that affects users and requires coordinated response, investigation, resolution, and follow-up. Do NOT use for non-production issues, minor bugs that do not affect users, or planned maintenance activities.

Orchestrates the full incident lifecycle from initial triage through postmortem documentation, chaining five software-development skills into a structured incident management workflow. This workflow chains the incident-response skill with logging, monitoring, deployment, and documentation skills. Use when the user is handling an active production incident and needs a structured process from detection through resolution and postmortem. Do NOT use for non-production issues, planned maintenance, or post-incident analysis only (use technical-documentation directly for standalone postmortems).

Orchestrates the process of shipping a new software version by chaining four engineering skills into a structured release pipeline. Covers release planning with changelog generation, commit history analysis, deployment execution, and post-release monitoring verification. Use when the user needs to ship a release with proper versioning, documentation, and deployment verification. Do NOT use for hotfixes that bypass the normal release process or for continuous deployment where every merge auto-deploys.

Complete workflow for building a production monitoring stack from scratch, covering metrics collection, alerting strategy, dashboard design, runbook creation, and on-call practices. Establishes the observability foundation that enables confident deployments and fast incident resolution. Use when the user wants to set up monitoring or needs a structured multi-step process for this goal. Do NOT use when the request is a single-step task or requires professional advice beyond educational guidance.

Orchestrates the creation of a complete CI/CD pipeline from scratch by chaining five DevOps skills into a structured automation pipeline. Covers pipeline architecture design, workflow configuration, containerization, deployment strategy, and production monitoring. Use when the user needs to set up automated build, test, and deployment from zero or replace a manual deployment process. Do NOT use for tweaking an existing pipeline or adding a single CI job to an established workflow.

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.

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 personal brand, consultant, coach, or founder. Not for a bio (use content-bio) and not for a full sales page (use convert-sales-page) - the About page is the trust asset in the awareness layer, not the conversion layer.

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 window. Not for writing cold pitches to journalists (use content-press-release + pitch email) and not for full press release drafting (use content-press-release).

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 /market landing).

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-new copy generation (use /convert sales-page or /convert open) and not for live-URL CRO teardown (use /market landing).

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 for Method audit scoring (use convert-audit).

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-transition).

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 structuring).

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 generation (use convert-open) and not for the Voice Rules pass (use convert-voice).

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 after this diagnostic).

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 scroll-rhythm) and not for native mobile-app design.

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 Method deployment.