From unstructured project context to traceable, review-ready requirements.
Requra.AI turns documents, meetings, and notes into requirements, user stories, acceptance criteria, evidence, stakeholder feedback, and delivery exports.
Open interactive demo · Workflow · Architecture · Run locally
- Create a project and add source documents or meeting context.
- Start asynchronous analysis and follow explicit progress states.
- Review summaries, requirements, stories, criteria, risks, and evidence.
- Invite stakeholders to comment through focused public review links.
- Resolve feedback and export delivery-ready artifacts.
| Area | What is implemented |
|---|---|
| Projects | Create, edit, search, filter, sort, inspect, and delete project workspaces. |
| Analysis | Queued, processing, completed, partial, rejected, failed, and retry states. |
| Results | Summaries, requirements, user stories, acceptance criteria, quality signals, and source evidence. |
| Collaboration | Viewer/commenter invitations, public review, feedback submission, and team inboxes. |
| Meetings | Scheduling, invitations, join flow, live controls, consent, recording orchestration, and summaries. |
| Export | Browser-generated CSV and Jira-ready JSON data. |
The normal production path is React frontend → .NET backend → external AI pipeline → normalized results.
- TanStack Query owns server state, mutations, cache invalidation, and polling.
- Zustand owns focused session and client state.
- React Router keeps project and results views linkable.
- React Hook Form + Zod keep forms local, typed, and validated.
- Axios adapters isolate transport contracts from feature UI.
- MSW fixtures power the explicit, backend-free demo variant without silently replacing failed production requests.
| Responsibility | Technology |
|---|---|
| Application | React 19, TypeScript 5.9, Vite 7, React Router 7 |
| Data | TanStack Query 5, Zustand 5, Axios |
| UI | Tailwind CSS 4, Radix UI, CVA, Lucide, Sonner |
| Forms | React Hook Form, Zod |
| Motion | GSAP, Lenis, Framer Motion |
| Testing | Vitest, Testing Library, MSW, JSDOM |
Requirements: a current Node.js LTS release and npm.
git clone <repository-url>
cd frontend
npm ci
cp .env.example .env
npm run devPowerShell:
Copy-Item .env.example .env
npm run devVite serves http://localhost:5173. Environment options and safety gates are documented inline in .env.example.
| Command | Purpose |
|---|---|
npm run dev |
Start the development server. |
npm run build |
Type-check and create the production bundle. |
npm run test:run |
Run the test suite once. |
npm run lint |
Run repository-wide ESLint. |
npm run preview |
Preview the production bundle. |
The /demo entry opens a deterministic, resettable workspace with synthetic data. Its dedicated runtime uses the normal UI and API contracts with same-origin MSW handlers, browser-local versioned fixtures, and production-service isolation.
- Production build: passing.
- Test suite: 15 files, 97 tests passing.
- Responsive verification: 320×568 through 1920×1080.
- Accessibility checks include keyboard activation, visible focus, exact accessible metric values, touch-target sizing, text scaling, and reduced motion.
The backend and AI pipeline are external services. Demo meeting media and transcription are simulated, Jira-ready export does not create remote issues, and direct browser-to-AI processing remains a guarded opt-in fallback rather than the production default.
Capture context. Expose evidence. Align stakeholders. Deliver clearly.