bundles
What each starter kit writes, and why
A bundle is a starter kit: an AGENTS.md with real sections, a one-lineCLAUDE.md bridge, plus whatever extra files that kind of project needs. Installing one never overwrites a file already doing the job. It completes the structure; the substance, your real build command, your actual conventions, what you've actually rejected, stays yours to write. See starter files for the full mechanics.
One kit per project type
Built into the app. General gets no kit of its own: a kit for "anything the other six don't describe" could only hold generic headings.
Coding Project
Code, GeneralProduces: software that runs
Universal on purpose. A coder already knows their own stack, so the app ships this holding placeholder headings and fetches its real content, agent guidelines, code-quality rules, and a skill set, from this catalog.
- Build & Run
- Architecture
- Code Style
- Testing Philosophy
- Verification Gate
- Commit Discipline
- File Size Limit
- Mistakes Log
Research Gem
ResearchProduces: answers, synthesis
- Files in this gem
- Citing a source
- Mistakes Log
sources/README.mdFINDINGS.md
Content Gem
ContentProduces: published work for an audience
- Files in this gem
- Audience and voice
- Mistakes Log
drafts/README.mdpublished/README.mdSTYLE.md
Records Gem
RecordsProduces: state tracked over time
- Files in this gem
- Entry format
- Adding an entry
- Mistakes Log
data/README.md
Personal Gem
PersonalProduces: change in you or a relationship
- Files in this gem
- Writing in the log
- Mistakes Log
LOG.md
Orchestration Gem
OrchestrationProduces: decisions and dispatch across other gems
- Files in this gem
- Mistakes Log
ROSTER.mdPRIORITIES.mdINBOX.mdLOG.mdWORKING-WITH-ME.mdits own richer WORKBENCH.md
Stack kits for Code and General gems
Additive to the universal Coding Project kit above, not a replacement for it. Fetched from this catalog, so they can improve without an app update.
Next.js Fullstack
Next.js App Router with TypeScript, Tailwind, and Prisma
Vite React Dashboard
Vite + React SPA with TypeScript and TanStack Query
Node API Backend
Express API with TypeScript, Drizzle ORM, and Vitest
React Native Mobile
React Native with Expo, TypeScript, and React Navigation
SvelteKit Fullstack
SvelteKit with TypeScript, Tailwind, and Prisma
Vue Nuxt Fullstack
Nuxt 3 with Vue Composition API, Pinia, and Nitro server
Astro Content Site
Astro with content collections, Tailwind, and MDX
Go Backend Service
Go service with stdlib net/http, structured logging, and table-driven tests
Python API Backend
FastAPI or Django REST API with SQLAlchemy/Django ORM, pytest, and async patterns
Swift macOS/iOS App
SwiftUI app with Swift concurrency, SwiftData, and platform-native patterns
About crystl's NORTH-STAR.md
Most CLAUDE.md or AGENTS.md files are filled with rules, do's and don'ts, and that's fine, they have real value. But when you're building a product, doing research, or even just organizing your finances, you're guided by something else too: a mixture of goals, preferences, and values that shape where you want to end up. That's what lets you make decisions.
Agents are constantly making decisions on your behalf, by their very nature, and no amount of rules will ever cover the whole territory. That's whyNORTH-STAR.md exists. It isn't another place to put rules. It's where you say why you're doing this, who it's for, and what will make it a success, including what you've already ruled out.
No kit ships one, on purpose. The only thing a kit could put there is an empty skeleton, and an empty direction file is worse than none. Getting yours written is a conversation with the agent already in your gem: the setup pass offers it, or runcrystl northstar init any time.