初始化
- 作者仓库星标 36
- 许可证 MIT
- 作者仓库 everything-react-native-expo
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @JubaKitiashvili · MIT
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 1 步:询问偏好
在运行任何内容之前,请在一条消息中询问用户两件事: 配置文件:ERNE 使用挂钩配置文件来控制自动进行的代码质量检查的数量。询问他们想要哪一个:最少 — 几乎没有自动检查。适合快速原型设计或当您只需要没有护栏的代理时。标准——捕获常见问题(格式、console.logs、特定于平台的错误),而不会减慢速度。这是大多数人的选择。
步骤 2:运行 init 命令
一旦您了解了他们的偏好,请在 Bash 中运行:将 `<profile>` 替换为他们的选择(最小、标准或严格)。仅当他们拒绝 MCP 服务器时才添加`--no-mcp`。 `--yes` 标志很重要 - 它告诉 CLI 跳过它自己的交互式提示,因为您已经收集了首选项。
第 3 步:启动仪表板
init 完成后,启动仪表板:仪表板在后台运行。读取输出以查找它在哪个端口上启动(通常为 3333,但如果使用 3333,它会自动选择一个空闲端口)。如果仪表板需要在首次运行时安装依赖项(大约需要 2 分钟),请告诉用户它正在安装,并将在准备就绪后在浏览器中打开。
第 4 步:告诉用户发生了什么
以清晰的消息进行总结: 设置了什么(代理、挂钩、规则、技能、MCP 服务器) 仪表板 URL(例如,http://localhost:3333) 他们需要重新启动 MCP 服务器和挂钩的 Claude 代码会话才能激活 重新启动后他们可以尝试的一些命令:
# Initialize ERNE
ERNE is an AI agent harness for React Native and Expo. Setting it up involves choosing a few preferences and then running a single CLI command. The reason you need to ask the user before running is that the CLI's interactive prompts don't work reliably in Claude Code — so you handle the interaction here in conversation instead.
## 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.
- **strict** — Adds security scanning, accessibility checks, and test gates. Good for production apps or teams.
**MCP servers:** ERNE can configure agent-device (controls iOS Simulator and Android Emulator for screenshots, taps, navigation) and GitHub integration. Ask if they want these set up now or later.
Wait for the user to respond before continuing.
## Step 2: Run the init command
Once you have their preferences, run this in Bash:
```bash
npx erne-universal@latest init --yes --profile <profile> [--no-mcp]
```
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:
```bash
npx erne-universal 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:
- `/erne-plan` — plan a new feature
- `/erne-perf` — profile performance issues
- `/erne-doctor` — check project health
- `/erne-code-review` — review code quality
- Type `/erne-` and press Tab to see all commands
章节与文件索引
按说明文件中的顺序排列。
第 1 步:询问偏好
步骤 2:运行 init 命令
第 3 步:启动仪表板
第 4 步:告诉用户发生了什么
文件/命令 -> <profile> · --no-mcp · --yes · /erne-plan · /erne-perf · /erne-doctor · /erne-code-review · /erne-
内容校验值 -> 226795d71355
当前原文的自动摘译,尚未人工审校。
步骤 2:运行 init 命令
一旦您了解了他们的偏好,请在 Bash 中运行:将
<profile>替换为他们的选择(最小、标准或严格)。仅当他们拒绝 MCP 服务器时才添加--no-mcp。--yes标志很重要——它告诉 CLI 跳过它自己的交互式提示,因为您已经收集了首选项。