# egc - Doramagic AI Context Pack

> Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated.

## Sufficiency Principle

- **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary.
- **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work.

## How the Host AI Should Use This

You are reading the AI Context Pack that Doramagic compiled for egc. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project.

## Claim Consumption Rules

- **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure.
- **Minimum status for a fact**: `supported`
- `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path.
- `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying.
- `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact.
- `unverified`: Must not be used as fact; state clearly that evidence is insufficient.
- `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf.

## Who It Fits Best

- **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0004` supported 0.86
- **Users who want to bring professional workflows into a host AI**: The repo contains Skill documents. Evidence: `.agents/skills/agent-introspection-debugging/SKILL.md`, `.agents/skills/agent-sort/SKILL.md`, `.agents/skills/api-design/SKILL.md`, `.agents/skills/article-writing/SKILL.md` et al. Claim: `clm_0005` supported 0.86

## What It Can Do

- **AI Skill / Agent Instruction Asset Library** (Previewable before install): The project contains Skill or Agent instruction files that a host AI can read, useful for bringing professional workflows into hosts like Claude, Codex, or Cursor. Evidence: `.agents/skills/agent-introspection-debugging/SKILL.md`, `.agents/skills/agent-sort/SKILL.md`, `.agents/skills/api-design/SKILL.md`, `.agents/skills/article-writing/SKILL.md` et al. Claim: `clm_0001` supported 0.86
- **Multi-Host Install and Distribution** (Verify after install): The project contains plugin or marketplace configuration, indicating it targets install and distribution across one or more AI hosts. Evidence: `.agents/plugins/marketplace.json`, `.codex-plugin/plugin.json`, `.gemini-plugin/marketplace.json`, `.gemini-plugin/plugin.json` Claim: `clm_0002` unverified 0.25
- **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `README.md` Claim: `clm_0003` supported 0.86

## How to Start

- `npm install -g @egchq/egc && egc install` Evidence: `README.md` Claim: `clm_0006` supported 0.86
- `npx @egchq/egc install` Evidence: `README.md` Claim: `clm_0007` supported 0.86
- `npm install -g @egchq/egc` Evidence: `README.md` Claim: `clm_0006` supported 0.86, `clm_0008` supported 0.86

## Continue-or-Stop Decision Card

- **Current recommendation**: Sandbox-trial the workflow first
- **Why**: This project changes the host AI's development workflow and rules. It is worth trying, but do not install it straight into your primary Claude/Cursor/Codex; verify it first with a temporary host or an isolated directory.

### 30-Second Read

- **What to do now**: Sandbox-trial the workflow first
- **Minimum safe next step**: Feel the workflow constraints with Prompt Preview first; trial in a temporary host only once satisfied
- **Do not trust yet**: Whether this workflow fits your way of working cannot be trusted directly.
- **Continuing will touch**: Host behavior change, Command execution, Host AI configuration

### What You Can Trust Now

- **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0004` supported 0.86
- **Target-audience signal: Users who want to bring professional workflows into a host AI** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `.agents/skills/agent-introspection-debugging/SKILL.md`, `.agents/skills/agent-sort/SKILL.md`, `.agents/skills/api-design/SKILL.md`, `.agents/skills/article-writing/SKILL.md` et al. Claim: `clm_0005` supported 0.86
- **Capability exists: AI Skill / Agent Instruction Asset Library** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `.agents/skills/agent-introspection-debugging/SKILL.md`, `.agents/skills/agent-sort/SKILL.md`, `.agents/skills/api-design/SKILL.md`, `.agents/skills/article-writing/SKILL.md` et al. Claim: `clm_0001` supported 0.86
- **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `README.md` Claim: `clm_0003` supported 0.86
- **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0006` supported 0.86

### What You Cannot Trust Yet

- **Whether this workflow fits your way of working cannot be trusted directly.** (unverified): Workflow-style Skills can strongly constrain AI behavior; they can improve discipline but may also slow your current task pace. Evidence: `.agents/plugins/marketplace.json`, `.agents/skills/agent-introspection-debugging/SKILL.md`, `.agents/skills/agent-sort/SKILL.md`, `.agents/skills/api-design/SKILL.md` et al.
- **That it will not conflict with your existing Claude/Cursor/Codex rules cannot be trusted directly.** (inferred): A dev-workflow Skill changes default behaviors like clarifying, planning, testing, and verifying, so it must be tried in a temporary host. Evidence: `.agents/plugins/marketplace.json`, `.agents/skills/agent-introspection-debugging/SKILL.md`, `.agents/skills/agent-sort/SKILL.md`, `.agents/skills/api-design/SKILL.md` et al.
- **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project.
- **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment.
- **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior. Evidence: `.agents/plugins/marketplace.json`, `.agents/skills/agent-introspection-debugging/SKILL.md`, `.agents/skills/agent-sort/SKILL.md`, `.agents/skills/api-design/SKILL.md` et al.
- **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first.
- **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment. Evidence: `.agents/plugins/marketplace.json`, `.codex-plugin/plugin.json`, `.gemini-plugin/marketplace.json`, `.gemini-plugin/plugin.json`
- **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.

### What Continuing Will Touch

- **Host behavior change**: The default development rhythm of clarifying, planning, TDD, verifying, and wrapping up. Why: This kind of Skill draws both its value and its risk from strongly constraining the workflow; confirm first that you are willing to have it change how you work. Evidence: `.agents/plugins/marketplace.json`, `.agents/skills/agent-introspection-debugging/SKILL.md`, `.agents/skills/agent-sort/SKILL.md`, `.agents/skills/api-design/SKILL.md` et al.
- **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md`
- **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `.agents/plugins/marketplace.json`, `.agents/skills/agent-introspection-debugging/SKILL.md`, `.agents/skills/agent-sort/SKILL.md`, `.agents/skills/api-design/SKILL.md` et al.
- **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `.agents/plugins/marketplace.json`, `.codex-plugin/plugin.json`, `.gemini-plugin/marketplace.json`, `.gemini-plugin/plugin.json` et al.
- **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts.

