v0.2.2

Decide. Build. Judge.

Creative direction, interface design and motion engineering for coding agents.

Form & Force is an open-source Agent Skill and Claude Code plugin. It gives an agent a method for web work: directions dealt from the subject and chosen by looking, a design language derived from the chosen frame, and a jury that judges the rendered page above hard accessibility and engineering gates.

claude plugin marketplace add erenthedeveloper0/form-and-force
claude plugin install form-and-force@form-and-force

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 toRead
Know what it is and whether it fits your workIntroduction
Install itInstallation
Use it on a project todayQuick start
Understand the method end to endHow 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.

GuideCovers
Creative directionReading the subject, the register, the twin, dealing a hand, turning answers into devices
Visual explorationSketching key frames, the sketch board, choosing by looking
Design languageDeriving composition, typography, colour, imagery, coded visuals and a design system from the chosen frame
MotionWhether something should move, motion character and tokens, choreography, scroll, reduced motion, the motion strip
BuildingWorking in your stack, components and the atlas, accessibility, responsive design, performance, security
Quality: the floor and the juryThe ten hard gates, the static scan, the rendered audit, the jury and its verdicts, the report
Reviewing existing workAudits and critiques that redesign nothing uninvited

Reference

PageWhat it lists
ToolsEvery command-line tool: arguments, output, exit codes
Reference libraryThe skill's 18 references: what each is for and when it is loaded
Component atlasHow the atlas of 180 components is organised and searched, with its index
The deckRegisters, lenses, structures and lead media
TemplatesThe direction brief, motion score, component spec, jury brief and report
ConfigurationEnvironment variables, and the files the skill writes on your machine
CompatibilitySupported environments and what has been verified in each
TroubleshootingInstallation, discovery, browsers, packaging and the checks

Working on Form & Force

PageFor
ContributingSetting up, the checks, pull requests
ArchitectureHow the repository is organised and why
Testing and evaluationThe four ways the project is checked, from free tests to human judgement
ExtendingAdding references, atlas entries, deck cards, tools and eval cases
Brand and siteRebuilding the brand assets and this documentation site
ReleasingVersions, 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.