ears init

Other Community

Skill notes

When to Use

Starting work on a new project that has no EARS setup Onboarding a project that another developer started Upgrading a project from generic EARS to project-specific EARS After significant project restructuring

Phase 1: Project Analysis

Scan the project to build a profile: Detect language and framework: Look for package.json → Node.js/TypeScript Look for pyproject.toml or setup.py or requirements.txt → Python Look for Cargo.toml → Rust

Phase 2: Generate Project CLAUDE.md

Use the project analysis to fill in a CLAUDE.md. Use the template from this plugin's templates/PROJECT-CLAUDE.md as the base structure. If CLAUDE.md already exists: Read it fully Check if it has an EARS section If no EARS section: offer to append the EARS block

Phase 3: Create EARS Skeleton

Create the directory structure and files: traces/ directory — create if missing Initial trace.md — ask user for the current task name, create traces/<task-name>/trace.md: KNOWN_ISSUES.md — create from template if missing LEARNING.md — create if missing:

Phase 4: Multi-Tool Setup (Optional)

Ask the user: "Do you use Cursor or Codex for this project? I can generate EARS rules for them too." If Cursor is used: Generate .cursor/rules/ears-project.mdc (create .cursor/rules/ if needed): Use the templates/cursor-ears.mdc template Fill in project name and tech stack

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

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

01
Phase 1: Project Analysis

Scan the project to build a profile: Detect language and framework: Look for `package.json` → Node.js/TypeScript Look for `pyproject.toml` or `setup.py` or `requirements.txt` → Python Look for `Cargo.toml` → Rust

02
Phase 2: Generate Project CLAUDE.md

Use the project analysis to fill in a CLAUDE.md. Use the template from this plugin's `templates/PROJECT-CLAUDE.md` as the base structure. If CLAUDE.md already exists: Read it fully Check if it has an EARS section If no EARS section: offer to append the EARS block

03
Phase 3: Create EARS Skeleton

Create the directory structure and files: `traces/` directory — create if missing Initial trace.md — ask user for the current task name, create `traces/<task-name>/trace.md`: `KNOWN_ISSUES.md` — create from template if missing `LEARNING.md` — create if missing:

04
Phase 4: Multi-Tool Setup (Optional)

Ask the user: "Do you use Cursor or Codex for this project? I can generate EARS rules for them too." If Cursor is used: Generate `.cursor/rules/ears-project.mdc` (create `.cursor/rules/` if needed): Use the `templates/cursor-ears.mdc` template Fill in project name and tech stack

05
Phase 5: Hook Check (Optional)

Check if `~/.claude/scripts/ears-trace.py` exists If it exists, inform the user about the improved hook in the Synapse plugin Offer to install/upgrade: Copy `hooks/ears-trace.py` from the plugin to `~/.claude/scripts/ears-trace.py` Verify `~/.claude/settings.json` has PostToolUse hooks configured

Discussion

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