### Minimum Safe Next Steps

- **Run Prompt Preview first**: Feel how it changes the AI's development rhythm first, then decide whether to let it into a real host. (applies when: Applies to any project, especially when output quality is unknown.)
- **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.)
- **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.)
- **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.)

### Exit Plan

- **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable.
- **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state.
- **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually.
- **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck.

## What Can Only Be Previewed

- Explain who the project fits and what it can do
- Demonstrate a typical conversation flow based on project docs
- Help the user decide whether it is worth installing or researching further

## What Must Be Verified After Install

- Actually installing the Skill, plugin, or CLI
- Running scripts, modifying local files, or accessing external services
- Verifying real output quality, performance, and compatibility

## Boundary & Risk Decision Card

- **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0009` inferred 0.45
- **Host AI plugin or Skill rule conflicts**: New rules may change how the user's existing host AI behaves. Mitigation: Inspect the plugin manifest and Skill files before installing, and test in isolation if needed. Evidence: `.agents/plugins/marketplace.json`, `.codex-plugin/plugin.json`, `.gemini-plugin/marketplace.json`, `.gemini-plugin/plugin.json` Claim: `clm_0010` inferred 0.45
- **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `README.md` Claim: `clm_0011` supported 0.86, `clm_0012` supported 0.86, `clm_0026` contradicted 0.20
- **Source document conflict: skill_count**: The project documentation states inconsistent counts; the AI Context Pack must warn the user not to treat any single number as a verified fact. Mitigation: Flag it as unverified in both the Human Manual and the AI Context Pack rather than forcing a single number. Evidence: `skills/general/configure-egc/SKILL.md`, `manifests/install-components.json`, `.codex-plugin/README.md`, `docs/installation.md` et al. Claim: `clm_0011` supported 0.86, `clm_0012` supported 0.86, `clm_0026` contradicted 0.20
- **Source file conflict skill_count**: multiple values `45, 81, 182, 229, 230` found; verify before real use.
- **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment.
- **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.
- **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments.

## Pre-Work Working Context

### Loading Order

- First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset.
- Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative.
- Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match.
- When you need to carry out a concrete task, check role_skill_index first, then evidence_index.
- For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required.

### Task Routes

- **AI Skill / Agent Instruction Asset Library**: Use role_skill_index / evidence_index to help the user pick a usable role, Skill, or workflow first. Boundary: Can be experienced via a pre-install Prompt. Evidence: `.agents/skills/agent-introspection-debugging/SKILL.md`, `.agents/skills/agent-sort/SKILL.md`, `.agents/skills/api-design/SKILL.md`, `.agents/skills/article-writing/SKILL.md` et al. Claim: `clm_0001` supported 0.86
- **Multi-Host Install and Distribution**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `.agents/plugins/marketplace.json`, `.codex-plugin/plugin.json`, `.gemini-plugin/marketplace.json`, `.gemini-plugin/plugin.json`
- **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `README.md` Claim: `clm_0003` supported 0.86

### Context Scale

- Total files: 1459
- Important-file coverage: 40/1459
- Evidence index entries: 180
- Role / Skill entries: 260

### Handling Insufficient Evidence

- **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts.
- **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install.
- **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run.
- **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version.

## Prompt Recipes

### Fit assessment

- Goal: Judge whether this project fits the user's current task.
- Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation.

```text
Based on the AI Context Pack for egc, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id.
```

### Pre-install experience

- Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise.
- Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language.

```text
Treat egc as a pre-install experience asset, not an already-installed tool or a real runtime environment.

Output exactly four parts:
1. Ask me 3 necessary questions first.
2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow.
3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run.
4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project.

Hard boundaries:
- Do not claim you have installed, run, executed tests, modified files, or produced real results.
- Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing".
- If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...".
- The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating".
- Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment.
- Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions.

