Jarvis Starter

JARVIS-Starter

[](https://opensource.org/licenses/MIT) [](https://claude.com/claude-code) [](https://github.com/dtdesigner36/jarvis-starter/releases) [](https://github.com/dtdesigner36/jarvis-starter/stargazers)

**A persistent project assistant for Claude Code.** Bootstraps new projects, softly adopts existing ones, and stays as a quiet helper — maintaining the wiki, recommending the right model per task, surfacing past decisions, and tracking how the project evolves.

Built for **vibe-coders** first: people who describe ideas in plain language and want the right defaults picked for them. Works for technically literate users too — every decision is optional, and you can switch off anything that gets in the way.

---

60-second tour

# 1. Install the skill in your project
npx skills add dtdesigner36/jarvis-starter --yes

# 2a. New project? Start fresh:
> jarvis start: Telegram bot for reminders with a Next.js admin panel

# 2b. Existing project? Adopt without breaking anything:
> jarvis adopt

# 3. That's it. JARVIS lives in .jarvis/ and runs via hooks.
#    Need something? Ask it:
> jarvis status
> jarvis route "refactor the auth module"
> jarvis find "pdf parser"
> jarvis audit

---

Why this exists

Starting a Claude Code project means re-inventing the same scaffolding every time: `CLAUDE.md` rules, hooks, wiki, which skills to install, which model to pick for which task. And once the project grows, keeping docs and decisions in sync with the code is a losing battle.

JARVIS solves both:

• On start — sets up architecture for the project type (Telegram bot, web app,