claude

agents-canvas

CANVAS design-system-to-code methodology: a coordinator walks a Pencil design through capture, audit, norm-check, vectorize and assemble, dispatching every phase and every verifier as a separate isolated context with a blocking generator-is-not-verifier gate at each handoff, plus a fail-closed hook that blocks source writes until the token contract is active. Use when a design system has to become working components in the project's own framework, with visual parity and token fidelity proven rather than asserted. Full history in CHANGELOG.md.

4 on GitHubby ForgePlanv1.6.0MITupdated 12 days agomethodology
/

Plugin agents-canvas from marketplace ForgePlan-marketplace in ForgePlan/marketplace. Commands read from the repo's manifest — 12 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (6)

  • canvas-conventions

    CANVAS DS-build conventions knowledge base — the rule set the canvas-guardian audits a Pencil Design System against (HOW it was built, not whether it matches requirements). Single-source refs/slots/no-detach, $--token usage + Category/Variant naming, atomic layering + screens-not-reusable, and snaps

  • canvas-design

    Pencil designer knowledge base for the CANVAS methodology — how to design and extend a .pen Design System with refs, slots, descendants, Layout B, atomic organization, themed tokens, style presets, and UX-law-driven node constraints. Use when designing or extending a Pencil DS, building screens/comp

  • canvas-port

    CANVAS porting playbook — Pencil design system -> Storybook -> native framework code. Shared contract read by canvas-porter-storybook (Vectorize) and canvas-coder (Assemble); the optional canvas-porter-framework (multi-target port) is dispatched only on an explicit multi-framework request, out of th

  • canvas-storybook-test

    CANVAS Storybook-gate validation toolkit (RFC-021 FR-4) — the knowledge base read by canvas-storybook-validator (the C4 Storybook-gate, a SUB Task agent) when it certifies the BUILT Storybook against the Pencil source ONLY. Covers the six certifications: (1) story coverage vs the port-manifest varia

  • canvas-truth-map

    Map a Pencil design system to the ForgePlan source of truth (PRD/ADR/EVID) — the CANVAS Norm-check (N) knowledge base. Use when validating a DS snapshot for coverage (does every required capability have a component, and does every component have a backing requirement) and provenance/traceability (do

  • canvas

    Entry point for the CANVAS design-system -> code pipeline — the master-coordinated walk from a Pencil design to **native code in the consuming project's own framework** (framework resolved via Step 0 — Capture -> Audit -> Norm-check -> Vectorize -> Assemble), an instance of the AD/AID-PDLC sub-cycle

Slash commands (4)

  • /agents-canvas:canvas-audit

    One-shot DS-convention audit (canvas-guardian as a command). Loads the canvas-conventions rule set, reads an exported Pencil DS snapshot (manifest + reference screenshots + snapshot_layout dump), and reports Critical/Warning/Suggestion findings - each with a RULE-ID, a node-id, and a concrete fix. A

  • /agents-canvas:canvas-init

    One-time per-branch setup for the CANVAS tokens-gate. Detects the project framework, derives the per-framework guarded globs, verifies them against disk, and writes the per-branch state file the canvas-gate.sh PreToolUse hook reads. Without it the gate is dormant and design-system writes are unguard

  • /agents-canvas:canvas-review

    CANVAS post-export code + UX gate. Wraps /laws-of-ux:ux-review on the generated Storybook / component code in the project's resolved framework (native single-framework by default; Web Components only when that's the declared stack) and adds CANVAS-specific lenses (token-fork detection, framework-res

  • /agents-canvas:canvas-rule

    Look up a CANVAS design-system convention or a UX law by name — refs/slots, token naming, atomic layering, the token contract, the six Pencil HARD RULES, or any of the 30 Laws of UX. Shows the canonical rule + checklist + 2-3 related rules. Usage: /canvas-rule [name]

Subagents (8)

  • canvas-coder

    CANVAS phase A — Assemble. Profile C-coder source mutator, dispatched as a Task sub-agent (needs no Pencil — works from the port manifest + reference screenshots). Builds the Storybook NATIVELY in the project's resolved framework (React / Vue / Svelte / Angular / Solid — or Web Components only when

  • canvas-coordinator

    Methodology: CANVAS design-suite master (Profile B-orchestrator) — the L2 stage-master of the CANVAS sub-cycle, an instance of the AD/AID-PDLC sub-cycle contract (ADR-010, contract C1-C6; RFC-021). Peer of sparc-orchestrator, bmad-orchestrator, and tdd-orchestrator; this is the design-system instanc

  • canvas-designer

    CANVAS phase C — Capture, an ordinary Task sub-agent (C3 phase generator). Designs/extends the Pencil design system (tokens -> atoms -> molecules -> organisms -> templates -> pages) using laws-of-ux + task-based UX best-practices + Pencil templates + do/don't rules, and produces the DS snapshot the

  • canvas-guardian

    CANVAS phase A - Audit (Profile C read-only reviewer + C4 EVID recorder). Independent, fresh-context audit of HOW a Pencil Design System was built - reads the exported DS snapshot (manifest + reference screenshots + snapshot_layout dump), never live Pencil, so generator != verifier holds. Checks the

  • canvas-porter-framework

    OPTIONAL multi-framework porter — NOT a default CANVAS phase. Profile C-coder source mutator, dispatched as a Task sub-agent (no Pencil). Dispatched ONLY on an explicit multi-framework request; the default native single-framework build never invokes this agent (out-of-default; deferred to future ADR

  • canvas-porter-storybook

    CANVAS phase V — Vectorize, an ordinary Task sub-agent (C3 phase generator). Reads the approved Pencil DS (post Gate A+N) via export_nodes/batch_get/get_variables/ get_screenshot and AUTHORS the token contract (as a forgeplan tokens RFC) plus the Storybook port manifest the Coder implements: a singl

  • canvas-storybook-validator

    CANVAS Gate Storybook — the C4 Storybook validator (Profile C reviewer + EVID-recorder, SUB Task agent). Runs in a fresh isolated context and certifies the BUILT Storybook against the Pencil source ONLY (Figma is a future seam) — never writes component/test code (generator != verifier vs canvas-code

  • canvas-tester

    CANVAS phase N — Norm-check (Profile B reviewer + EVID-recorder, SUB). Independent, read-only validation of a Pencil DS snapshot against the ForgePlan source of truth (active PRD/ADR/EVID): bidirectional coverage (gaps + scope creep) and provenance/traceability (every component + token traces to an

Hooks (1)

  • PreToolUse

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/canvas-gate.sh"

View source on GitHub forgeplan.dev

More from ForgePlan/marketplace

All 24 plugins →

Flagship workflow plugin of the ForgePlan ecosystem — the skills, templates and authoring contract the rest of the marketplace is written against: the smith methodology router (14 contexts), the agent-authoring guide every forgeplan-aware agent follows, and the gate, cleanup and insight skills that keep a pipeline honest. Use when you want the methodology itself rather than one specialist — deciding how to approach a task, gating an artifact before activation, or authoring a new agent to the house canon. Full history in CHANGELOG.md.

44 skills · 1 agent · hooks

4

Professional specialist agents: security and prompt-injection review, PII detection, architecture and staff-level system review, the pre-activation guardian gate, ADR and specification authors, research analysts and infrastructure roles. Use when a task needs a named expert rather than a generalist — an OWASP/STRIDE pass, an architectural fitness review, a decision recorded as an ADR, or the last gate before an artifact is activated. Full history in CHANGELOG.md.

30 agents

4

Builds a navigable map of a project — zones, nodes and verified edges — as a `map.json`, through an eight-agent pipeline (scan -> extract -> verify -> emit -> validate) where every stage runs in a fresh isolated context and a deterministic guardian script, not an LLM, is the sole authority on whether the result can be trusted. Use when you need a structural view of a large or unfamiliar repository that a file tree cannot give, or when a project's forgeplan artifact graph should be shown alongside its code. Not a documentation generator: an edge is either sourced from the artifact graph or proven by a grep, and an unproven one is dropped rather than shipped as noise. Full history in CHANGELOG.md.

3 skills · 4 commands · 8 agents · hooks

4

fpl-hsmem

claude

Project-scoped cross-session memory for Hindsight API >=0.10.2 and <0.11.0. Use when a repository explicitly opts in via .hindsight.json; hooks default off, enrichment is operator-gated, and BankGate is client safety, not server authorization.

10 skills · 1 agent · 1 MCP server · hooks

4

Brownfield extraction pack — turns legacy code and documents into a structured forgeplan graph through a discover agent and twelve extraction skills (ubiquitous language, use cases, invariants, causal links, scenarios, knowledge-graph curation, reproducibility). Use when taking over an undocumented codebase and the first problem is not what to build but what is already there and why it is that way. Full history in CHANGELOG.md.

12 skills

4

Core engineering agents: the source-mutating coder, the code reviewer and test runner that record evidence, plus debugger, planner, researcher, performance and production-readiness roles. Use when the work is ordinary engineering — implement this, review that diff, run the suite and report coverage against the acceptance criteria — and the reviewer should be a different context from the author. Full history in CHANGELOG.md.

11 agents

4

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.

5 commands

HKUDS/CLI-Anything 58,665

obsidian

claude

Claude Skills for Obsidian

6 skills

kepano/obsidian-skills 51,587

Maintain agents-canvas?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins24 plugins