claude-starter

Plugin claude-starter from marketplace claude-starter in ryanportfolio/willaicite. Commands read from the repo's manifest — today.

Skills (57)

• addskill

  Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

• adopt-repo

  Mirror external repo privately under user's account + overlay firmware: clone, strip template-only files, privacy-sweep, init-project. Use: $adopt-repo <url>, 'pull this repo into our firmware'.

• advocate

  Only on explicit $advocate: challenge a just-made change before it lands. Never from natural-language requests.

• apply-firmware

  $apply-firmware, or bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

• arena

  Parallel attempts at one task, blind judging, best ideas grafted onto strongest. Use: $arena, 'try a few approaches', 'build me options', bakeoffs, competing versions, stalled long-horizon or wow-loop step.

• astra-fullreview

  Full multi-agent Codex review on gpt-6-astra, medium. Same lifecycle as codex-fullreview. Use: $astra-fullreview, 'full Astra review with sub-reviewers'.

• astra-review

  Cross-vendor review on gpt-6-astra, medium. Same CLI lifecycle as codex-review. Use: $astra-review, 'have Astra review this'.

• babysit-ci

  Watch PR checks, fix failures. Use: $babysit-ci, 'watch CI', 'fix CI', 'get checks green', PR with failing or pending checks. Not a bare merge request.

• brainstorming

  Brainstorm or design product, interface, workflow, architecture, or behavior change with unresolved goals or material tradeoffs. Skip routine or fully specified work.

• bro

  Plain-language restatement. Use: $bro anywhere in msg, 'plain english', 'plain language', 'dumb it down', 'I don't understand', 'what does that mean'.

• cache-loop

  Caching or stale content.

• caveman

  Every session reply to user: terse Caveman prose + built-in Unslop. User-facing deliverables → Writing.

• claude-review

  $claude-review, Claude or Fable asked to review Codex-written code, or cross-vendor review via Claude CLI.

• climb-loop

  Hill-climb a target round after round: Opus, Sol and Astra rank our UI blind against named reference apps (none → redesign-concepts, build the pick, climb past our own versions) until all rank ours first, or a scripted eval climbs to perfect. Use: $climb-loop, 'make our UI beat <app>', 'climb our UI

• codex-fullreview

  Full multi-agent Codex review: codex exec runs impartial-review as Manager with fresh sub-reviewers (gpt-6.1-sol, high), then each finding verified. Use: $codex-fullreview, 'full Codex review with sub-reviewers'.

• codex-image-gen

  Image asset needed (icon, sprite, texture, splash, logo, marketing art, illustration) → Codex image_gen via codex exec. Use: 'generate an image', 'make an icon', 'use gpt-image / my Codex sub', placeholder → real art.

• codex-review

  Cross-vendor second opinion: Codex CLI (codex exec review, gpt-6.1-sol, high) over PR, branch, commit, or uncommitted diff, then each finding verified. Use: $codex-review, 'have Codex/Sol review this'.

• conversion-ux

  Audit, design conversion flows stage by stage (arrive to exit): each element asks easier, honest question. Paywalls, pricing, trials, sign-up, onboarding, checkout, forms, filters, booking. Use: $conversion-ux, 'why doesn't this convert', 'audit this flow'. Visual concepts → redesign-concepts; copy

• coordinate

  Coordinate with another named Claude Code session: read its work + recs, critique, send own rec, let it answer, once agreed have it finish; ping user only when a step needs them. Use: $coordinate <session>, 'coordinate / review / go back and forth with another session'.

• dare

  $dare, first principles, questioning the problem: 4 fresh stages decompose, audit, recombine, test; immutable goals + constraints kept.

• deep-plan

  $deep-plan: interview a loose idea in short decision rounds; stop for explicit go before anything is built.

• deploy-site

  Deploy willaicite to Railway production and verify it live. Use when the user says $deploy-site, asks to deploy, ship, or push the site, or asks why a merged change is not live yet. Handles the git-worktree gotcha that ships stale source.

• design-prototypes

  Brief → distinct image concepts (sections, features, interactions, branding) → compare → refine pick, before build. Use: $design-prototypes, prototype visual directions, compare design options. Built UI → redesign-concepts.

• design-study

  Study admired reference websites into a persistent design-learnings file future design work must consult. Use when the user says $design-study, sends links to study for design inspiration, or asks what prior site studies found.

• enhance-prompt

  User wants a rewritten, copy-ready prompt for another agent or session. Produce prompt; don't run its task.

• fable-mode

  Hard multi-step work, uncertain diagnoses, repeated failures, 'did it work/is it fixed/prove it', or tasks needing careful verification + handoff. Skip routine changes.

• forge-repo-ui-skill

  Synthesize a repo-specific UI or design skill from current agent skills. Not ordinary UI work or backend-only work.

• gauntlet

  Only on explicit $gauntlet: draft → dare → final draft → why → rewrite → arena → commit, stop for $merge. Skills fully; other artifacts need declared apply method + real check.

• handoff-audit

  Draft self-contained audit prompt for a separate fresh session: exact scope, falsifiable checks. Doesn't run the audit.

• impartial-review

  Review, audit, or stress-test recent code changes with fresh independent agents. Needs exposed multi-agent tools or authed Codex CLI.

