Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

de-novo

@de-novo source repo

9 published skills

  1. ▌
    Pencil Skill · de-novo bundle
    Create and edit Pencil (.pen) design files programmatically. Generate UI designs as JSON-based .pen files with themes, variables, components, and layouts. Includes CLI tools for reading, searching, editing, and validating .pen files without requiring the Pencil desktop app. Requires Node.js 18+. Schema version 2.8.
    0
    installs
  2. ▌
    Dryad · de-novo bundle
    de-novo Dryad — one seat per worker on Grove's ground. A seat is a Git worktree, an overlay env when the project has overlays, and a task. Dryad launches no agent: the human picks the launcher (a terminal, a worktree app, tmux, an ACP client) and which worker sits where. Use when you wake up with DRYAD_ID set; when planning parallel work across worktrees; when counting who sits where and what they reported; when the user runs /dryad. Project values live in .agents/dryad-profile.yml. Launching, mailboxes, DAGs, and merging are out of scope.
    0
    installs
  3. ▌
    Grove · de-novo bundle
    de-novo Grove — shared local ground on one machine. n projects, m apps each, one infra set. Names instead of ports; thin overlays instead of cloned stacks. Use when starting, checking, or switching a local environment; when matching ports; when several agents work and verify on the same machine at once; when planting Grove on a new project; when managing machine-shared engines (de-novo skills infra); when the user runs /grove or /grove infra. Project values live in .agents/runtime-profile.yml. Browser QA and e2e runners are out of scope.
    0
    installs
  4. ▌
    Clearing · de-novo bundle
    de-novo Clearing — stop and re-pitch where the work has got to, for a person who lost the thread: read the graph and the facts, then say it again in plain words and the project's own vocabulary.
    0
    installs
  5. ▌
    Forester · de-novo bundle
    de-novo Forester — break a body of work into a plan of items with dependencies and file claims, set how many may run at once on this machine, and keep that many seated as Dryad seats. Values live in .agents/forester-plan.yml (the plan, tracked) and .agents/forester.local.yml (this machine's budget, never committed). The CLI never calls a model; the analysis is yours.
    0
    installs
  6. ▌
    Mycelium · de-novo bundle
    de-novo Mycelium — the facts under the forest. One append-only log of assertions per project: what is held true, since when, with what confidence, in which domain, on whose word. Workers propose; a person or the judging worker commits or invalidates; readers query a moment. Use when work produces a fact that outlives the seat that found it (a locked decision, a verified cause, a blocker, a check result), when a person asks what the project currently holds true, or when the user runs /mycelium. Values live in .agents/mycelium.yml (domains, entity types, predicates with one|many cardinality, and the judges who may commit; tracked). Corrections are amendments that point back; nothing is edited in place. The CLI never judges; the promotion is yours.
    0
    installs
  7. ▌
    Herbarium · de-novo bundle
    de-novo Herbarium — every document a project keeps has one house, and the rest point at it. Use whenever you are about to write, move, rename, or review a document that someone else will read: a README, a skill, a design note, an evidence record, a reference, working rules for agents. Use when a fact seems to live in two files, when a document is getting long, when a link may have gone stale, or when the user runs /herbarium. Values live in .agents/herbarium.yml (the houses, the language, the page cap). The CLI counts drift; it never edits a document.
    0
    installs
  8. ▌
    Understory · de-novo bundle
    de-novo Understory — the story under the canopy. Write the document that lets a person read Forester's graph: what the work is, how it depends and what it claims, what is moving now, what was proven, and what is open. Use when a person asks for a shared document, a write-up, a map, or a status page of the work graph; when the user runs /understory. The graph and the per-item reading lines come from the CLI; you write the prose around them and never restate a fact another file owns.
    0
    installs
  9. ▌
    Catalog · de-novo
    Add, edit, rename, or review a published skill in the de-novo skills catalog (skills/<name>/). Use when creating a new skill, splitting SKILL.md vs README vs examples, wiring .agents load paths, updating the catalog README table, or when the user runs /catalog. Not for planting Grove on a consuming project — that is grove.
    0
    installs