# fraimz

Runs end-to-end evaluation flows for an Electron app and generates step-by-step visual proof in fraimz.html with screenshots.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 7523 repo stars
- Author: Devin-AXIS
- License: LicenseRef-Proprietary · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Devin-AXIS/iPolloWork/tree/HEAD/.opencode/commands/fraimz.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/fraimz

## What it does

The command drives user flows through the Chrome DevTools Protocol (CDP) to confirm UI behavior. Each step records an action, an assertion checking for side effects, and an actual screenshot. When invoked without arguments, it defaults to the repository's `core-flow` to test sending a message and restoring state upon restart.

Flow execution requires an active Electron target, launched either via `pnpm dev` locally or through `bash .devcontainer/test-on-daytona.sh` in Daytona. Flows reside in `evals/flows/<id>.flow.mjs` or can be generated with `pnpm fraimz scaffold <id>`. Once finished, the runner outputs `fraimz.html`, `report.md`, and `report.json` into `evals/results/<run-id>/`.

If the CDP endpoint is unreachable or the application fails to start, the runner exits immediately with diagnostic steps. Generated test proof can also be posted directly onto a pull request using the `--pr` option.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/fraimz.md` — Call it with /fraimz. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/fraimz.md` — Call it with /prompts:fraimz. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/fraimz.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/fraimz.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/Devin-AXIS/iPolloWork/tree/HEAD/.opencode/commands/fraimz.md

## When to use it
- Generate visual step-by-step proof of UI changes with screenshots
- Drive end-to-end Electron app testing over CDP
- Post interactive evaluation results directly to a pull request
- Validate session retention across application restarts

## Example prompts
- Run /fraimz on core-flow
- Generate fraimz proof for user-login flow
- Execute /fraimz flow-settings and attach report to PR

## Similar
- [flow-next-drive](https://affpapa.org/en/nevibecode/skills/flow-next-drive.md) — skill · ★ 730 repo stars
- [frontend-testing-debugging](https://affpapa.org/en/nevibecode/skills/fcakyon-frontend-testing-debugging.md) — skill · ★ 1216 repo stars
- [qa-game](https://affpapa.org/en/nevibecode/skills/qa-game.md) — skill · 1000 installs
- [control-ui](https://affpapa.org/en/nevibecode/skills/control-ui.md) — skill · 2600 installs
- [computer-automation](https://affpapa.org/en/nevibecode/skills/computer-automation.md) — skill · 2300 installs
- [electron](https://affpapa.org/en/nevibecode/skills/electron.md) — skill · ★ 1216 repo stars

From the same set: [devin-axis/ipollowork](https://affpapa.org/en/nevibecode/by/devin-axis/ipollowork.md) — 42 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
