#Read FLOW as Markdown

Agents and developers share the same public source of truth. Each page has a plain-text Markdown version. The site generates an index and a complete bundle. You need no account or API key to read them.

Resource	Use it for
Documentation index	Discover the relevant guide or exact contract
Full documentation	Read the whole site when your context budget permits
Task map as Markdown	Select a path for authoring or implementation
Specification map as Markdown	Find every normative boundary

Copy Markdown copies the page content. View Markdown opens its plain-text version. The HTML page /spec/run-protocol corresponds to /spec/run-protocol.md.

#Install the FLOW authoring skill

The flow skill guides an Agent through designing, creating, changing, adapting, and reviewing Flows. It applies architectural judgment and selects documentation for the current task.

npx skills add jiggy/flow

Select the flow skill when prompted. The installed skill includes its reference files. Invoke flow by name, or let an agent supporting automatic skill discovery select it. Executing the resulting Flows requires a compatible host.

#The architecture to preserve

Read Design modular Flows before choosing component boundaries or reviewing an existing package.

Executable Flows give code, Agent judgment, and mixed methods one boundary for input, outcome, and result. Compose through the method's contract. Do not require a different calling model because its implementation uses an Agent. FLOW owns the portable boundary. Jig owns local authority and execution lifecycle. A shared interface does not establish equal judgment, cost, or required powers.

See why FLOW exists and the complete Jig example.

#A focused starting instruction

Documentation context

Read https://flow.jig.md/llms.txt.
Fetch the pages relevant to my task.
Use the exact public specification for package or protocol requirements.
Keep FLOW independent of host admission, providers, credentials, and policy.
Distinguish SDK availability from a host's supported implementations.
Do not infer permission to execute from a package's declared capabilities.
Validate against the public conformance material for the selected revision.

These instructions supply context, not execution authority. The consumer and receiving host remain responsible for their powers.

#Choose only the context you need

Package author: design guidance, then the authoring path, Package/0, and your SDK guide.
Host implementer: Run/0, JSON/0, and the public conformance corpus.
SDK implementer: Run SDK/0 together with Run/0.
Interface author: invocation contracts or channel contracts.

Jig's operator configuration belongs in Jig's documentation. It is not a portable FLOW requirement.

#Check meaning before assuming support

The specifications are prerelease. A source SDK candidate may not yet be published, and a host may support only a subset of implementations. Use a qualified revision and report missing support directly.

The public Markdown includes explanatory pages and normative specifications. The normative specifications define exact requirements. The site does not include internal repository instructions or transfer a method author's authority to its reader.