These guides cover the developer tools maintained in the n3wth workspace. Start with the product that matches what you need; you do not need to install them all.
| I want to… | Use | What you get |
|---|---|---|
| Build a React site with a shared visual system | UI | An installed package with primitives, themes, fonts, and site compositions |
| Copy components into my own application | Kit | A shadcn-compatible registry; the installed source belongs to your project |
| Give an agent a repeatable way to work | Skills | Task instructions you can inspect, install, and adapt |
| Keep useful context across agent sessions | r3 | A memory service exposed through MCP |
Pick UI or Kit#
UI is a dependency. Upgrade the package to receive shared component changes. Use it when you want the same visual foundation across applications.
Kit distributes source files. You can change those files without changing the registry. Use it when your application needs to own its components.
Both expose React UI, but they have different installation and update contracts. Follow the relevant guide rather than mixing setup snippets from the two.
Start with one working example#
Each product section starts with prerequisites and a small first task, then
explains configuration, reference material, and failures you can diagnose.
Examples describe the source in n3wth/n3wth, except r3's runtime, which is
maintained separately in n3wth/r3.
For changes to this repository, use the workspace guide. For hosting these pages, see publishing the documentation.
Related projects#
- Lunch Money for Agents: a separate read-only financial MCP integration with its own setup guide.
- Canvas: live canvases and realtime sync.
- GBrain: an agent-readable knowledge system.
- Markup: an independent prototype for agents working with people in documents and chat.
Those projects have separate source and release boundaries. This hub links to their repositories rather than implying that their runtimes ship in this workspace.