메뉴
Initialize the ~/.jarvis/ directory structure for a project. Use this skill when setting up jarvis for the first time, when the user says "init jarvis", "set up jarvis", "initialize jarvis", or when /jarvis-reload detects no JaRVIS data directory exists.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Reload jarvis identity and memories mid-session. Use this skill when the user says "reload jarvis", "refresh context", "who are you", "what do you remember", or when you need to re-read identity/memories after they've been updated during the session.
Post-task reflection and memory sculpting for jarvis. Use this skill after completing any meaningful task, when the user says "reflect", "what did we learn", "save what we did", "update memories", or after finishing a coding task, debugging session, architecture decision, or any significant unit of work. Also use when the user asks to review or consolidate memories. Writes to the JaRVIS data directory.
Apply pending JaRVIS data-dir schema migrations. Use when the user reports JaRVIS is not seeing recent data, after upgrading the plugin, or when the SessionStart hook reports a migration failure.
Evolve the jarvis agent identity based on accumulated reflections. Use this skill when the agent has completed 5 reflections since the last identity evolution, when the user says "evolve identity", "update identity", "who have you become", or when explicitly prompted by the jarvis-reflect skill.
Search across your JaRVIS data — journals, memories, identity, and growth log. Use when you want to search jarvis, find in journal, search memories, look up past reflections, find entries by tag or date, or recall what you learned about a topic.
Enable or disable JaRVIS for the current project. Use when you want to turn jarvis on or off, pause jarvis, disable jarvis hooks, or stop jarvis from loading.
| name | jarvis-init |
| description | Initialize the ~/.jarvis/ directory structure for a project. Use this skill when setting up jarvis for the first time, when the user says "init jarvis", "set up jarvis", "initialize jarvis", or when /jarvis-reload detects no JaRVIS data directory exists. |
Scaffold 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."