```

### Role / Skill selection

- Goal: Pick the best-matching asset from the project's roles or Skills.
- Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed.

```text
Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs.
```

### Risk pre-check

- Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting.
- Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items.

```text
Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have.
```

### Host AI kickoff instruction

- Goal: Turn the project context into a host AI instruction for the start of a conversation.
- Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI.

```text
Based on the AI Context Pack for egc, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results.
```

## Role / Skill Index

- Indexed 260 role / Skill / project-doc entries.

- **agent-introspection-debugging** (skill): Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Activation hint: When the user's task is highly relevant to the workflow described by “agent-introspection-debugging”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/agent-introspection-debugging/SKILL.md`
- **agent-sort** (skill): Build an evidence-backed EGC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when EGC should be trimmed to what a project actually needs instead of loading the full bundle. Activation hint: When the user's task is highly relevant to the workflow described by “agent-sort”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/agent-sort/SKILL.md`
- **api-design** (skill): REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs. Activation hint: When the user's task is highly relevant to the workflow described by “api-design”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/api-design/SKILL.md`
- **article-writing** (skill): Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter. Activation hint: When the user's task is highly relevant to the workflow described by “article-writing”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/article-writing/SKILL.md`
- **backend-patterns** (skill): Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Activation hint: When the user's task is highly relevant to the workflow described by “backend-patterns”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/backend-patterns/SKILL.md`
- **brand-voice** (skill): Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes. Activation hint: When the user's task is highly relevant to the workflow described by “brand-voice”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/brand-voice/SKILL.md`
- **bun-runtime** (skill): Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support. Activation hint: When the user's task is highly relevant to the workflow described by “bun-runtime”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/bun-runtime/SKILL.md`
- **coding-standards** (skill): Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Activation hint: When the user's task is highly relevant to the workflow described by “coding-standards”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/coding-standards/SKILL.md`
- **content-engine** (skill): Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms. Activation hint: When the user's task is highly relevant to the workflow described by “content-engine”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/content-engine/SKILL.md`
- **crosspost** (skill): Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms. Activation hint: When the user's task is highly relevant to the workflow described by “crosspost”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/crosspost/SKILL.md`
- **deep-research** (skill): Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations. Activation hint: When the user's task is highly relevant to the workflow described by “deep-research”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/deep-research/SKILL.md`
- **dmux-workflows** (skill): Multi-agent orchestration using dmux tmux pane manager for AI agents . Patterns for parallel agent workflows across Gemini Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows. Activation hint: When the user's task is highly relevant to the workflow described by “dmux-workflows”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/dmux-workflows/SKILL.md`
- **documentation-lookup** (skill): Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework e.g. React, Next.js, Prisma . Activation hint: When the user's task is highly relevant to the workflow described by “documentation-lookup”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/documentation-lookup/SKILL.md`
- **e2e-testing** (skill): Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Activation hint: When the user's task is highly relevant to the workflow described by “e2e-testing”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/e2e-testing/SKILL.md`
- **egc** (skill): Development conventions and patterns for EGC - Extended Global Context. JavaScript project with conventional commits. Activation hint: When the user's task is highly relevant to the workflow described by “egc”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/egc/SKILL.md`
- **eval-harness** (skill): Formal evaluation framework for Gemini Code sessions implementing eval-driven development EDD principles Activation hint: When the user's task is highly relevant to the workflow described by “eval-harness”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/eval-harness/SKILL.md`
- **exa-search** (skill): Neural search via Exa MCP for web, code, and company research. Use when the user needs web search, code examples, company intel, people lookup, or AI-powered deep research with Exa's neural search engine. Activation hint: When the user's task is highly relevant to the workflow described by “exa-search”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/exa-search/SKILL.md`
- **fal-ai-media** (skill): Unified media generation via fal.ai MCP: image, video, and audio. Covers text-to-image Nano Banana , text/image-to-video Seedance, Kling, Veo 3 , text-to-speech CSM-1B , and video-to-audio ThinkSound . Use when the user wants to generate images, videos, or audio with AI. Activation hint: When the user's task is highly relevant to the workflow described by “fal-ai-media”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/fal-ai-media/SKILL.md`
- **frontend-patterns** (skill): Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices. Activation hint: When the user's task is highly relevant to the workflow described by “frontend-patterns”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/frontend-patterns/SKILL.md`
- **frontend-slides** (skill): Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices. Activation hint: When the user's task is highly relevant to the workflow described by “frontend-slides”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/frontend-slides/SKILL.md`
- **investor-materials** (skill): Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets. Activation hint: When the user's task is highly relevant to the workflow described by “investor-materials”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/investor-materials/SKILL.md`
- **investor-outreach** (skill): Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging. Activation hint: When the user's task is highly relevant to the workflow described by “investor-outreach”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/investor-outreach/SKILL.md`
- **market-research** (skill): Conduct market research, competitive analysis, investor due diligence, and industry intelligence with source attribution and decision-oriented summaries. Use when the user wants market sizing, competitor comparisons, fund research, technology scans, or research that informs business decisions. Activation hint: When the user's task is highly relevant to the workflow described by “market-research”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/market-research/SKILL.md`
- **mcp-server-patterns** (skill): Build MCP servers with Node/TypeScript SDK: tools, resources, prompts, Zod validation, stdio vs Streamable HTTP. Use Context7 or official MCP docs for latest API. Activation hint: When the user's task is highly relevant to the workflow described by “mcp-server-patterns”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/mcp-server-patterns/SKILL.md`
- **nextjs-turbopack** (skill): Next.js 16+ and Turbopack: incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack. Activation hint: When the user's task is highly relevant to the workflow described by “nextjs-turbopack”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/nextjs-turbopack/SKILL.md`
- **product-capability** (skill): Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an EGC-native PRD-to-SRS lane instead of vague planning prose. Activation hint: When the user's task is highly relevant to the workflow described by “product-capability”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/product-capability/SKILL.md`
- **security-review** (skill): Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns. Activation hint: When the user's task is highly relevant to the workflow described by “security-review”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/security-review/SKILL.md`
- **strategic-compact** (skill): Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction. Activation hint: When the user's task is highly relevant to the workflow described by “strategic-compact”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/strategic-compact/SKILL.md`
- **tdd-workflow** (skill): Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests. Activation hint: When the user's task is highly relevant to the workflow described by “tdd-workflow”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/tdd-workflow/SKILL.md`
- **verification-loop** (skill): A comprehensive verification system for Gemini Code sessions. Activation hint: When the user's task is highly relevant to the workflow described by “verification-loop”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/verification-loop/SKILL.md`
- **video-editing** (skill): AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content. Activation hint: When the user's task is highly relevant to the workflow described by “video-editing”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/video-editing/SKILL.md`
- **x-api** (skill): X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically. Activation hint: When the user's task is highly relevant to the workflow described by “x-api”, use it for a pre-install experience first, then decide whether to install. Evidence: `.agents/skills/x-api/SKILL.md`
- **article-writing** (skill): Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter. Activation hint: When the user's task is highly relevant to the workflow described by “article-writing”, use it for a pre-install experience first, then decide whether to install. Evidence: `.cursor/skills/article-writing/SKILL.md`
- **bun-runtime** (skill): Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support. Activation hint: When the user's task is highly relevant to the workflow described by “bun-runtime”, use it for a pre-install experience first, then decide whether to install. Evidence: `.cursor/skills/bun-runtime/SKILL.md`
- **content-engine** (skill): Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms. Activation hint: When the user's task is highly relevant to the workflow described by “content-engine”, use it for a pre-install experience first, then decide whether to install. Evidence: `.cursor/skills/content-engine/SKILL.md`
- **documentation-lookup** (skill): Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework e.g. React, Next.js, Prisma . Activation hint: When the user's task is highly relevant to the workflow described by “documentation-lookup”, use it for a pre-install experience first, then decide whether to install. Evidence: `.cursor/skills/documentation-lookup/SKILL.md`
- **frontend-slides** (skill): Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices. Activation hint: When the user's task is highly relevant to the workflow described by “frontend-slides”, use it for a pre-install experience first, then decide whether to install. Evidence: `.cursor/skills/frontend-slides/SKILL.md`
- **investor-materials** (skill): Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets. Activation hint: When the user's task is highly relevant to the workflow described by “investor-materials”, use it for a pre-install experience first, then decide whether to install. Evidence: `.cursor/skills/investor-materials/SKILL.md`
- **investor-outreach** (skill): Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging. Activation hint: When the user's task is highly relevant to the workflow described by “investor-outreach”, use it for a pre-install experience first, then decide whether to install. Evidence: `.cursor/skills/investor-outreach/SKILL.md`
- **market-research** (skill): Conduct market research, competitive analysis, investor due diligence, and industry intelligence with source attribution and decision-oriented summaries. Use when the user wants market sizing, competitor comparisons, fund research, technology scans, or research that informs business decisions. Activation hint: When the user's task is highly relevant to the workflow described by “market-research”, use it for a pre-install experience first, then decide whether to install. Evidence: `.cursor/skills/market-research/SKILL.md`
- **mcp-server-patterns** (skill): Build MCP servers with Node/TypeScript SDK: tools, resources, prompts, Zod validation, stdio vs Streamable HTTP. Use Context7 or official MCP docs for latest API. Activation hint: When the user's task is highly relevant to the workflow described by “mcp-server-patterns”, use it for a pre-install experience first, then decide whether to install. Evidence: `.cursor/skills/mcp-server-patterns/SKILL.md`
- **nextjs-turbopack** (skill): Next.js 16+ and Turbopack: incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack. Activation hint: When the user's task is highly relevant to the workflow described by “nextjs-turbopack”, use it for a pre-install experience first, then decide whether to install. Evidence: `.cursor/skills/nextjs-turbopack/SKILL.md`
- **agentic-engineering** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “agentic-engineering”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/agentic-engineering/SKILL.md`
- **api-design** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “api-design”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/api-design/SKILL.md`
- **backend-patterns** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “backend-patterns”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/backend-patterns/SKILL.md`
- **coding-standards** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “coding-standards”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/coding-standards/SKILL.md`
- **database-migrations** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “database-migrations”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/database-migrations/SKILL.md`
- **deployment-patterns** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “deployment-patterns”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/deployment-patterns/SKILL.md`
- **e2e-testing** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “e2e-testing”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/e2e-testing/SKILL.md`
- **frontend-patterns** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “frontend-patterns”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/frontend-patterns/SKILL.md`
- **golang-patterns** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “golang-patterns”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/golang-patterns/SKILL.md`
- **golang-testing** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “golang-testing”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/golang-testing/SKILL.md`
- **postgres-patterns** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “postgres-patterns”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/postgres-patterns/SKILL.md`
- **python-patterns** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “python-patterns”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/python-patterns/SKILL.md`
- **python-testing** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “python-testing”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/python-testing/SKILL.md`
- **search-first** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “search-first”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/search-first/SKILL.md`
- **security-review** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “security-review”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/security-review/SKILL.md`
- **tdd-workflow** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “tdd-workflow”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/tdd-workflow/SKILL.md`
- **verification-loop** (skill):  Activation hint: When the user's task is highly relevant to the workflow described by “verification-loop”, use it for a pre-install experience first, then decide whether to install. Evidence: `.kiro/skills/verification-loop/SKILL.md`
- **agent-eval** (skill): Head-to-head comparison of coding agents Gemini Code, Aider, Codex, etc. on custom tasks with pass rate, cost, time, and consistency metrics Activation hint: When the user's task is highly relevant to the workflow described by “agent-eval”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/agent-eval/SKILL.md`
- **agent-harness-construction** (skill): Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates. Activation hint: When the user's task is highly relevant to the workflow described by “agent-harness-construction”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/agent-harness-construction/SKILL.md`
- **agent-introspection-debugging** (skill): Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Activation hint: When the user's task is highly relevant to the workflow described by “agent-introspection-debugging”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/agent-introspection-debugging/SKILL.md`
- **agent-sort** (skill): Build an evidence-backed EGC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when EGC should be trimmed to what a project actually needs instead of loading the full bundle. Activation hint: When the user's task is highly relevant to the workflow described by “agent-sort”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/agent-sort/SKILL.md`
- **agentic-engineering** (skill): Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing. Activation hint: When the user's task is highly relevant to the workflow described by “agentic-engineering”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/agentic-engineering/SKILL.md`
- **ai-first-engineering** (skill): Engineering operating model for teams where AI agents generate a large share of implementation output. Activation hint: When the user's task is highly relevant to the workflow described by “ai-first-engineering”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/ai-first-engineering/SKILL.md`
- **autonomous-agent-harness** (skill): Transform Gemini Code into a fully autonomous agent system with persistent memory, scheduled operations, computer use, and task queuing. Replaces standalone agent frameworks Hermes, AutoGPT by leveraging Gemini Code's native crons, dispatch, MCP tools, and memory. Use when the user wants continuous autonomous operation, scheduled tasks, or a self-directing agent loop. Activation hint: When the user's task is highly relevant to the workflow described by “autonomous-agent-harness”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/autonomous-agent-harness/SKILL.md`
- **autonomous-lesson-learning** (skill): Autonomous loop that learns while it runs: recalls stored lessons before each iteration, saves new lessons on failures and wins, and reinforces known lessons instead of repeating mistakes. Orchestrates continuous-agent-loop patterns with the egc-memory lesson tools. Activation hint: When the user's task is highly relevant to the workflow described by “autonomous-lesson-learning”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/autonomous-lesson-learning/SKILL.md`
- **autonomous-loops** (skill): Patterns and architectures for autonomous Gemini Code loops: from simple sequential pipelines to RFC-driven multi-agent DAG systems. Activation hint: When the user's task is highly relevant to the workflow described by “autonomous-loops”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/autonomous-loops/SKILL.md`
- **continuous-learning-v2** (skill): Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination. Activation hint: When the user's task is highly relevant to the workflow described by “continuous-learning-v2”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/continuous-learning-v2/SKILL.md`
- **continuous-learning** (skill): Automatically extract reusable patterns from Gemini Code sessions and save them as learned skills for future use. Activation hint: When the user's task is highly relevant to the workflow described by “continuous-learning”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/continuous-learning/SKILL.md`
- **cost-aware-llm-pipeline** (skill): Cost optimization patterns for LLM API usage: model routing by task complexity, budget tracking, retry logic, and prompt caching. Activation hint: When the user's task is highly relevant to the workflow described by “cost-aware-llm-pipeline”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/cost-aware-llm-pipeline/SKILL.md`
- **deep-research** (skill): Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations. Activation hint: When the user's task is highly relevant to the workflow described by “deep-research”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/deep-research/SKILL.md`
- **exa-search** (skill): Neural search via Exa MCP for web, code, and company research. Use when the user needs web search, code examples, company intel, people lookup, or AI-powered deep research with Exa's neural search engine. Activation hint: When the user's task is highly relevant to the workflow described by “exa-search”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/exa-search/SKILL.md`
- **fal-ai-media** (skill): Unified media generation via fal.ai MCP: image, video, and audio. Covers text-to-image Nano Banana , text/image-to-video Seedance, Kling, Veo 3 , text-to-speech CSM-1B , and video-to-audio ThinkSound . Use when the user wants to generate images, videos, or audio with AI. Activation hint: When the user's task is highly relevant to the workflow described by “fal-ai-media”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/fal-ai-media/SKILL.md`
- **prompt-optimizer** (skill): - Activation hint: When the user's task is highly relevant to the workflow described by “prompt-optimizer”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/prompt-optimizer/SKILL.md`
- **regex-vs-llm-structured-text** (skill): Decision framework for choosing between regex and LLM when parsing structured text: start with regex, add LLM only for low-confidence edge cases. Activation hint: When the user's task is highly relevant to the workflow described by “regex-vs-llm-structured-text”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/regex-vs-llm-structured-text/SKILL.md`
- **token-budget-advisor** (skill): - Activation hint: When the user's task is highly relevant to the workflow described by “token-budget-advisor”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/ai/token-budget-advisor/SKILL.md`
- **agent-architecture-audit** (skill): Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature. Activation hint: When the user's task is highly relevant to the workflow described by “agent-architecture-audit”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/architecture/agent-architecture-audit/SKILL.md`
- **agentic-os** (skill): Build persistent multi-agent operating systems on Gemini CLI. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases. Activation hint: When the user's task is highly relevant to the workflow described by “agentic-os”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/architecture/agentic-os/SKILL.md`
- **android-clean-architecture** (skill): Clean Architecture patterns for Android and Kotlin Multiplatform projects: module structure, dependency rules, UseCases, Repositories, and data layer patterns. Activation hint: When the user's task is highly relevant to the workflow described by “android-clean-architecture”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/architecture/android-clean-architecture/SKILL.md`
- The remaining 180 entries are in `AI_CONTEXT_PACK.json`.

