Skip to content
DarkPrint
Setup

Assisted Design

One command puts the DarkPrint skill in your own agent. It interviews you about the work, searches the registry for a blueprint or cards that already do part of it, and writes what you decided as a folder the registry can store.

  1. 1. Install it

    Claude Code
    npx -y darkprint skill install
    Codex
    npx -y darkprint skill install --codex

    Either line has npx fetch the darkprint package from npm and copy the DarkPrint skill it carries into skills/darkprintunder that agent’s folder, ~/.claude for Claude Code and ~/.agents for Codex, where the agent reads its skills. The first run downloads the package and npx keeps it in its own cache. Nothing else is installed and no account is created. When you ask it to, the DarkPrint skill can post your draft to a live page on this site while it interviews you, and it does nothing of the kind otherwise.

    Read it before you run it if you like: SKILL.md and its references are served file by file, and a manifest lists every file with its checksum, so the copy npx installed can be checked against what this site serves. Running the line again replaces the copy with the version the package carries.

  2. 2. Answer its questions

    An interview, not a generator. Ask it for a blueprint and it asks you what the work is first, because a graph nobody described is a graph nobody can check. Six things, all of which you would have had to decide anyway, and one of them it looks up for you.

    • the outcomewhat exists at the end that does not exist now
    • the checkthe command that exits non-zero when the work is wrong
    • the registrywhether a published blueprint or card already does part of the job, searched before you describe a node
    • the nodeswho does each part, and whether that is an agent, a command, a check or a person
    • the boundarieswhat has to reach each node, and what must never reach it
    • the loopwhere it closes, how many attempts it may take, and which way each fork goes

    It can decline. If nobody can name the command that fails when the work is wrong, it offers a two-node prototype to find one instead of drawing a graph that cannot be checked.

  3. 3. Keep the folder

    What it writes
    • topology.dotthe graph: who is wired to whom, and the guard on every fork
    • cards/<node>.yamlone card per node, reused cards byte for byte
    • blueprint.yamlthe slug, title and one-line summary the registry files it under
    • README.mdwhat it is, which validator checked it, and what it leaves to the runner

    Before you see the folder, the DarkPrint skill runs the registry’s own validator over it, with the darkprint CLI when it is installed and through this site’s API when you say yes, and reads every warning back to you. Drop the folder on Publish, or publish it from your terminal with a write-scoped API key from Settings.

What it never does

The DarkPrint skill writes files and runs nothing. Whatever it is asked, three limits hold.

  • runno node runs and no model is called on your behalf. The folder is text, and whichever runner you choose executes it
  • publish by itselfpublishing is your step. Sign in at Welcome, name the blueprint at New blueprint, then drop the folder on Publish or POST it from your terminal with a write-scoped API key from Settings
  • sendthe DarkPrint skill sends your one-sentence task to the registry's search while it drafts, and nothing else leaves your machine on its own. Checking the folder against the registry's validator, publishing it, and opening a live page are steps it asks you for and you take