PostIdea catches architectural contradictions before your AI turns them into code.Export as AGENTS.md. Paste into your AI tool as system context. Done.
caught before line 1 — chat app idea, run through PostIdeademo
idea →"offline-first, real-time chat, lightweight"⚠ conflict: offline_mode=true vs realtime=true these are mutually exclusive without a sync queue — resolve before proceeding⚠ ambiguous: "lightweight" — no memory or bundle size target defined rejected: cannot generate a measurable NFR from thisstatus →2 conflicts, spec blocked
how it works:three steps
Describe your idea. We catch the conflicts. You lock the spec.
Vague, contradictory, half-formed — describe what you want to build. PostIdea surfaces the conflicts before your AI coding tool builds the wrong thing.
<IDEA>→<PARSE>→<SPEC>parsing...
ProjectIntent
realtime: true
offline: true
✖ CONFLICT⚠ BLOCKED
<discover>
<validate>
<conflict>
<spec>
<handoff>
<verify>
● discover
Discover
A structured conversation extracts what you actually want to build. Messy, half-formed, contradictory — PostIdea asks focused questions until the intent is clear enough to work with.
input →"build a chat app fast scalable maybe offline idk"output →target users, scale estimate, realtime needs, offline requirements extracted
● warning
Validate
We force contradictions out of your requirements before they hit production. Ambiguous terms get flagged. Vague constraints get rejected.
⚠ ambiguous: "fast" — no latency target defined⚠ ambiguous: "scalable" — no load target defined
● conflict
Conflict Detection
Contradictions in your requirements are surfaced before a single line of code is written. Not after a sprint. Not in production.
✖ conflict: offline mode vs realtime sync✖ conflict: "fast" vs no defined infra constraints→ resolve before proceeding
● valid
Spec
Measurable, unambiguous requirements. Define constraints once — we reject designs that violate them. This is your source of truth.
✔ FR-01: messages delivered <200ms on 4G✔ FR-02: offline queue with sync-on-reconnect✔ FR-03: supports 10k concurrent users
● valid
Handoff
Structured context that Cursor, Claude, and Copilot actually understand. Stop re-explaining your project on every session.
✔ AGENTS.md generated✔ constraints embedded✔ scope boundaries defined
● valid
Verify
Three deterministic layers. Layer 1 checks your file tree against expected architecture paths. Layer 2 matches each FR's testable signals as word-boundary identifiers in your source. Layer 3 audits your git diff semantically — advisory only, never overrides the verdict.
Built for developers who are tired of building the wrong thing.
conflict:detected
Conflict detection — before line 1
You told your AI “offline-first, real-time.” Those are two conflicting architectures. PostIdea catches it before Cursor builds both. Contradictions, ambiguous constraints, and missing NFRs are surfaced and blocked — not discovered three sprints in.
idea (what you said)PostIdea verdict
real-time chat
✖offline-first
⚠conflict: mutually exclusive without sync queue
lightweight
✖no memory target defined
⚠rejected: cannot generate measurable NFR
arch_enforce()Architecture decisions locked before code starts. The ADE generates database, service structure, realtime, and auth decisions from your spec — with explicit tradeoffs and future consequences attached.
spec_generation()From conversation to structured requirements in minutes. Functional requirements, constraints, acceptance criteria — organized automatically.
compliance_score()Your build is scored against your own spec. Attach it to PRs. Share it with clients. No hiding behind "it works."
agents_md()Exports your spec and architecture decisions as AGENTS.md. Paste into your AI tool as system context. Done. Works with Cursor, Claude, and Copilot today — no integration required.