From ijoka
Initialize a new project in the Ijoka graph database for structured task management.
npx claudepluginhub shakestzd/ijoka --plugin ijoka# /init-project Initialize a new project in the Ijoka graph database for structured task management. ## What This Command Does Registers the current project in Ijoka's Memgraph database and helps you define initial features. Projects are identified by their **git repository root** - all subdirectories within a git repo belong to the same project. ## Prerequisites Before running this command, ensure: 1. **Memgraph is running**: `docker compose up -d` (from ijoka repo) 2. **Ijoka CLI is installed**: `ijoka --version` should work 3. **uv is installed**: `uv --version` should show 0.8.0+ f...
/init-projectInitializes new project with essential directory structure, git repo, README, framework-specific configs (React/Vue/Angular/Express/FastAPI/etc.), TypeScript/linting/testing/build tools, and GitHub Actions CI/CD.
/init-projectInitializes new project with essential directory structure, git repo, README, framework-specific configs (React/Vue/Angular/Express/FastAPI/etc.), TypeScript/linting/testing/build tools, and GitHub Actions CI/CD.
/init-projectInitializes project by interactively generating CLAUDE.md (overview, stack, structure), spec.md (feature specs), and prompt_plan.md (phased implementation plan). Auto-detects tech stack; supports [name] [--type next|vite|go|python|rust].
/init-projectScans current codebase to auto-generate project-level CLAUDE.md with detected stack, conventions, domain context, team rules, and clarifying questions.
/init-projectConfigures repo for Obsidian PKM: detects/links vault project folder, scaffolds index if needed, updates CLAUDE.md with PKM path annotation and integration section.
/init-projectInitialize project with constitution, standards, and docs structure for AI-augmented development
Initialize a new project in the Ijoka graph database for structured task management.
Registers the current project in Ijoka's Memgraph database and helps you define initial features. Projects are identified by their git repository root - all subdirectories within a git repo belong to the same project.
Before running this command, ensure:
docker compose up -d (from ijoka repo)ijoka --version should workuv --version should show 0.8.0+ for full Python supportRun /init-project and provide:
User: /init-project
Claude will:
ijoka statusijoka feature create/ijoka:start or ijoka status CLIijoka feature start <ID> CLI to begin work (or /next-feature)ijoka feature complete CLI when done (or /complete-feature)ijoka plan set CLI to declare implementation stepsWhen the user runs this command:
Check uv installation:
uv --version
curl -LsSf https://astral.sh/uv/install.sh | sh"pip install --upgrade uv"IMPORTANT: In Ijoka, a project is defined by its git repository root. All work attribution depends on git.
git rev-parse --show-toplevel to find the git rootgit init and create an initial commit.gitignore file with common patternsSearch for existing AI agent configuration files in the project root:
Known config files:
CLAUDE.md / claude.md / .claude.md - Claude CodeGEMINI.md / gemini.md / .gemini.md - Google GeminiCURSOR.md / cursor.md / .cursorrules - Cursor IDECOPILOT.md / copilot.md - GitHub CopilotAGENT.md / agent.md / AI.md - Generic agent configsFor each config file found:
Ask the user:
"I found the following agent config files:
- CLAUDE.md (Python section: yes/no)
- GEMINI.md (Python section: yes/no)
Ijoka uses uv for reproducible Python execution. Would you like me to add Python standards to config files that don't have them?
This ensures all AI agents (Claude, Gemini, Cursor, etc.) follow the same Python execution rules."
If user agrees, add the following section to each config file missing Python standards:
### Python (CRITICAL)
**See Ijoka's `PYTHON_STANDARDS.md` for full details.**
Key rules:
- **ALWAYS use `uv run` to execute Python scripts** - never `python3` directly
- Scripts with dependencies MUST have uv shebang: `#!/usr/bin/env -S uv run --script`
```bash
# ✅ CORRECT
uv run script.py
# ❌ WRONG - will fail with missing dependencies
python3 script.py
### Step 5: Check Connectivity
- Run `ijoka status` to verify Memgraph is running
- If connection fails, inform user to start Memgraph: `docker compose up -d`
### Step 6: Gather Project Info
- Ask what project they're working on and its main goals
- Note: The project path will be the git root, not the current directory
### Step 7: Define Features
Help identify 5-10 initial features:
- For each feature, determine the appropriate category
- Write clear, actionable descriptions
- Add verification steps for each feature
### Step 8: Create Features
For each feature:
```bash
ijoka feature create --category "functional" --priority 100 "Feature description"
Decrease priority by 10 for each subsequent feature.
Show the created features and explain:
/ijoka:start at session start/next-feature to pick up work/complete-feature when doneIf the project has an existing feature_list.json file, suggest running /migrate to import those features into the graph database.
Remember: PROJECT = GIT REPOSITORY