Apppublic

pathmode/intent-preflight

sourceHugging Faceupdated 12h agoView on Hugging Face

0likes

App README

Intent Preflight by Pathmode

What will your coding agent have to guess? Paste a brief, ticket, Markdown IntentSpec, or JSON spec and check six dimensions of implementation readiness. Compare a weak checkout brief with a stronger version, inspect what the checker read, edit it, and download the exact input.

This static Space runs entirely in your browser. It has no inference API, analytics, storage, or upload endpoint. A Content Security Policy blocks outbound connections. Reloading the page clears edits.

How it works

The build imports Pathmode's existing web preflight parser (lib/specProseExtract.ts), MCP readiness engine (packages/mcp-server/src/readiness.ts), synthetic demo fixtures, and canonical IntentSpec serializer. The six checks cover title, objective, outcomes, constraints, edge cases, and verification. Recorded unresolved product choices are reported separately.

“Needs review” means the English-language heuristics could not confirm extracted text; it does not establish that the text is wrong. Confirmations and waivers are reported as self-asserted, not authenticated here. A passing check does not prove product value, implementation quality, or authorization to build. The examples are synthetic demonstrations, not a performance benchmark.

Downloads preserve the original input, including any existing metadata. They do not approve, rewrite, or update a readiness stamp in that input. Re-run preflight through the MCP server before implementation.

Continue with Pathmode

Build from the Pathmode repository

node apps/huggingface-preflight/build.mjs
npx tsc -p apps/huggingface-preflight/tsconfig.json --noEmit
npx vitest run apps/huggingface-preflight/ lib/preflightReadinessParity.test.ts lib/intentMdParseParity.test.ts
python3 -m http.server 7860 --directory apps/huggingface-preflight/dist

Upload only the contents of apps/huggingface-preflight/dist/ into a Static Hugging Face Space. Do not upload the application repository, environment files, or unrelated assets. Rebuild and rerun parity tests when shared readiness logic changes.