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.
Use Node.js 22.12+ on the 22.x line, 24.x, or 26+ (^22.12.0 || ^24.0.0 || >=26.0.0), as required by the repository's tooling. Node.js 18, 20, 23, and 25 are outside the supported range.
npm install
npm run devGo to http://localhost:10000 in your browser of choice.
We use Vercel for hosting.
Run the type check, CLI primitive tests, component documentation guards, documentation-route tests, and Python tests:
npm testThis runs three gates: TypeScript type-check, the vitest suite, and the Python unittest suite (which includes a parity test between the JS and Python CLI runtimes). If python3 is not on your PATH, the Python suite skips with a warning. 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; global.css mirrors that palette for React. Two reference templates demonstrate the same layout in two languages, with language-specific sample data:
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 Esc or Ctrl-C 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 porting 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
The documentation routes publish AGENTS.md and SKILL.md files from traversed, non-hidden directories, plus top-level components/*.tsx source, so humans and agents can read them without cloning. Dependency, build, Git, and .workdir directories are excluded. Other Markdown files, including README.md, are outside the allowlist:
- https://sacred.computer/llms.txt — llmstxt.org index, grouped into Repo conventions, Simulacrum (CLI framework), Skills, and Component source
- https://sacred.computer/llms-full.txt — discovered instruction documents concatenated in one fetch; component source is served separately
- 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/components/Card.tsx.txt — raw source of a component (every
components/*.tsxfollows this pattern) - 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
- https://sacred.computer/llm/skills/fast-typescript-check/SKILL.md — keep this repo's TypeScript fast to type-check and fast to run
Adding an allowlisted instruction document or top-level component source makes it discoverable for the next build. Component sources use the .tsx.txt URL suffix. 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.
