v0.2.2

Configuration

Form & Force has no configuration file. Its behaviour is set by the request you make, by command-line options, and by a few environment variables.

Environment variables

For the skill's tools

VariableUsed byEffect
FF_PLAYWRIGHT_DIRThe rendered tools, the brand renderer, the browser testsA directory where Playwright is installed. Checked after the current project. Lets you keep Playwright out of the project you are working on
FF_CHROMIUM_PATHThe rendered toolsA Chromium or Chrome for Testing executable to use instead of Playwright's own. audit_page.mjs --chromium does the same for one run
FF_HISTORYdeal.mjsWhere the dealer's history is kept, instead of ~/.form-and-force/history.json. --history <file> does the same for one run

For this repository's checks

VariableUsed byEffect
FF_REQUIRE_NODE=1The test suiteFail, instead of skipping, the tests that need Node. CI sets it
FF_UPDATE_FACTS=1tests/test_rendered_tools.pyRewrite the recorded design facts in tests/fixtures/facts/ after a deliberate change to what design_facts.mjs measures

What the skill writes on your machine

WhatWhereNotes
The dealer's history~/.form-and-force/history.jsonSee below
SketchesWhere the agent puts them; by convention .ff/frames/ in your projectAdd .ff/ to your ignore file
Sketch boards<tmp>/ff-board/<time>/ unless --outboard.jpg, board.json
Page audits<tmp>/ff-audit/<slug>-<time>/ unless --outfirst.jpg, flatplan.jpg, sheet.jpg, report.json
Filmstrips<tmp>/ff-motion/<slug>-<time>/ unless --outstrip.jpg, motion.json

<tmp> is your system's temporary directory. Nothing is sent anywhere: the tools make no network requests of their own, and the rendered tools load only the pages you name.

The dealer's history

The history is how consecutive projects stop resembling each other. For each hand it stores the card ids dealt; for each direction you record, the one-line device, the typeface names, palette words and motion character. Entries are keyed by a hash of the project path, never the path itself.

  • Turn it off for one command with --no-history.
  • Move it with FF_HISTORY or --history <file>.
  • See what it holds with node scripts/deal.mjs recent.
  • Delete the file to forget everything. The next hand is dealt as if no project came before.

The skill's own settings

SKILL.md's frontmatter uses only the portable Agent Skills fields (name, description, license, compatibility, metadata), so the same folder works as a Claude Code plugin skill, a personal or project skill, and an upload to claude.ai or the Skills API. It sets no allowed-tools: the agent asks for permission to run commands as your Claude Code settings require.