mirror of
https://github.com/affaan-m/ECC.git
synced 2026-10-16 05:05:30 +02:00
Affaan MustafaandGitHub
c05b2d6614
* chore: retire the Everything Claude Code name, ECC only Replace the expanded product name and the everything-claude-code slug with ECC across READMEs, translated docs, harness folders, skills, commands, scripts and examples. Repo URLs now point at affaan-m/ECC. Rename repo-internal artifacts to ecc forms (ecc-conventions skill, ecc-guardrails, ecc-research-playbook, ecc-team-config, ecc-instincts with ecc-* ids) and update .claude/ecc-tools.json. Legacy install ids, plugin dirs, package names and MCP prefixes stay where existing installs resolve against them. The codex global-state check and harness-audit repo detection accept the new name first and the legacy one as a fallback. The Discord bot prefers ~/GitHub/ECC and falls back to the nested legacy checkout path. Refresh the skill-triggers registryDigest for the changed skill text. * fix(ecc-tools): drop managed paths to the removed Claude repo skill .claude/skills/<repo-skill>/SKILL.md was deleted in #2770 but stayed listed in ecc-tools.json and the team config. Remove those entries and point the Claude Code adapter at the existing .agents/skills/ecc-conventions/SKILL.md.
94 lines
3.1 KiB
Markdown
94 lines
3.1 KiB
Markdown
---
|
|
description: Navigate ECC's current agents, skills, commands, hooks, install profiles, and docs from the live repository surface. This is the slash-command entrypoint for that navigation; the ecc-guide skill covers the same map for on-demand use in conversation.
|
|
---
|
|
|
|
# /ecc-guide
|
|
|
|
Use this command as a conversational map of ECC. It should help the user discover the right ECC surface for their task without dumping the entire README or stale catalog counts.
|
|
|
|
## Usage
|
|
|
|
```text
|
|
/ecc-guide
|
|
/ecc-guide setup
|
|
/ecc-guide skills
|
|
/ecc-guide commands
|
|
/ecc-guide hooks
|
|
/ecc-guide install
|
|
/ecc-guide find: <query>
|
|
/ecc-guide <feature-or-file-name>
|
|
```
|
|
|
|
## Operating Rules
|
|
|
|
1. Read current repository files before answering when the checkout is available.
|
|
2. Prefer current filesystem/catalog data over hard-coded counts.
|
|
3. Keep the first answer short, then offer specific drill-down paths.
|
|
4. Link users to canonical files instead of copying long sections.
|
|
5. Do not invent commands, skills, agents, or install profiles that are not present.
|
|
|
|
## What To Inspect
|
|
|
|
Use these files as the canonical map:
|
|
|
|
- `README.md` for install paths, reset/uninstall guidance, and high-level positioning
|
|
- `AGENTS.md` for contributor and project-structure guidance
|
|
- `agent.yaml` for exported agent and command surface
|
|
- `commands/` for maintained slash-command shims
|
|
- `skills/*/SKILL.md` for reusable skill workflows
|
|
- `agents/*.md` for delegated agent roles
|
|
- `hooks/README.md` and `hooks/hooks.json` for hook behavior
|
|
- `manifests/install-*.json` for selective install modules, components, and profiles
|
|
- `scripts/ci/catalog.js --json` for live catalog counts when running inside ECC
|
|
|
|
## Response Patterns
|
|
|
|
### No Arguments
|
|
|
|
Give a compact menu:
|
|
|
|
- setup and install
|
|
- choosing skills
|
|
- command compatibility shims
|
|
- agents and delegation
|
|
- hooks and safety
|
|
- troubleshooting an install
|
|
- finding a specific feature
|
|
|
|
Then ask what they want to do next.
|
|
|
|
### Topic Lookup
|
|
|
|
For topics like `skills`, `commands`, `hooks`, `install`, or `agents`:
|
|
|
|
1. Summarize the current surface in 3-6 bullets.
|
|
2. Point to the canonical directories/files.
|
|
3. Suggest one or two commands that can verify the state.
|
|
4. Avoid exhaustive lists unless the user asks for one.
|
|
|
|
### Search Mode
|
|
|
|
For `find: <query>`:
|
|
|
|
1. Search the relevant files with `rg`.
|
|
2. Group results by surface: skills, commands, agents, rules, docs, hooks.
|
|
3. Return the strongest matches first with file paths.
|
|
4. Recommend the next action for each match.
|
|
|
|
### Feature Lookup
|
|
|
|
For a specific feature name:
|
|
|
|
1. Check exact paths first, such as `skills/<name>/SKILL.md`, `commands/<name>.md`, and `agents/<name>.md`.
|
|
2. If exact lookup fails, search with `rg`.
|
|
3. Explain what the feature does, when to use it, and what file is canonical.
|
|
4. Mention adjacent features only when they reduce confusion.
|
|
|
|
## Related Commands
|
|
|
|
- `/project-init` for stack-aware ECC onboarding of a target project
|
|
- `/harness-audit` for deterministic repo readiness scoring
|
|
- `/skill-health` for skill quality checks
|
|
- `/skill-create` for extracting a new skill from local git history
|
|
- `/security-scan` for Claude/OpenCode configuration security review
|