Ship
Agent Packs
An Agent Pack is an explicit export intended to give implementation agents structured product context.
Agent Packs are the handoff layer in Lines. They package product meaning, relationships, and visual context so an implementation agent can work from more than a screenshot or a loose prompt.
The goal is straightforward: preserve the path from product intent to implementation context without making the handoff opaque.
Package the model and the View
Lines follows a core workflow:
Model to View to Package to Ship
Model Mode describes what the product means. Design Mode shows how that meaning appears. Ship Mode brings the two together so you can inspect bindings and prepare a package for downstream work.
An Agent Pack can help an agent understand:
The pages and concepts in the product model.
The Nodes and connections that describe behavior.
The visual Views that express those concepts.
The bindings between product meaning and interface elements.
The context a person approved for handoff.
Inspectable by default
In the current beta, Ship export creates a folder containing:
model.md — a readable representation of the product model.
graph.json — structured pages, Nodes, connections, Views, and bindings.
manifest.json — package metadata for the export.
These files are designed to be readable by people and structured enough for agent workflows. Review the exported package before giving it to an implementation agent, just as you would review any other release artifact.
Handoff is explicit
Your working Lines file stays local by default. Creating an Agent Pack is a deliberate export step, so you decide when a model leaves the working document and what is ready to share.
This boundary keeps experimentation separate from approved implementation context. It also leaves a concrete artifact that can be reviewed, versioned, archived, or attached to an existing engineering workflow.
What is planned
Agent Packs are evolving. Planned areas include richer state and annotation authoring, assets, implementation instructions, export history, consent records, and additional handoff files. These capabilities should be treated as planned until they are available in the product and included in an exported package.
Lines is currently in beta. Use Agent Packs for deliberate, inspectable handoffs and validate generated implementation work before shipping it.
Read the current Agent Pack documentation — /docs/agent-packs.