iframe-proxy | Sunbelt Computer Software

Repository navigation

schema: spec-driven

context: |

Project: parallel-code — Electron desktop app that runs Claude Code, Codex,

and Gemini side by side, each in its own git worktree. macOS + Linux only.

For stack, layout, and conventions see `CLAUDE.md` (the single source of

truth). Highlights relevant when authoring specs:

- Frontend ↔ backend communication goes through typed Electron IPC.

- IPC channel names live in the `IPC` enum in `electron/ipc/channels.ts`

and are re-exported to the preload allowlist in `electron/preload.cjs`.

- IPC payload types live in `src/ipc/types.ts`.

- Capability specs describe CURRENT behavior; propose new behavior through

`openspec/changes/<name>/` (run `/opsx:propose`).

rules:

proposal:

- Keep proposals focused on WHY; put HOW in design.md.

specs:

- Requirements MUST use SHALL/MUST; avoid should/may for normative text.

- Every requirement MUST have at least one scenario with WHEN/THEN.

- Describe observable behavior, not library names or internal APIs. If

you need to name an exported identifier (e.g. an IPC channel the

renderer calls), prefer ones that are already part of the public

contract rather than internal helpers.