piflow

Plugin piflow in blueif16/PiFlow. Commands read from the repo's manifest — 1 month ago.

Skills (19)

• multi-source-research

  Fan out a research query across three source types — Reddit (practitioner sentiment), local YouTube transcript RAG via yt-rag (curated long-form), and Exa web search (semantic crawl) — then synthesize a distilled brief. Use when the user wants the newest/highest-quality information on a topic — vend

• web-design-guidelines

  Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

• iso-hero-illustration

  Method for authoring the piflow hand-authored 2.5D ISOMETRIC hero SVGs (atom = one node, substrate = the DAG, protein = the self-improve loop, and any new metaphor) so every shape AND decoration is grounded in the canonical design doc and named — never decorative, never illogical. TRIGGER before cre

• memory-slices

  Per-node MEMORY slices (Leg A — self/history) — FIND a node's standing lessons + cross-run RECURRENCE before the optimizer edits it, and MAINTAIN the memory.md set so it stays honest, bounded, and never rots. The Leg-A twin of `okf-slices` (Leg B — world/code): a memory lesson `[[links]]` the OKF co

• okf-slices

  THE DEFAULT pathway to understand this codebase — any setting, any logic, any lifecycle, at any level, INCLUDING how much of the codebase is mapped/covered in the first place. Load this FIRST whenever you (or a sub-agent) are about to explain, investigate, or answer any question about how a part of

• piflow-enhance

  Pi Flow · ENHANCE — improve an existing, running pi-flow workflow the disciplined way: turn a spotted flaw, a recurring finding, or human feedback into ONE atomic, generalizing change via capture→route→edit→verify→ approve→commit, never a one-off hack. Owns the criteria fixture (the per-node quality

• piflow-fixer

  Pi Flow · FIXER — the default playbook staged into EVERY substrate fixer spawn, the human-facing fix protocol, and the orchestrator contract for a whole feedback cycle; it turns one assigned issue + an isolated candidate git worktree of its node into a staged, gate-proven repair. LOAD/FOLLOW when: y

• piflow-gate

  Pi Flow · GATE — the base agent that judges whether ONE fixer's candidate edit actually fixed its issue, and decides its fate: STAGE it for a human to adopt, or REJECT it back to a fresh fixer. The third agent of the optimize loop and the last: triage NAMES the defect, the fixer SOLVES it, the GATE

• piflow-init

  Pi Flow · INIT — create a structured workflow (a DAG of producer/verify nodes coordinating through the filesystem) and stand it up to run as a fleet of efficient pi agents (pi.dev / earendil-works/pi) driven by non-Claude coding-plan models, with Claude Code as the single console. The source of trut

• piflow-inspect

  Pi Flow · INSPECT — the instrument router for looking INTO a run or a node: performance, cost, timing, context composition, loop/stall anomalies, recurrence. LOAD THIS SKILL BEFORE debugging or analyzing ANY pi-flow run/node — it routes each question to the piflowctl verb that already answers it (st

• piflow-maintenance

  Pi Flow · MAINTENANCE — the canonical STANDARDS reference for a node config + a run condition: the exact per-node lifecycle, the `op[]` action envelope, PRE/POST hooks, gates & policy, how a node FINISHES (fenced-JSON tail · `submit_result` · `returnMode` · verified-not-trusted), run PROFILES, and t

• piflow-overlord

  Pi Flow · OVERLORD — the CONTROL-PLANE agent contract: the seat between the human and the pi fleet that OBSERVES the canonical telemetry stream, DECIDES, and ACTS through piflowctl (run / optimize / fix), making the high-order calls a deterministic controller can't — continue · abort · rerun-with-a-

• piflow-release

  Pi Flow · RELEASE — publish the @piflow/* npm packages (the @piflow/core SDK, the `piflowctl` CLI, and the langgraph/e2b/daytona extension adapters) the disciplined way: Changesets OWNS the versions, CI publishes via npm OIDC Trusted Publishing, and every release passes one gate sweep. LOAD THIS SKI

• piflow-start

  Pi Flow · START — run & monitor an already-created pi-flow workflow on the pi fleet via the SDK CLI, with Claude Code as the single console. LOAD THIS SKILL BEFORE running ANY piflow/pi command — it pins the canonical invocation: the npm-linked global `piflowctl run <templateDir>` bin (NOT `node …/d

• piflow-triage

  Pi Flow · TRIAGE — the base agent that turns a finished run's MEASUREMENTS into recorded, de-duplicated issue files, and nothing else. The twin of piflow-fixer: TRIAGE names the problem, the FIXER solves it; the issue file is the boundary object between them, and the loop always runs both in that or

• piflow-web-design

  The design system for the PiFlow marketing site (`site-piflow/`): a white/grey editorial field with a HARD-rationed orange accent, Geist type, an ink (not orange) action system, the engineering grid, the white passe-partout hero frame + imitated top pills, and the light iso-block illustration vocabu

• premium-saas-stack

  Build a premium, dark, "Linear/Vercel/daytona"-grade SaaS or dev-tool frontend by composing from a BOUNDED MENU of vetted choices — a few locked-in premium picks per layer (tokens, type, layout, background effects, motion/scroll, component idioms, particles, cursor, kinetic text, optional 3D) so tha

• transform-workflow-to-pi

  Take any Claude Code Workflow (a `.claude/workflows/*.js` script that uses agent()/parallel()/ pipeline()/phase()) and run the IDENTICAL pipeline efficiently on a fleet of pi agents (pi.dev / earendil-works/pi) driven by non-Claude coding-plan models — with Claude Code as the single console and moni

• piflow

  Pi Flow — author, enhance, and run structured filesystem-coordinated workflows (a DAG of producer/verify nodes) as a fleet of efficient pi agents driven by non-Claude coding-plan models, with Claude Code as the single console. This is the plugin OVERVIEW/router; the work lives in three skills — pifl