DirectedEdges/specs

Schema, types, and command line tools to record and manage UI component specifications.

125Stars on the repository
25Mods indexed here, across every type
3d agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

schema.release

02

DirectedEdges/specs

Command Claude Code

Release @directededges/specs-schema to npm. Arg: version (e.g., 0.16.0).

125 3d ago A 0 tokens

DirectedEdges/specs

Command Claude Code

Generate a dependency blast-radius or change-impact report for one or more components from fresh specs analyze dependencies data. Args: [— intended change description].

125 3d ago A 0 tokens

specs.adr.accept

04

DirectedEdges/specs

Command Claude Code

Confirms the implementation is clean, then marks the ADR as ACCEPTED. Run this after reviewing the diff from /specs.adr.implement.

125 3d ago A 30 tokens

specs.adr.create

05

DirectedEdges/specs

Command Claude Code

Draft an Architecture Decision Record (ADR) for a proposed change to the specs-schema types or schema package.

125 3d ago A 21 tokens

specs.adr.implement

06

DirectedEdges/specs

Command Claude Code

Applies the changes described in an ADR directly to types, schema, tests, and changelog. Runs all validation gates.

125 3d ago A 25 tokens

DirectedEdges/specs

Command Claude Code

Check consistency across adr/, packages/schema/, packages/cli/, and site/ for the current branch before merging. Reports gaps between what the ADR declares, what the schema defines, what the CLI exposes, and what the docs cover.

125 3d ago A 46 tokens

apply-custom-tokens

08

DirectedEdges/specs

Command

Inject your team's token shapes into fetched Figma data so generated specs use your format, not ours.

125 3d ago A 19 tokens

bridge

09

DirectedEdges/specs

Command

Command "bridge" from DirectedEdges/specs, covering usage, subcommands, start, stop and status.

125 3d ago A 0 tokens

cache

10

DirectedEdges/specs

Command

Command "cache" from DirectedEdges/specs, covering usage, why it exists, what it writes, staleness and options.

125 3d ago A 0 tokens

fetch

11

DirectedEdges/specs

Command

Fetch raw Figma REST API payloads for configured sources.

125 3d ago A 0 tokens

generate

12

DirectedEdges/specs

Command

Generate component specifications from Figma. There are three ways to run it, distinguished by where the Figma data comes from: a manifest listing many components, a JSON file plus one named component, or the live Figma file itself over the CLI bridge.

125 3d ago A 0 tokens

init

13

DirectedEdges/specs

Command

Initialize a specs.config.yaml file with production-ready defaults.

125 3d ago A 0 tokens

render

14

DirectedEdges/specs

Command

Command "render" from DirectedEdges/specs, covering how a render works, usage, arguments, options and --config.

125 3d ago A 0 tokens

scan

15

DirectedEdges/specs

Command

Scan a Figma file and generate a manifest of all components.

125 3d ago A 0 tokens

transform

16

DirectedEdges/specs

Command

Command "transform" from DirectedEdges/specs, covering usage, arguments, options, -o, --output and --config.

125 3d ago A 0 tokens