Checks a finished frontend change against the WRITTEN decisions rather than against what the implementer thought they were building. Reads the decision documents and the checkable requirement lines, drives a real browser through the Playwright MCP server, and reports pass or fail per requirement with the measured…
Looks at a finished screen in a real browser and judges whether a person who has never used this product could work out what to do. Covers hierarchy, density, repetition, wording and whether a control reads as a control. Use when a frontend change is done and you want a second pair of eyes on how it looks and reads…
The research-first precondition for building any app on AIMEAT, and the repo-side rules for the app-building prompt system and the served browser SDK libs. Use when the task is to build, make, publish or fork an AIMEAT application (game or tool), or when editing src/services/build-app-prompt.ts, /v1/app-templates, or…
The AIMEAT design language in words and in numbers: the two faces (showroom outside, poster inside), the three type tokens every font on the site descends from, the four shapes, the colours, the wordmark, and the one place a value is changed (theme.css tokens) with the map of every surface a token reaches. Use before…
AIMEAT frontend rules: the styling conventions to write to, and how a finished change is verified by driving a real browser through the Playwright MCP server (three viewports, repaint count, idle network log). Use before writing or editing anything under public/views, public/components, public/js, public/css…
How images for AIMEAT are produced with scripts/genimage.py instead of stock or placeholder art, including the upload log to check before regenerating. Use whenever a task needs an app icon, banner, hero graphic, illustration, logo, og-image or any other picture.
How shared code is authored on the AIMEAT platform: served browser SDK libs, cortex libs, sandboxed extensions and library packs, each with its own source layout, build and gate. Use before writing or editing anything under src/static/sdk-libs/, public/cortex-bundled/, src/data/library-packs, public/lib/, an extension…
Where AIMEAT design specs, plans and roadmap items are authored (in the AIMEAT organism on aimeat.io, not repo docs/), the dogfood session rituals, LOOM/MACHINE ROOM reference resolution, and the ODPS provider identity block. Use when writing a design spec, plan, roadmap item, room.target/room.card/room.release…
How AIMEAT videos are made from live captures and existing recordings with the three tools in aimeat/scripts/demo-video/ (a scripted performer, a passive camera, and a stills-plus-cards cutter), including the capture rules, the card style, the honesty captions and the YouTube hand-off. Use whenever a task is to make…
How prose is written on this project: the AI tells that give a text away and how to remove them, and how Finnish and Spanish are composed rather than translated. Use before writing or editing any user-visible text: UI copy, locale strings, documentation, a handbook page, a changelog entry, a commit message, an…
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
Instructions for miikkij/aimeat-protocol, covering claude.md: aimeat protocol, what this is for, two ways of working, and where each one's knowledge lives, working with jouni and ask the developer first.
Build and publish AIMEAT apps. This OpenHands is wired to an AIMEAT node over MCP (the aimeat tools). When the user asks to build, make, or publish an app, a game, a tool, or anything "on AIMEAT" / "to aimeat.io", follow the workflow below.