Installation
Form & Force ships in two forms built from the same skills/form-and-force folder:
- A Claude Code plugin. This repository is both the plugin and a one-plugin marketplace.
- A standalone skill ZIP for claude.ai or the Skills API, or a folder you copy into your skills directory.
Commands below were checked against the Claude Code documentation and Claude Code 2.1.308 on 2026-10-23.
Claude Code plugin
From GitHub
claude plugin marketplace add erenthedeveloper0/form-and-force
claude plugin install form-and-force@form-and-force
Claude Code 2.1.292 and later can do both steps in one command: claude plugin install form-and-force --marketplace erenthedeveloper0/form-and-force. Inside a session, /plugin opens the same flows.
The skill then appears as form-and-force:form-and-force. Claude loads it when a request matches its description, or you can invoke it with /form-and-force:form-and-force.
From a local clone
git clone https://github.com/erenthedeveloper0/form-and-force.git
claude plugin marketplace add ./form-and-force
claude plugin install form-and-force@form-and-force
A marketplace added from a local path is read in place rather than copied: claude plugin list shows the clone as the plugin's location.
For one session only
claude --plugin-dir ./form-and-force
Update and remove
claude plugin update form-and-force@form-and-force
claude plugin uninstall form-and-force@form-and-force
claude plugin marketplace remove form-and-force
plugin.json sets a version. A release reaches users only when that version increases (see releasing).
Standalone skill
ZIP for claude.ai or the Skills API
Each GitHub release has the ZIP attached. To build it yourself:
python3 tooling/package_skill.py
This validates the skill, then writes dist/form-and-force-<version>.zip. The archive contains one folder, form-and-force/, holding SKILL.md, references/, scripts/, assets/ and LICENSE, and nothing from the rest of the repository. The command then reopens the archive and verifies that every linked reference and script is inside it.
Upload the ZIP in claude.ai under the skills settings, or through the Skills API. The upload itself has not been tested by the maintainers yet.
Copy as a personal or project skill
macOS and Linux:
cp -R skills/form-and-force ~/.claude/skills/ # every project
cp -R skills/form-and-force path/to/project/.claude/skills/ # one project
Windows (PowerShell):
Copy-Item -Recurse skills\form-and-force "$env:USERPROFILE\.claude\skills\"
As a personal skill it is invoked as /form-and-force.
Requirements
| Need | For | Install |
|---|---|---|
| Claude Code | the plugin | see the Claude Code documentation |
| Node 18 or newer | every bundled script (inspect_repo, slop_scan, deal, motion_tokens, and the rendered tools) | https://nodejs.org |
| Playwright with Chromium | the rendered tools only: sketch_board, audit_page, motion_strip, contact_sheet | below |
| Python 3.11 or newer | building the ZIP, the repository checks and the documentation site; not needed to use the skill | https://www.python.org |
Optional: rendered tools
The sketch board, the page audit, the motion strip and the contact sheet use Playwright. Install it in the project you are working on, or in a scratch directory. Never install it globally. Without it the skill still works: directions are compared from written frames, checks are static, and the report says which judgements had no rendered evidence.
npm i -D playwright && npx playwright install chromium
To keep it out of the project:
mkdir -p ~/.cache/ffpw && cd ~/.cache/ffpw && npm i playwright && npx playwright install chromium
export FF_PLAYWRIGHT_DIR=~/.cache/ffpw
FF_CHROMIUM_PATH can point at an existing Chromium or Chrome for Testing binary.
What the skill writes on your machine
- The dealer's history:
~/.form-and-force/history.json. It holds the ids of dealt cards, and for each direction you record, its one-line device, typeface names, palette words and motion character, keyed by a hash of the project path. It is how consecutive projects are kept from resembling each other. Nothing is sent anywhere. Use--no-historyto turn it off, orFF_HISTORYto move it. - Tool output: the rendered tools write images and JSON under the system's temporary directory unless given
--out. - Sketches: key frames go where the agent puts them, by convention
.ff/frames/in the project. Add.ff/to the project's ignore file.
Environment variables and the exact output locations are listed in configuration. If something does not work, see troubleshooting.