• init-project

  Configure a starter project on setup request: detected project facts, only necessary user questions.

• lab

  Explicit ask to lab or prototype a visual, UI, motion, or game-feel element with live tuning before production.

• long-horizon-workflows

  Long-horizon rounds via Workflow tool: 1 script per batch, fresh baseline, candidate executors, blind pick, independent judges each round, schema verdicts, run journal. Use: $long-horizon-workflows, big task in Workflow-audited rounds. Claude Code only.

• long-horizon

  Work too big for one context window: long multi-step tasks, progress lost to compaction or failed retries, work spanning hours or sessions, $long-horizon, or 'run in verified rounds'.

• merge

  Merge PRs: 4 fresh-context self-reviewers + fixes, then Codex loop: $codex-fullreview, fix, $codex-review reruns (3 max) until clean, then CI + squash-merge. Only when user types $merge; then every session PR goes through it + merges.

• motion-design

  Animation that must read + feel right: explainers, promos, trailers, hero/UI motion, landing-page effects, generated scroll films, 3D embeds, component transitions + gestures, UI card loops, kinetic type, WebGL particles, janky animation. Not static layout.

• optimize-context

  Cut per-turn context or token load: trim kernels, skills, connectors; push generic context optimization to starter.

• perf-loop

  Measured optimization rounds with independent review: FPS, loading, latency, throughput, resources; no named target → triage every dimension first. Use: $perf-loop, broad perf requests. Skip isolated fixes.

• product-walkthrough

  Product tour replaying real screens (product CSS + markup), guide cursor acts; embed or MP4. Use: $product-walkthrough, onboarding tours.

• recall

  Before unfamiliar project-area work; retrieve project decisions or pitfalls; save authorized durable fact; quirk just cost retry, backed-out change, or user correction → pitfalls.

• redesign-concepts

  Built UI → screenshots → Codex image_gen → 10 redesign concepts → owner picks → build plan. Use: $redesign-concepts, 'show what we have to Codex, get 10 better versions', 'prototype improvements to current UI'. Brief only → design-prototypes.

• refine

  Explicit workflow-improvement review; user preferences → rules or skill; recurring task friction justifying a narrow skill or reference change; unattended weekly review ($refine weekly).

• security-loop

  Whole-repo security audit or pen-test in independently verified runs → fix owner's picks → rerun until nothing new. Use: $security-loop, 'security-audit / pen-test this codebase'. One diff or question → security-review.

• seo-loop

  SEO/AEO/GEO: study the site, map how people search for it, compare with its field, improve pages. Use: $seo-loop, 'improve SEO', keywords.

• servers

  $servers, after starting a dev server, or user asks what's running, which port is which, why browsers or node.exe are open, or to close old servers and browsers.

• session-hub

  Coordinate parallel Claude Code sessions via shared append-only HTML hub. Use: $session-hub, 'run parallel sessions on this', joining a hub, or proactively when the checkout shows edits or commits this session didn't make.

• showpiece

  Push an artifact past what people expect of its kind, any medium. Use: $showpiece, ambitious creative direction, portfolio-quality work, replacing generic AI styling. Not quiet or faithful work (forms, dashboards, exact recreations, brand matching) → ui-quality, frontend-design or project UI skill.

• sync-starter

  Pull template improvements into a spawned repo, compare starter drift, or push a generic improvement back to the starter.

• ui-quality

  Everyday UI quality floor (forms, dashboards, settings): build every state; audit by measuring rendered page (axe-core, focus, reflow, contrast). Use: $ui-quality, 'audit accessibility', 'is this UI production-ready', 'check this page on mobile', 'feels wrong on my phone', 'break this UI' with worst

• untangle

  Whole-codebase structure survey: hidden links, needless links, surplus, special cases → decision log of fixes, each over the problems it solves → owner picks → long-horizon fixes. Report only. Use: $untangle [area], 'untangle this codebase', 'where is this codebase tangled'. One diff → simplify or i

• why

  Pressure-test a recommendation with one fresh reviewer: on $why, or before presenting own weighty rec (hard to undo, 2+ real options, real time or money at stake). Never from ordinary why questions or paraphrases.

• wow-animation

  Use when the user runs `$wow-animation <subject> [notes]`, or asks to start a new shareable promo, explainer or trailer animation for a website, game, app or feature. Kickoff and orchestration only; the craft lives in motion-design.

• wow-loop

  Evidence-gated review + repair loop, one deliverable or set of like items. Use: $wow-loop, wow factor, 'dial it to 11', target score ('get it to 8/10', 'bring everything under 6 up to 6+'), substantial visual work (3D, animation, UI, rendered docs) needing reference fidelity or repeated correction.

• wrapup

  $wrapup, or user asks if session is done, OK to archive, or what's left: one verdict from git, the PR, scratch files, running servers or browsers.

• writing-plans

  Clear task needing a multi-step implementation plan, dependency ordering, or durable handoff. Skip routine changes doable directly.

• writing-skills

  Use when creating new skills, editing existing skills, or verifying skills work before deployment

• writing

  Write or edit audience-facing prose: docs, UI copy, emails, release notes, application answers; voice matching, clarity review, AI-tell cleanup. Session replies follow session conventions.

Similar plugins