Srijika Documentation

Srijika is a CLI-first toolchain for a code-first React application studio. Create a complete project directly from npm; then use a terminal, VS Code, Codex/MCP, or optional Desktop Studio against the same source and architecture rules.

npm create srijika@latest my-app
cd my-app
npx @srijika/cli dev

Desktop Studio is not required. Restricted, typed source ending in the resolved UI suffix (canonical default .ui.tsx) remains the only persisted UI source of truth whenever the visual workbench is used.

Cross-feature code is equally governed: src/shared accepts only pure UI Primitives, UI+Connector Widgets, and UI-less Headless Capabilities. The default starter remains minimal, with TanStack Query available only through the explicit --react-query create option.

Public alpha

The current milestone is a working code-first UI foundation. Rust-backed generated APIs and business logic are planned for Phase 2; they are not part of the current product.

Start with product status

Understand what is implemented today, what remains deliberately limited, and what the roadmap promises.

Learn the authoring model

See how pure UI files, connectors, stores, hooks, slots, and parts form one predictable system.

Start from public npm

Create a pinned React workspace, validate its architecture, and run the real Vite application without installing Desktop Studio.

Connect VS Code or MCP

Use generated editor tasks, structure actions, and software-independent MCP tools against the same project files.

Scale through a monorepo

Register multiple Vite and Next.js applications, route VS Code and MCP by project, and aggregate owner-test evidence.

Migrate an existing React app

Keep the source immutable while Codex converts reviewed slices into a distinct, traceable, verified Srijika target.

Understand the architecture

Follow source through the restricted compiler, derived document, workbench, renderer, and native boundary.

Use canonical reference

Read the complete engineering documents used by the repository and its quality gates.

The core promise

Visual tooling must never silently replace developer-owned code with a hidden format. Srijika permits an operation only when it can produce a bounded source edit, validate the expected content hash, compile the resulting TSX, and pass the same rules used everywhere else.

.ui.tsx source
  → restricted non-executing compiler
  → diagnostics + stable source map + validated UiDocument
  → hierarchy + Inspector + React preview
  → bounded source edit intent
  → hash-checked save
  → compile again

Recommended path

1. Follow Getting started to create the first project from npm.
2. Use the CLI-first workflow for terminal creation and runtime commands.
3. Follow the VS Code workflow for Structure, context creation, diagnostics, tasks, and MCP.
4. Use the Monorepo workflow when one repository contains multiple applications.
5. Read Product status to establish the current boundary.
6. Follow React migration to convert an existing app into a separate target.
7. Follow Using Srijika Studio only when you want the optional visual workbench.
8. Learn Project anatomy and the ownership rules.
9. Study the Authoring model for .ui.tsx and connectors.
10. Read Architecture before extending the compiler or native boundary.

Create your first project

View create-srijika on npm