VinkyDev / vibestart

# VibeStart
**Compose. Verify. Ship.**
Compose a full-stack TypeScript stack and get a cutting-edge, verified project made for AI coding agents, with type safety, lint, and tests built in.
**English** · 简体中文
https://github.com/user-attachments/assets/aa58d60b-4776-460b-97ee-234aa331f436
## Quick start
### Compose it yourself
Pick each layer in the web studio and copy the command it builds, or answer the prompts in your terminal:
 [code] 
### Hand it to an AI agent
Paste this command, along with what you want to build, into Claude Code, Codex, Cursor, or any coding agent:
 [code] 
The agent installs the vibestart skill, chooses the stack, and creates the project. Later, ask it to add capabilities or upgrade the templates. See the Agent Skills guide.
## Why VibeStart
Full details: Why vibestart.
With a coding agent, the hard part of an application is rarely the first day. It is the thirtieth: features pile up, the structure erodes, and each fix introduces another bug. VibeStart gives the agent, and you, a better starting point: best practices for a current, carefully chosen stack, and a codebase built so that an agent writes good code in it.
- **Good code begets good code.** An agent imitates the code around it, follows written rules, and corrects itself from errors. Every project ships a consistent codebase, an `AGENTS.md` that says where and how each change is made, and checks (types, lint, tests) that report a mistake within seconds. `vp run ready` runs them all, fastest first.
- **A current stack, kept current.** Only technologies that are the current standard or clearly becoming it: TypeScript 7, React 19 with the React Compiler, Drizzle ORM 1.0, Oxlint and Oxfmt, and Vite+ as one toolchain. Open source, no vendor lock-in, one library per capability. When a better tool becomes the standard, the template moves to it and the old one is removed.
- **Composed, not copied.** Each technology is an integration with its own files, dependencies, and constraints, and the project is composed from the integrations you choose. A combination that cannot work is refused with the reason and the smallest change that fixes it.
- **Every combination is verified.** Before each release, every supported combination is covered: each file `vp run ready` reads, and every three of its choices together, have been installed, type-checked, linted, tested, tested in a browser, and built in a combination that CI ran. The passes are recorded with fingerprints on the `verification` branch, and the CLI shows a representative pass for your project when it creates it.
- **TypeScript across the stack.** One language from database to button, with types that travel from the schema through the API to the page and no code generation step. Zod validates data from outside.
- **Tests that earn their place.** End-to-end tests for whole workflows, integration tests for every API operation against a real database, and unit tests only for logic with real branches.
- **Maintained after creat