erne init

AI Community

Skill notes

Step 1: Ask preferences

Before running anything, ask the user two things in a single message: Profile: ERNE uses hook profiles to control how much code quality checking happens automatically. Ask which one they'd like: minimal — Almost no automated checks. Good for quick prototyping or when you just want the agents without guardrails. standard — Catches common issues (formatting, console.logs, platform-specific bugs) without slowing things down. This is what most people pick.

Step 2: Run the init command

Once you have their preferences, run this in Bash: Replace <profile> with their choice (minimal, standard, or strict). Add --no-mcp only if they said no to MCP servers. The --yes flag is important — it tells the CLI to skip its own interactive prompts since you already gathered the preferences.

Step 3: Launch the dashboard

After init completes, start the dashboard: The dashboard runs in the background. Read the output to find which port it started on (usually 3333, but it auto-selects a free port if 3333 is taken). If the dashboard needs to install dependencies on first run (takes about 2 minutes), tell the user it's installing and will open in the browser when ready.

Step 4: Tell the user what happened

Summarize in a clear message: What was set up (agents, hooks, rules, skills, MCP servers) The dashboard URL (e.g., http://localhost:3333) That they need to restart this Claude Code session for MCP servers and hooks to activate A few commands they can try after restart:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@JubaKitiashvili · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Ask preferences

Before running anything, ask the user two things in a single message: Profile: ERNE uses hook profiles to control how much code quality checking happens automatically. Ask which one they'd like: minimal — Almost no automated checks. Good for quick prototyping or when you just want the agents without guardrails. standard — Catches common issues (formatting, console.logs, platform-specific bugs) without slowing things down. This is what most people pick.

02
Step 2: Run the init command

Once you have their preferences, run this in Bash: Replace `<profile>` with their choice (minimal, standard, or strict). Add `--no-mcp` only if they said no to MCP servers. The `--yes` flag is important — it tells the CLI to skip its own interactive prompts since you already gathered the preferences.

03
Step 3: Launch the dashboard

After init completes, start the dashboard: The dashboard runs in the background. Read the output to find which port it started on (usually 3333, but it auto-selects a free port if 3333 is taken). If the dashboard needs to install dependencies on first run (takes about 2 minutes), tell the user it's installing and will open in the browser when ready.

04
Step 4: Tell the user what happened

Summarize in a clear message: What was set up (agents, hooks, rules, skills, MCP servers) The dashboard URL (e.g., http://localhost:3333) That they need to restart this Claude Code session for MCP servers and hooks to activate A few commands they can try after restart:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.