Start with your project
Load the brief, design guidance, relevant examples, and accepted decisions for the task at hand.
AnyPixel Next / Open-source alpha
Give your coding agent the context to make better design decisions—and the tools to check its work. Edit the guidance. Keep the evidence. Carry decisions into the next task.
CLI + MCP · Node 24+ · Apache-2.0
The workflow
Your agent does the reasoning and edits. AnyPixel brings the project context, captures the evidence, and helps check what changed.
Load the brief, design guidance, relevant examples, and accepted decisions for the task at hand.
Import a screenshot or reference. Add the browser extension to capture a live page, DOM facts, and axe results.
Read the evidence, run checks, and compare results in an HTML report. Keep measured findings separate from design judgments.
Save an accepted decision with its reason and scope. Bring it into the next relevant task instead of starting over.
Five shared operations, through CLI or MCP: context / observe / review / record / read
Make it yours
Your team's way of working belongs in files you control. Start with the included guidance, change it, and contribute what you learn.
your-project/
└── design/
├── brief.md # the job to do
├── system.md # your patterns
├── project.json # packs + tools
└── decisions/ # choices + reasons
Read the starter practice
Add Markdown guidance and examples for your product, brand, or domain. A useful contribution doesn't need TypeScript.
Use the extension API to collect new kinds of evidence or check your team's conventions. Keep those additions outside the core engine.
The new runtime and original packs are Apache-2.0. Read the source, fork it, share a pack, or help improve a fixture.
Start here
The local demo captures the invitation form, finds two accessibility issues, applies a scripted fix, and checks again. Then it carries a decision into the next task.
It prints the before-and-after reports so you can inspect the evidence yourself.
Set it up in your own projectgit clone https://github.com/justinrhowell/anypixel-next.git
cd anypixel-next
npm ci
npx playwright install chromium
npm run demo
Already have Chrome? Skip the browser download and use BROWSER_CHANNEL=chrome npm run demo.
Early alpha, installed from source. npm publication and testing in individual agent hosts are still ahead.
A few details
Use the CLI or register the MCP server, then give your agent the starter skill. The same five operations are available through both. Your agent keeps responsibility for reasoning, edits, and permissions. The MCP SDK integration is tested; setup in specific agent hosts still needs validation.
Project decisions are scoped Markdown files with a reason and an acceptance record. Relevant accepted decisions appear in later context. You can read and edit them. This is explicit project knowledge, not automatic model training.
No. Guidance, decisions, and importing PNG, JPEG, Markdown, text, or JSON work without browser tools. Live capture and accessibility checks use the optional Playwright and axe extension.
AnyPixel stores guidance, decisions, and evidence locally. The runtime makes no model-provider calls and has no telemetry. Your host agent has its own data handling, and live pages can make normal network requests. Only install native extensions you trust.
The CLI, MCP server, packs, decisions, evidence reports, file import, and optional browser extension work today. Next come real agent-host trials, authenticated capture, and independent design tasks. See the current status and roadmap.
A better example. A sharper check. A practice that helps your team. Start small and help shape what comes next.