Editorial collection

Frontend builder stack

A curated sequence for planning, designing, implementing, testing, and deploying product interfaces.

Workflow stages
6
Curation
Editorial
Reviewed
2026-07-30

How to use this collection

The collection shows a suggested sequence and responsibility for each Skill. Do not install everything by default; start with the stage that matches a real workflow gap.

  1. 01
    Stage 1

    ab-testing

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

    Quality 100/1000 platforms0 risk flags
  2. 02
    Stage 2

    ci-speedup

    Audits a repository's GitHub Actions workflows for CI optimization opportunities — missing caches, redundant setup, sleep-based readiness, long test jobs without sharding, full-history checkout, dead env vars, build-cache misconfig, and ~60 more patterns across caching, redundancy, parallelization, conditional execution, trigger scope, and hidden failures. Use when: (1) analyzing a repo's CI for optimization opportunities, (2) producing a prioritized report with measured wall-clock and runner-mi

    Quality 93/1000 platforms2 risk flags
  3. 03
    Stage 3

    autopilot

    Run the idea-to-ship pipeline AUTONOMOUSLY, in character as a grounded founder-persona — composing ideate → deep-dive → prompt-pack → build-loop to take a real, grounded niche to a near-finish-line-AIMED first-draft product plus an honest ledger of what only a human or the market can finish. ALWAYS invoke when the user says any of "run autopilot", "build this idea→ship autonomously", "spin up a grounded founder and build it", "fly the whole pipeline end to end", or "autonomous first-draft from a

    Quality 91/1000 platforms0 risk flags
  4. 04
    Stage 4

    accessibility-auditor

    Use when reviewing UI for accessibility — WCAG 2.2 AA, keyboard nav, focus, ARIA, contrast, screen-reader semantics — even on 'is this a11y-OK?' or 'mach das barrierefrei'.

    Quality 89/1000 platforms0 risk flags
  5. 05
    Stage 5

    claude-permissions-audit

    Review and reorganize Claude Code permission settings across all config files (global settings.json, project settings.local.json, dotfiles copies). Identifies redundancy, misplaced permissions, and lack of read/write organization. Produces a clean layout where global settings are the source of truth and project-local files only contain project-specific overrides. Use this skill whenever the user mentions reviewing permissions, cleaning up settings, auditing allowed tools, reorganizing settings.j

    Quality 88/1001 platforms2 risk flags
  6. 06
    Stage 6

    create-agent-adapter

    Create or modify Paperclip agent adapters across server, UI, and CLI surfaces. Use when adding support for a new CLI agent, API agent, custom process, or adapter package.

    Quality 87/1000 platforms2 risk flags

Collection completion rule

A workflow is complete when the target outcome is met with acceptable permissions and maintenance—not when every listed Skill is installed.

Build a private local stack