// the find
lidangzzz/OnlySpecs
Do not modify the code. The code should always be generated solely from the specs. After each update to the specs, the code will be regenerated from scratch.
OnlySpecs is an Electron desktop app that pairs a Monaco editor and integrated terminal with Claude's Agent SDK to enforce a spec-driven workflow: you write markdown specs, and the app regenerates the entire codebase from them rather than letting you hand-edit output. It's aimed at developers experimenting with AI-generated codebases who want a GUI around that loop instead of scripting it themselves.
The multi-version folder convention (specs_v0001.md paired with code_v0001/) gives a dead-simple audit trail of which spec produced which code, with zero extra tooling required. It wraps real building blocks (Monaco, xterm.js via node-pty, the official Claude Agent SDK) instead of reinventing an editor or terminal, so the editing and shell experience should feel familiar. The GitHub import-and-analyze flow is a genuinely useful idea: reverse-engineer specs out of an existing repo instead of only going spec-to-code.
Full regeneration from scratch on every spec change throws away the normal code-review/diff workflow — there's no way to see what changed in the generated output short of diffing two full folders yourself, and no rollback beyond keeping old version folders around. The config file stores the Anthropic API key in plaintext JSON under Documents, which is a bad default for anything beyond a local toy. Test coverage is a single file (claude-sdk.test.ts) for an app with this much surface area (file system ops, PTY management, IPC, GitHub cloning), and the README still has the placeholder 'yourusername/OnlySpecs' clone URL, suggesting docs haven't been proofread post-release.