FORM//GRAPH / quick start

One reference.
A useful next step.

Choose a visual idea, understand its mechanism, then give it a place to work.

Three ways into the field

Sources / 33 attributed references
What was found. Each note links to an original reference and separates its summary from our interpretation.
Recipes / 10 production directions
What could be made. Original FORM//GRAPH sequences describe deliverables and proposed runtime budgets.
Studies / three original visual experiments
What the language can look like. Original Metanomicon AI-assisted image studies explore form and material; they are not imagery copied from the source library.

A five-minute path

  1. Choose where the form belongs. Open the atlas. Pick a Project lens or search for a technique. Sources, categories and search work together; Reset filters brings the whole field back.
  2. Inspect one source. Start with Visual AI is shifting from pixels to code. Read its summary, then follow the original reference. Keep the creator’s work separate from our interpretation and build translation.
  3. Give it a production sequence. Switch to Recipes. Try Spectral data membrane: inspect the steps, output and proposed budget. A recipe is a brief to build from, not a finished software package.
  4. See the visual language. Visit the three original studies. Treat them as authored examples of the visual language, not screenshots of saved sources or proof that a recipe is complete. In the hero, open Explore the field to compare modes and adjust entropy. Pause is available alongside the field.
  5. Leave with a brief. Open a source or recipe in the atlas and choose Copy build brief. Add the target screen, the state this visual should express, intended devices and a performance budget. The brief carries permanent reference links; ask a builder to return editable source and a tested implementation.

Grid results arrive in small groups. Use Show more to keep exploring, or Map to inspect all matches. Every entry also has a permanent page that works without JavaScript.

For an agent joining the work

  1. Read llms.txt for the reading contract, then atlas.json for stable public IDs, canonical URLs and source attribution.
  2. Fetch the permanent HTML pages relevant to the task. Verify claims against original sources; describe interpretations and recipes as synthesis. A project lens suggests fit, not a shipped integration.
  3. For repository changes, read the canonical README, AGENTS.md and FORM//GRAPH handoff before editing. The repository owns implementation and contribution rules; the public index describes the reference collection.
  4. Follow the tracked scope in GitHub issue #6 and report actual build and verification results. Public study images and proposed recipe budgets do not establish release status.

Where the source lives

The canonical editable system lives in ydefix/ui-ux. Its README, AGENTS.md, handoff and issue links are team resources that require authorized GitHub access. The public atlas works without repository access.

Everything needed to browse and cite the library is available in this guide, the source and recipe pages, and the public JSON.