Form & Force documentation
Form & Force is an open-source Agent Skill and Claude Code plugin for web work: creative direction, interface design and motion engineering. These pages explain what it does, how to install and use it, how its method works, and how to work on it.
The same pages are published as a website, built from this folder by site/build.py. On GitHub, read them here.
Start here
| If you want to | Read |
|---|---|
| Know what it is and whether it fits your work | Introduction |
| Install it | Installation |
| Use it on a project today | Quick start |
| Understand the method end to end | How it works |
Guides
The method in the order an agent applies it. Each guide explains a stage for people, and links to the reference the agent reads.
| Guide | Covers |
|---|---|
| Creative direction | Reading the subject, the register, the twin, dealing a hand, turning answers into devices |
| Visual exploration | Sketching key frames, the sketch board, choosing by looking |
| Design language | Deriving composition, typography, colour, imagery, coded visuals and a design system from the chosen frame |
| Motion | Whether something should move, motion character and tokens, choreography, scroll, reduced motion, the motion strip |
| Building | Working in your stack, components and the atlas, accessibility, responsive design, performance, security |
| Quality: the floor and the jury | The ten hard gates, the static scan, the rendered audit, the jury and its verdicts, the report |
| Reviewing existing work | Audits and critiques that redesign nothing uninvited |
Reference
| Page | What it lists |
|---|---|
| Tools | Every command-line tool: arguments, output, exit codes |
| Reference library | The skill's 18 references: what each is for and when it is loaded |
| Component atlas | How the atlas of 180 components is organised and searched, with its index |
| The deck | Registers, lenses, structures and lead media |
| Templates | The direction brief, motion score, component spec, jury brief and report |
| Configuration | Environment variables, and the files the skill writes on your machine |
| Compatibility | Supported environments and what has been verified in each |
| Troubleshooting | Installation, discovery, browsers, packaging and the checks |
Working on Form & Force
| Page | For |
|---|---|
| Contributing | Setting up, the checks, pull requests |
| Architecture | How the repository is organised and why |
| Testing and evaluation | The four ways the project is checked, from free tests to human judgement |
| Extending | Adding references, atlas entries, deck cards, tools and eval cases |
| Brand and site | Rebuilding the brand assets and this documentation site |
| Releasing | Versions, the release gate, tags and packages |
The project's changelog, roadmap, support and security policies, and its research and brand, are documented beside the code.