Roadmap

Shipped in v1.0.0Copy Anchor Link

• A form can be rendered, bound, validated with a real Zod schema, and submitted end to end, with full TypeScript inference rejecting a mismatched field type at compile time.
• prismrepo, the real CLI, installs Prism's Layer 1/2 templates into a consumer project, verified against a genuinely fresh, standalone, non-workspace project via a real npm install and npx invocation, the exact path every real consumer uses.
• A compatibility matrix covering React, Zod, React Hook Form, Tailwind, Next.js, Node, and TypeScript, with every cell backed by an actual test, see Requirements.
• All six packages, published and publicly installable from npm under the @prismrepo scope.

The forms-only milestoneCopy Anchor Link

Prism's current product milestone is forms only. Data grids/tables, an API integration layer, a CRUD engine, permissions, dashboards, workflows, and file management are long-term directions that inform today's six-package boundary but are explicitly out of scope right now.

Known gapsCopy Anchor Link

• No manual assistive-technology testing (VoiceOver, NVDA, JAWS) has been performed yet. Automated axe-core coverage is real and covers the full assembled form plus keyboard tab order, see Changelog.
• Nested field paths in defineForm's configuration aren't supported yet, see Advanced Usage.
• Only Tailwind v4 has been exercised in a full application build.

See Changelog for the complete v1.0.0 release notes, and GitHub for ongoing development.