## Evidence Index

- Indexed 180 evidence entries.

- **EGC Documentation** (documentation): This directory is the canonical entry point for everything that is not the user-facing README.md at the repository root. Evidence: `docs/README.md`
- **EGC Architecture** (documentation): EGC ships one production runtime alongside an exploratory kernel direction kept under architecture/ for research and ecosystem-evolution work. This page is the index: read it first, then drill into the specific documents below. Evidence: `docs/architecture/README.md`
- **EGC Governance** (documentation): Documents that define how subsystems are classified, how skills and agents are placed and adapted, and how capability surfaces are selected. Read SUBSYSTEM-MAP.md first. Evidence: `docs/governance/README.md`
- **EGC Guides** (documentation): Operational and contributor walk-throughs. These are tutorial-shaped documents; for architecture or governance see ../architecture/ and ../governance/ . Evidence: `docs/guides/README.md`
- **VEX Documents** (documentation): This directory contains Vulnerability Exploitability eXchange VEX documents for EGC. Evidence: `docs/security/vex/README.md`
- **EGC Specification** (documentation): The EGC specification is executable. It lives in JSON Schemas under schemas/ , in install manifests under scripts/lib/ , and in tests under tests/spec/ . This document is the index that ties them together. Evidence: `docs/spec/README.md`
- **Documentacao do EGC** (documentation): Este diretorio e o ponto de entrada canonico para tudo que nao e o README.md voltado ao usuario na raiz do repositorio. Evidence: `translations/pt/docs/README.md`
- **Arquitetura do EGC** (documentation): O EGC possui um runtime de producao alem de uma direcao exploratoria de kernel mantida em architecture/ para pesquisa e evolucao do ecossistema. Esta pagina e o indice: leia primeiro, depois aprofunde-se nos documentos especificos abaixo. Evidence: `translations/pt/docs/architecture/README.md`
- **Governanca do EGC** (documentation): Documentos que definem como os subsistemas sao classificados, como skills e agentes sao posicionados e adaptados, e como as superficies de capacidade sao selecionadas. Leia SUBSYSTEM-MAP.md primeiro. Evidence: `translations/pt/docs/governance/README.md`
- **Guias do EGC** (documentation): Guias operacionais e tutoriais para contribuidores. Estes sao documentos em formato tutorial; para arquitetura ou governanca, consulte ../architecture/ e ../governance/ . Evidence: `translations/pt/docs/guides/README.md`
- **Documentos VEX** (documentation): Este diretorio contem documentos de Vulnerability Exploitability eXchange VEX para o EGC. Evidence: `translations/pt/docs/security/vex/README.md`
- **Especificacao do EGC** (documentation): A especificacao do EGC e executavel. Ela vive em JSON Schemas em schemas/ , em manifestos de instalacao em scripts/lib/ , e em testes em tests/spec/ . Este documento e o indice que os une. Evidence: `translations/pt/docs/spec/README.md`
- **Article Writing** (skill_instruction): Write long-form content that sounds like an actual person with a point of view, not an LLM smoothing itself into paste. Evidence: `skills/docs/article-writing/SKILL.md`
- **Brand Voice** (skill_instruction): Build a durable voice profile from real source material, then use that profile everywhere instead of re-deriving style from scratch or defaulting to generic AI copy. Evidence: `skills/docs/brand-voice/SKILL.md`
- **Content Engine** (skill_instruction): Build platform-native content without flattening the author's real voice into platform slop. Evidence: `skills/docs/content-engine/SKILL.md`
- **Documentation Lookup Context7** (skill_instruction): When the user asks about libraries, frameworks, or APIs, fetch current documentation via the Context7 MCP tools resolve-library-id and query-docs instead of relying on training data. Evidence: `skills/docs/documentation-lookup/SKILL.md`
- **Investor Materials** (skill_instruction): Build investor-facing materials that are consistent, credible, and easy to defend. Evidence: `skills/docs/investor-materials/SKILL.md`
- **Investor Outreach** (skill_instruction): Write investor communication that is short, concrete, and easy to act on. Evidence: `skills/docs/investor-outreach/SKILL.md`
- **Market Research** (skill_instruction): Produce research that supports decisions, not research theater. Evidence: `skills/docs/market-research/SKILL.md`
- **Machine Learning Engineering Workflow** (skill_instruction): Machine Learning Engineering Workflow Evidence: `skills/docs/mle-workflow/SKILL.md`
- **PubMed Database** (skill_instruction): Use this skill when a task needs biomedical literature from PubMed rather than general web search. Evidence: `skills/docs/scientific-db-pubmed-database/SKILL.md`
- **USPTO Database** (skill_instruction): Use this skill when a task needs official United States patent or trademark records from USPTO systems. Evidence: `skills/docs/scientific-db-uspto-database/SKILL.md`
- **gget** (skill_instruction): Use this skill when a task needs quick bioinformatics lookup across genomic reference databases with the gget CLI or Python package. Evidence: `skills/docs/scientific-pkg-gget/SKILL.md`
- **Literature Review** (skill_instruction): Use this skill when the task is to find, screen, synthesize, and cite a body of academic or technical literature. Evidence: `skills/docs/scientific-thinking-literature-review/SKILL.md`
- **Scholar Evaluation** (skill_instruction): Use this skill to evaluate academic or scientific work with a repeatable rubric. Evidence: `skills/docs/scientific-thinking-scholar-evaluation/SKILL.md`
- **SEO** (skill_instruction): Improve search visibility through technical correctness, performance, and content relevance, not gimmicks. Evidence: `skills/docs/seo/SKILL.md`
- **Custom Rules** (documentation): These calls are automatic and non-negotiable. Never wait for the user to ask. Evidence: `.agents/AGENTS.md`
- **EGC - Extended Global Context for CodeBuddy** (documentation): EGC - Extended Global Context for CodeBuddy Evidence: `.codebuddy/README.md`
- **.codex-plugin: Codex Native Plugin for EGC** (documentation): .codex-plugin: Codex Native Plugin for EGC Evidence: `.codex-plugin/README.md`
- **EGC for Codex CLI** (documentation): This supplements the root AGENTS.md with Codex-specific guidance. Evidence: `.codex/AGENTS.md`
- **Plugin Manifest Gotchas** (documentation): If you plan to edit .gemini-plugin/plugin.json , be aware that the Gemini plugin validator enforces several undocumented but strict constraints that can cause installs to fail with vague errors for example, agents: Invalid input . In particular, component fields must be arrays, agents is not a supported manifest field and must not be included in plugin.json, and a version field is required for reliable validation and installation. Evidence: `.gemini-plugin/README.md`
- **EGC - Extended Global Context for Kiro** (documentation): EGC - Extended Global Context for Kiro Evidence: `.kiro/README.md`
- **OpenCode EGC Plugin** (documentation): WARNING: This README is specific to OpenCode usage. If you installed EGC via npm e.g. npm install opencode-egc , refer to the root README instead. Evidence: `.opencode/README.md`
- **EGC - Extended Global Context for Trae** (documentation): EGC - Extended Global Context for Trae Evidence: `.trae/README.md`
- **EGC: Agent Catalog** (documentation): Extended Global Context EGC is a production-grade, multi-agent system providing 63 specialized agents, 230+ skills, 77 commands to any compatible AI coding environment. Evidence: `AGENTS.md`
- **EGC: Session Memory Protocol** (documentation): This project has persistent cross-session memory via the egc-memory MCP server. Evidence: `CLAUDE.md`
- **EGC: Session Memory Protocol** (documentation): This project has persistent cross-session memory via the egc-memory MCP server. Evidence: `GEMINI.md`
- **EGC - Extended Global Context** (documentation): 🌐 English · العربية translations/ar/README.md · Español translations/es/README.md · हिन्दी translations/hi/README.md · 日本語 translations/ja/README.md · 한국어 translations/ko/README.md · Português Brasil translations/pt/README.md · Русский translations/ru/README.md Evidence: `README.md`
- **Example Project GEMINI.md** (documentation): This is an example project-level GEMINI.md file. Place this in your project root. Evidence: `examples/GEMINI.md`
- **Hooks** (documentation): Hooks are event-driven automations that fire before or after AI tool executions. They enforce code quality, catch mistakes early, and automate repetitive checks. Evidence: `hooks/README.md`
- **Rules** (documentation): Rules are organized into a common layer plus language-specific directories: Evidence: `rules/README.md`
- **Hooks in Kiro** (documentation): 1. IDE Hooks this directory - Standalone .kiro.hook files that work in the Kiro IDE 2. CLI Hooks - Embedded in agent configuration files for CLI usage Evidence: `.kiro/hooks/README.md`
- **GAN-Style Harness Examples** (documentation): Examples showing how to use the Generator-Evaluator harness for different project types. Evidence: `examples/gan-harness/README.md`
- **Agent Orchestration** (documentation): Agent Purpose When to Use ------- --------- ------------- planner Implementation planning Complex features, refactoring architect System design Architectural decisions tdd-guide Test-driven development New features, bug fixes code-reviewer Code review After writing code security-reviewer Security analysis Before commits build-error-resolver Fix build errors When build fails e2e-runner E2E testing Critical user flows refactor-cleaner Dead code cleanup Code maintenance doc-updater Documentation Updating docs rust-reviewer Rust code review Rust projects Evidence: `rules/common/agents.md`
- **规则** (documentation): - common/ 包含通用原则: 无语言特定的代码示例。 - zh/ 包含 common 目录的中文翻译版本。 - 语言目录 扩展通用规则，包含框架特定的模式、工具和代码示例。每个文件引用其对应的通用版本。 Evidence: `rules/zh/README.md`
- **代理编排** (documentation): 代理 用途 何时使用 ------- --------- ------------ planner 实现规划 复杂功能、重构 architect 系统设计 架构决策 tdd-guide 测试驱动开发 新功能、bug 修复 code-reviewer 代码审查 编写代码后 security-reviewer 安全分析 提交前 build-error-resolver 修复构建错误 构建失败时 e2e-runner E2E 测试 关键用户流程 refactor-cleaner 死代码清理 代码维护 doc-updater 文档 更新文档 rust-reviewer Rust 代码审查 Rust 项目 Evidence: `rules/zh/agents.md`
- **scripts/runtime** (documentation): router.js , mount-all.js , unmount-all.js , and activator.js implement a dynamic skill router that would materialize skills into .agents/skills/ . Evidence: `scripts/runtime/README.md`
- **Visa Document Translator** (documentation): Automatically translate visa application documents from images to professional English PDFs. Evidence: `skills/security/visa-doc-translate/README.md`
- **src/llm: Python LLM Bridge** (documentation): Python bridge invoked by egc prompt via scripts/gemini.js . Evidence: `src/llm/README.md`
- **EGC - السياق العالمي الممتد Extended Global Context** (documentation): 🌐 English ../../README.md · العربية · Español ../es/README.md · हिन्दी ../hi/README.md · 日本語 ../ja/README.md · 한국어 ../ko/README.md · Português Brasil ../pt/README.md · Русский ../ru/README.md Evidence: `translations/ar/README.md`
- **EGC - Contexto Global Extendido** (documentation): 🌐 English ../../README.md · العربية ../ar/README.md · Español · हिन्दी ../hi/README.md · 日本語 ../ja/README.md · 한국어 ../ko/README.md · Português Brasil ../pt/README.md · Русский ../ru/README.md Evidence: `translations/es/README.md`
- **EGC - Extended Global Context** (documentation): 🌐 English ../../README.md · العربية ../ar/README.md · Español ../es/README.md · हिन्दी · 日本語 ../ja/README.md · 한국어 ../ko/README.md · Português Brasil ../pt/README.md · Русский ../ru/README.md Evidence: `translations/hi/README.md`
- **EGC - Extended Global Context** (documentation): 🌐 English ../../README.md · العربية ../ar/README.md · Español ../es/README.md · हिन्दी ../hi/README.md · 日本語 · 한국어 ../ko/README.md · Português Brasil ../pt/README.md · Русский ../ru/README.md Evidence: `translations/ja/README.md`
- **EGC - 확장된 전역 컨텍스트 Extended Global Context** (documentation): 🌐 English ../../README.md · العربية ../ar/README.md · Español ../es/README.md · हिन्दी ../hi/README.md · 日本語 ../ja/README.md · 한국어 · Português Brasil ../pt/README.md · Русский ../ru/README.md Evidence: `translations/ko/README.md`
- **EGC - Extended Global Context** (documentation): 🌐 English ../../README.md · العربية ../ar/README.md · Español ../es/README.md · हिन्दी ../hi/README.md · 日本語 ../ja/README.md · 한국어 ../ko/README.md · Português Brasil · Русский ../ru/README.md Evidence: `translations/pt/README.md`
- **EGC - Расширенный глобальный контекст Extended Global Context** (documentation): 🌐 English ../../README.md · العربية ../ar/README.md · Español ../es/README.md · हिन्दी ../hi/README.md · 日本語 ../ja/README.md · 한국어 ../ko/README.md · Português Brasil ../pt/README.md · Русский Evidence: `translations/ru/README.md`
- **Package** (package_manifest): { "name": "egc-universal", "version": "1.1.11", "description": "Extended Global Context EGC plugin for OpenCode - agents, commands, hooks, and skills", "main": "dist/index.js", "types": "dist/index.d.ts", "type": "module", "exports": { ".": { "types": "./dist/index.d.ts", "import": "./dist/index.js" }, "./plugins": { "types": "./dist/plugins/index.d.ts", "import": "./dist/plugins/index.js" }, "./tools": { "types": "./dist/tools/index.d.ts", "import": "./dist/tools/index.js" } }, "files": "dist", "commands", "prompts", "instructions", "opencode.json", "README.md" , "scripts": { "build": "tsc", "clean": "rm -rf dist", "prepublishOnly": "npm run build" }, "keywords": "opencode", "plugin", "egc… Evidence: `.opencode/package.json`
- **Package** (package_manifest): { "name": "egc-dashboard", "version": "1.0.0", "private": true, "description": "EGC real-time agent monitoring dashboard", "main": "server.js", "scripts": { "start": "node server.js" }, "dependencies": { "express": "^4.18.2", "ws": "^8.16.0" } } Evidence: `dashboard/package.json`
- **Package** (package_manifest): { "name": "mcp-proxy-pin", "version": "1.0.0", "private": true, "dependencies": { "mcp-proxy": "6.4.3" } } Evidence: `docker/package.json`
- **Package** (package_manifest): { "name": "egc-fuzz", "version": "1.0.0", "private": true, "description": "Fuzzing harness for egc-guardian validator", "dependencies": { "jsfuzz": "1.0.15" }, "overrides": { "cross-spawn": "^7.0.6", "uuid": "^11.1.1", "js-yaml": "^4.2.0" } } Evidence: `fuzz/package.json`
- The remaining 120 evidence entries are in `AI_CONTEXT_PACK.json` or `EVIDENCE_INDEX.json`.

## Rules the Host AI Must Follow

- **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `docs/README.md`, `docs/architecture/README.md`, `docs/governance/README.md`
- **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `docs/README.md`, `docs/architecture/README.md`, `docs/governance/README.md`

## Questions the User Should Answer First

- Which host AI or local environment do you plan to use it in?
- Do you just want to experience the workflow first, or are you ready to actually install?
- What matters most to you: install cost, output quality, or conflicts with your existing rules?

## Acceptance Checks

- Every capability claim can be traced back to a file path in evidence_refs.
- AI_CONTEXT_PACK.md does not package previews as a real run.
- The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes.

---

## Doramagic Context Augmentation

The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints.

## Human Manual Outline

Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph.

Host AI hard rules:
- Do not treat page titles, section order, summaries, or importance values as factual project evidence.
- When explaining the Human Manual outline, state that it is only a reading route or salience signal.
- Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph.

- **Overview**: importance `high`
  - source_paths: .clusterfuzzlite/Dockerfile, .codebuddy/README.md, .codex-plugin/README.md, .gemini-plugin/README.md, .kiro/README.md
- **Lib**: importance `high`
  - source_paths: .opencode/plugins/lib/changed-files-store.ts
- **Src**: importance `high`
  - source_paths: mcp/servers/egc-memory/src/branch-state.ts, mcp/servers/egc-memory/src/compress.ts, mcp/servers/egc-memory/src/encryption.ts, mcp/servers/egc-memory/src/index.ts, mcp/servers/egc-memory/src/integrity.ts
- **Src**: importance `high`
  - source_paths: mcp/servers/egc-guardian/src/audit-log.ts, mcp/servers/egc-guardian/src/catalog-index.ts, mcp/servers/egc-guardian/src/egc-array-crusher.ts, mcp/servers/egc-guardian/src/egc-chunk-router.ts, mcp/servers/egc-guardian/src/egc-volatile-scanner.ts

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `94288cd6395050a9640a9a01d5d171d641d12d8d`
- inspected_files: `Dockerfile`, `README.md`, `package.json`, `requirements.txt`, `docs/MAINTAINERS.md`, `docs/README.md`, `docs/ROADMAP.md`, `docs/RULES.md`, `docs/TROUBLESHOOTING.md`, `docs/architecture/ARCHITECTURE-IMPROVEMENTS.md`, `docs/architecture/EGC_2.0_BLUEPRINT.md`, `docs/architecture/EGC_2.0_TECHNICAL_DESIGN.md`, `docs/architecture/README.md`, `docs/architecture/SELECTIVE-INSTALL-ARCHITECTURE.md`, `docs/architecture/SELECTIVE-INSTALL-DESIGN.md`, `docs/architecture/SINGLE-AGENT-OPERATIONAL-MODEL.md`, `docs/architecture/continuous-learning-v2-spec.md`, `docs/architecture/cross-harness.md`, `docs/governance/README.md`, `docs/governance/SKILL-PLACEMENT-POLICY.md`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

### Constraint 1: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: feat(install): add native Cline install target
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: feat(install): add native Cline install target. Context: Observed when using node, python
- Why it matters: Developers may fail before the first successful local run: feat(install): add native Cline install target
- Evidence: failure_mode_cluster:github_issue | https://github.com/Fmarzochi/EGC/issues/846
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: feat(install): add native JetBrains Junie install target
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: feat(install): add native JetBrains Junie install target. Context: Observed when using node, python
- Why it matters: Developers may fail before the first successful local run: feat(install): add native JetBrains Junie install target
- Evidence: failure_mode_cluster:github_issue | https://github.com/Fmarzochi/EGC/issues/847
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: feat(install): add native Qwen Code install target
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: feat(install): add native Qwen Code install target. Context: Observed when using node, python
- Why it matters: Developers may fail before the first successful local run: feat(install): add native Qwen Code install target
- Evidence: failure_mode_cluster:github_issue | https://github.com/Fmarzochi/EGC/issues/845
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Configuration risk requires verification

- Trigger: Developers should check this configuration risk before relying on the project: v1.1.10
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v1.1.10. Context: Source discussion did not expose a precise runtime context.
- Why it matters: Upgrade or migration may change expected behavior: v1.1.10
- Evidence: failure_mode_cluster:github_release | https://github.com/Fmarzochi/EGC/releases/tag/v1.1.10
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Configuration risk requires verification

- Trigger: Developers should check this configuration risk before relying on the project: v1.1.11
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v1.1.11. Context: Observed when using node
- Why it matters: Upgrade or migration may change expected behavior: v1.1.11
- Evidence: failure_mode_cluster:github_release | https://github.com/Fmarzochi/EGC/releases/tag/v1.1.11
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.
