SRCL is an open-source React component and style repository that helps you build web applications, desktop applications, and static websites with terminal aesthetics. Its modular, easy-to-use components emphasize precise monospace character spacing and line heights, enabling you to quickly copy and paste implementations while maintaining a clean, efficient codebase.
npm install
npm run devGo to http://localhost:10000 in your browser of choice.
We use Vercel for hosting.
If you need to run node script without running the server, use this example to get started
npm run script exampleRun the unit tests for the sacred CLI framework primitives:
npm testThis runs two suites in sequence: the JavaScript vitest suite under scripts/cli/lib/__tests__ and the Python unittest suite under scripts/python/sacred_cli/__tests__. The Python suite includes a parity test that asserts byte-identical output between the two runtimes for every public layout primitive — change a JS module and the Python mirror must follow in the same PR or npm test fails. If python3 is not on PATH, the Python suite skips with a warning (so contributors on minimal containers can still run npm test). Use npm run test:js or npm run test:python to run a single suite.
Sacred ships a tiny zero-dependency CLI framework under scripts/cli/lib. The framework reads its palette from scripts/cli/colors.json so the terminal surface and the React surface stay in agreement. Two reference templates render the same data set in two languages:
npm run cli:typescript
npm run cli:pythoncli:typescript runs scripts/cli/templates/template.ts via tsx. cli:python runs scripts/python/templates/template.py against a snake_case Python mirror of the framework under scripts/python/sacred_cli. Both screens use the alt screen buffer and raw mode keyboard input — press q or Esc to exit. The same template is also mounted as a React component on the kitchen sink page (search for CLI TEMPLATE EXAMPLE).
If you want to write your own CLI screen or port a sacred React surface to a terminal, the four skills under skills/ walk through the conventions:
skills/port-sacred-terminal-ui-to-typescript-cli/SKILL.mdskills/port-sacred-terminal-ui-to-python/SKILL.mdskills/port-sacred-terminal-ui-to-react-using-same-conventions/SKILL.mdskills/port-sacred-terminal-ui-to-hostile-react-codebase/SKILL.md
Sacred Computer (the React framework) and Simulacrum (the CLI framework under scripts/cli/ and scripts/python/) are two halves of one project — both render the same primitives, both load the same palette from scripts/cli/colors.json, and both share a single doc surface. Every AGENTS.md and SKILL.md in the repo is published as raw markdown at a stable URL so coding agents can fetch them without cloning:
- https://sacred.computer/llms.txt — llmstxt.org index, grouped into Repo conventions, Simulacrum (CLI framework), and Skills
- https://sacred.computer/llms-full.txt — every doc concatenated in one fetch
- https://sacred.computer/llm/AGENTS.md — root sacred / Simulacrum conventions
- https://sacred.computer/llm/components/AGENTS.md — canonical catalog of every sacred React component (props, theming tokens, CLI primitive equivalent)
- https://sacred.computer/llm/scripts/cli/AGENTS.md — Simulacrum TypeScript framework
- https://sacred.computer/llm/scripts/python/AGENTS.md — Simulacrum Python mirror
- https://sacred.computer/llm/skills/port-sacred-terminal-ui-to-typescript-cli/SKILL.md
- https://sacred.computer/llm/skills/port-sacred-terminal-ui-to-python/SKILL.md
- https://sacred.computer/llm/skills/port-sacred-terminal-ui-to-react-using-same-conventions/SKILL.md
- https://sacred.computer/llm/skills/port-sacred-terminal-ui-to-hostile-react-codebase/SKILL.md
The URL set is built from the filesystem at compile time — app/llm/[...path]/route.ts calls generateStaticParams() against the same listDocs() helper used by /llms.txt and /llms-full.txt, so adding a new AGENTS.md or SKILL.md to the repo automatically exposes it at https://sacred.computer/llm/<repo-relative-path> and a vitest URL guard fails CI if the on-disk doc set drifts from the served URL set. Both /llms.txt and /llms-full.txt follow the llmstxt.org convention.
If you have questions ping me on Twitter, @wwwjim. Or you can ping @internetxstudio.