From jarvis
Scaffolds the ~/.jarvis/ data directory with identity, memories, and journal after detecting the platform (Claude Code, Cursor, etc.) and optional migration from legacy .jarvis/ projects.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jarvis:jarvis-initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Scaffold the JaRVIS data directory so the agent has a place to store its identity, memories, and journal.
references/AGENTS.md.examplereferences/CLAUDE.md.examplereferences/copilot-hooks.json.examplereferences/copilot-instructions.examplereferences/cursorrules.examplereferences/opencode-instructions.examplereferences/opencode-plugin.ts.examplereferences/platform-antigravity.mdreferences/platform-claude-code.mdreferences/platform-copilot.mdreferences/platform-cursor.mdreferences/platform-opencode.mdreferences/platform-other.mdreferences/scaffolding.mdscripts/jarvis-init.shscripts/resolve-dir.shScaffold the JaRVIS data directory so the agent has a place to store its identity, memories, and journal.
If .jarvis/ exists in the project root, this project used the old per-project storage layout. Offer to migrate:
.jarvis/ in the project root. Would you like to migrate it to the new home-directory location?"--migrate for the next step.--migrate (the old directory is left untouched).If no .jarvis/ exists in the project root, skip this step.
Determine which AI coding agent platform is running. Check for these signals in order:
| Signal | Platform |
|---|---|
CLAUDE_PROJECT_DIR env var or .claude/ directory exists | Claude Code |
.cursor/ directory exists | Cursor |
.github/ directory with copilot config exists | GitHub Copilot |
opencode.json or .opencode/ directory exists | OpenCode |
.agent/ directory or AGENTS.md exists | Antigravity |
If multiple signals are detected, ask the user which platform they're using (include "Other" as an option).
If no signals are detected, ask the user to choose from: Claude Code, Cursor, GitHub Copilot, Antigravity, or Other.
First, determine the skills base directory (SKILLS_DIR) for the detected platform:
| Platform | Local (project) | Global (user home) | Plugin |
|---|---|---|---|
| Claude Code | .claude/skills | ~/.claude/skills | $CLAUDE_PLUGIN_ROOT/skills (if installed as plugin) |
| Cursor | .cursor/skills | ~/.cursor/skills | — |
| GitHub Copilot | .github/skills | ~/.github/skills | — |
| OpenCode | .opencode/skills | ~/.config/opencode/skills | — |
| Antigravity | .agent/skills | ~/.agent/skills | — |
For Claude Code: if $CLAUDE_PLUGIN_ROOT is set and $CLAUDE_PLUGIN_ROOT/skills/jarvis-reload/ exists, JaRVIS is installed as a plugin — use $CLAUDE_PLUGIN_ROOT/skills. Otherwise check local then global.
For other platforms: check if the local path contains JaRVIS skills (e.g., <local-path>/jarvis-reload/ exists). If so, use the local path. Otherwise use the global path.
Call the result SKILLS_DIR.
Run the init script to resolve the path, scaffold the directory, and create a git repo:
bash $SKILLS_DIR/jarvis-init/scripts/jarvis-init.sh [--migrate] [--project-dir <path>]
--migrate if the user agreed to migrate in Step 1.--project-dir <path> if the project root differs from CLAUDE_PROJECT_DIR / pwd.The script prints ALREADY_EXISTS followed by the path if already initialized — inform the user and suggest /jarvis-reload.
Otherwise it prints MIGRATED (if migration happened) followed by the resolved path.
After successful migration, suggest the user remove the old .jarvis/ directory at their convenience.
Then read and follow the corresponding setup guide:
| Platform | Reference |
|---|---|
| Claude Code | references/platform-claude-code.md |
| Cursor | references/platform-cursor.md |
| GitHub Copilot | references/platform-copilot.md |
| OpenCode | references/platform-opencode.md |
| Antigravity | references/platform-antigravity.md |
| Other | references/platform-other.md |
Read the reference document for the detected platform and execute all steps within it.
Use <slug> from Step 4 and SKILLS_DIR from Step 3 wherever the guide references them.
Confirm the setup is complete:
"JaRVIS is initialized. Your agent data is stored at
<resolved-path>with its own git history. Run/jarvis-reloadto begin your first session, then/jarvis-reflectafter completing tasks to start building your identity."
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub epicrunze/jarvis --plugin jarvis