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 creating or revising ANY iso hero illustration under site-piflow/components/iso/: the order is DOC → named component spec → CONFIRM with the user → draw. Use when asked to draw/fix the atom, substrate, protein, add a metaphor, or when a render "looks terrible / illogical / decorative". Pairs with piflow-web-design (brand) + premium-saas-stack (bar); the workspace + kit + research live in site-piflow/components/iso/_gen/.

Aller à l'installation

Dépôt: blueif16/PiFlow
Dernière activité de la source: 27 juin 2026 à 04:56
Langue détectée de SKILL.md: anglais
Étoiles: 97
Forks: 1

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/blueif16/PiFlow --skill iso-hero-illustration

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

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 — piflow-init (create), piflow-enhance (improve), piflow-start (run). Source of truth is a structured workflow TEMPLATE; the `@piflow/core` SDK loads it and runs one `pi` per node.

2026-07-24

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 the token / contract vocabulary. The brother of piflow-init — init decides WHAT the DAG is (divide the purpose, assign the nodes); MAINTENANCE answers "what is our canonical way to DO this?" for an already-built or half-built loop. LOAD/FOLLOW when editing or extending an existing node.json / template and you need the standard: "where does a script go (which op, pre or post)", "how should this node end / return its result", "how do I add a gate / check / judge", "the exact node lifecycle", "how do promote / state channels work", "set up a profile", "inject vs readScope", "is this the right op syntax". REFERENCE, not a loop — carries the standards only, never the optimize loop and never the divide-and-assign creation

2026-07-17

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 …/dist/cli.js` nor `pi-runner/run.mjs`, both non-canonical) with `--provider <gw> --thinking low --sandbox local` + `--from`/`--until`. Do NOT reconstruct the command from memory. Triggers — load on ANY of: "run / kick off / start / resume my piflow workflow", "do a live run on pi", "run game-omni on pi", "companion-mode run", "monitor / follow / poll a run", "diagnose a stalled / never-wrote / blocked node", or the words "piflow" / "pi-runner" / "pi fleet" / "pi run" appearing at all. The run is ALWAYS: pull the next prompt from the bank → dry-run (free) → live background → poll. To CREATE or PORT the template first use piflow-init.

2026-07-16

Tout voir dans ce dépôt

Iso Hero Illustration — meaning-first, grounded in the design doc

These hero SVGs are HAND-AUTHORED 2.5D iso line-art for the piflow site. The recurring failure is a picture that looks plausible but is ILLOGICAL — shapes and decoration with no real meaning, the wrong topology (a boundary thing drawn inside the boundary), a label that isn't the real noun. The cause is always the same: drawing before grounding in the design doc. This skill forces the order so that never happens again.

The one law

Every object AND every decoration maps to exactly ONE real, nameable concept from the canonical design doc. If you cannot name it and state what it means, it does NOT go in the picture. Meaning before pixels — decoration is not free, a wall/tether/glow each needs a meaning or it is cut.

0. Setup (before anything visual)

Load piflow-web-design (brand: one orange spark, white/grey light system) and premium-saas-stack (the premium bar). Load test-discipline if you touch the kit/Scene.

Workspace: site-piflow/components/iso/_gen/ — kit.mjs (the shared iso kit + the collision-aware Scene + the deterministic shape-placement layer), RESEARCH-collision.md / / (the methods), (gate).

name

iso-hero-illustration

description