Capabilities
The Free product is durable and honest.
Beam focuses on Figma URL parsing, local credentials, rate-limit aware fetching, local cache, snapshots, simplification, token extraction, asset export, evidence scoring, visual compare, mappings, debug bundles, and local logs.
Free does not mean vague. Beam Free is the local product: inspect designs, export references, keep snapshots, explain missing evidence, and serve agents through MCP.
The evidence and confidence engine is designed for real Figma constraints. It distinguishes known Figma data, rendered-image inference, local snapshots, missing assets, user notes, and confirmation requests.
Visual compare is intentionally pragmatic in v1. It reports dimensions, pixel differences, dominant mismatches, and artifact paths rather than pretending to understand every semantic UI detail.
Run Sequence
- Use Figma access capabilities first: URL parsing, auth, scheduler, and cache.
- Use interpretation capabilities next: simplifier, tokens, assets, warnings, evidence, and confidence.
- Use persistence capabilities after that: snapshots, manifests, mappings, logs, and debug bundles.
- Use verification capabilities last: rendered references and visual compare.
Expected Output
Every capability should either produce structured context, a local artifact path, a stable JSON contract, or an actionable warning. Silent guessing is a product bug.
Files And Artifacts
- .beam/cache/raw/
- .beam/cache/briefs/
- .beam/cache/assets/
- .beam/mappings.json
- .beam/debug/
Next Step
When documenting a new capability, include the command, expected output, files touched, and how it fails.
Recovery Paths
- If a capability depends on Figma and Figma is unavailable, check whether a snapshot can satisfy the workflow.
- If a capability produces uncertain output, inspect the evidence confidence section.
- If a capability touches project files, make sure it does not write credentials or hidden cloud state.
