# Formlink Runtime

## Docs

- [Design & UX Guidelines](https://docs.formlink.ai/design-guidelines.md): Practical guidance for Classic and Typeform modes: required labels, validation UX, component choices, placeholders, and layout patterns.
- [Example — Composed Wiring (no Universal)](https://docs.formlink.ai/examples/composed-react-wiring.md): Minimal reactive wiring using runtime actions/context with Typeform helpers.
- [Example — Universal Classic](https://docs.formlink.ai/examples/universal-classic.md): Mount the page/list UI via ClassicTemplate with a headless runtime.
- [Example — Universal Typeform](https://docs.formlink.ai/examples/universal-typeform.md): Mount the one-by-one Typeform-style UI via UniversalTypeform with a headless runtime.
- [Formlink runtime spec v1 normative only](https://docs.formlink.ai/formlink-runtime-spec_v1_normative_only.md)
- [Formlink Runtime](https://docs.formlink.ai/index.md): Headless runtime + UI contracts, examples, and pitfalls.
- [CreateRuntime import](https://docs.formlink.ai/pitfalls/createRuntime-import.md)
- [Pitfall — mock transport name](https://docs.formlink.ai/pitfalls/mockTransport-alias.md): Incorrect import/export for mock transport factory.
- [Pitfall — Cannot read properties of undefined (reading 'title')](https://docs.formlink.ai/pitfalls/question-undefined-title.md): Guard question lookup against null qId and subscribe to runtime state.
- [Pitfall — ShadCnProvider missing primitives](https://docs.formlink.ai/pitfalls/shadcn-missing-primitives.md): Fix: provide required shadcn/ui primitives to ShadCnProvider components mapping.
- [Pitfall — Start button does nothing](https://docs.formlink.ai/pitfalls/start-button-no-op.md): Component never subscribes to the runtime store; state changes don't rerender.
- [UseRuntime export missing](https://docs.formlink.ai/pitfalls/useRuntime-export-missing.md)

## OpenAPI Specs

- [openapi](https://docs.formlink.ai/api-reference/openapi.json)