# claude-code-everything-you-need-to-know - 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 claude-code-everything-you-need-to-know. 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

- **AI researchers or builders of research-oriented Agents**: The README clearly centers on research, experiment, or paper workflows. Evidence: `README.md` Claim: `clm_0002` supported 0.86
- **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_0003` supported 0.86

## What It Can Do

- **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_0001` supported 0.86

## How to Start

- `npm install -g @anthropic-ai/claude-code` Evidence: `README.md` Claim: `clm_0004` supported 0.86
- `claude mcp add <server> npx '@<package>@latest'   # install a server` Evidence: `README.md` Claim: `clm_0005` supported 0.86

## Continue-or-Stop Decision Card

- **Current recommendation**: Trial role matching first
- **Why**: This project is more of a role library; the core risk is picking the wrong role or treating role copy as execution capability. Trial role matching with Prompt Preview first, then decide whether to sandbox-import it.

### 30-Second Read

- **What to do now**: Trial role matching first
- **Minimum safe next step**: Trial role matching with Prompt Preview first; import in isolation only once satisfied
- **Do not trust yet**: Role quality and task fit cannot be trusted directly.
- **Continuing will touch**: Role selection bias, Command execution, Local environment or project files

### What You Can Trust Now

- **Target-audience signal: AI researchers or builders of research-oriented Agents** (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_0002` supported 0.86
- **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_0003` 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_0001` 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_0004` supported 0.86

### What You Cannot Trust Yet

- **Role quality and task fit cannot be trusted directly.** (unverified): A role library proves there are many roles; it does not prove each one fits your specific task or that a role produces high-quality results.
- **Do not treat role copy as real execution capability.** (unverified): Before install you can only judge whether the role description and task profile match; you cannot prove it can complete the task inside the host AI.
- **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.
- **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.
- **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

- **Role selection bias**: The user's judgment about which expert role should handle the task. Why: Picking the wrong role makes the AI answer from the wrong expert perspective, wasting time or misleading decisions.
- **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`
- **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: `README.md`
- **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**: Use an interactive trial to verify the task profile and role match first; do not import the whole role library up front. (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.)
- **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.
- **Keep a record of the original role selection**: If output goes off-topic, you can return to the task-profiling stage and reselect a role instead of pushing on with the wrong one.
- **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_0006` 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_0007` supported 0.86
- **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

- **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_0001` supported 0.86

### Context Scale

- Total files: 60
- Important-file coverage: 40/60
- Evidence index entries: 56
- Role / Skill entries: 46

### 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 claude-code-everything-you-need-to-know, 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 claude-code-everything-you-need-to-know 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 claude-code-everything-you-need-to-know, 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 46 role / Skill / project-doc entries.

- **Claude Code: Everything You Need to Know** (project_doc): Claude Code: Everything You Need to Know Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `README.md`
- **MCP Servers Documentation** (project_doc): This directory contains comprehensive documentation for the four core Model Context Protocol MCP servers that enhance Claude Code's capabilities. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp-servers/README.md`
- **Contributing** (project_doc): Thanks for your interest in improving this guide. This is a learning resource — clear, practical, and beginner-friendly explanations beat thorough-but-overwhelming ones. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CONTRIBUTING.md`
- **Changelog — Claude Code & Ecosystem Updates** (project_doc): Changelog — Claude Code & Ecosystem Updates Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/reference/changelog.md`
- **Reasoning Effort Levels** (project_doc): ~8 min read · ← Back to README ../../README.md prompt-engineering-deep-dive Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/reference/effort-levels.md`
- **FAQ — Claude Code & Claude Plans** (project_doc): ← Back to README ../../README.md faq Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/reference/faq.md`
- **Further reading** (project_doc): ← Back to README ../../README.md references Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/reference/further-reading.md`
- **Models — Specifications & Pricing** (project_doc): ← Back to README ../../README.md the-claude-5-era-todays-model-lineup Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/reference/models.md`
- **Claude Skills — The Complete Guide** (project_doc): ~30 min read · ← Back to README ../README.md claude-skills Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/skills.md`
- **Memory MCP Server** (project_doc): The Memory server allows Claude Code to store and retrieve information across sessions , providing persistent context, remembering project details, and maintaining user preferences. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp-servers/memory.md`
- **Playwright MCP Server** (project_doc): The Playwright server provides browser automation capabilities for Claude Code, enabling web interaction, scraping, testing, and structured accessibility-based navigation. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp-servers/playwright.md`
- **Sequential Thinking MCP Server** (project_doc): The Sequential Thinking server helps Claude Code break down complex problems into manageable steps , improving reasoning and multi-step task execution. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp-servers/sequential-thinking.md`
- **Serena MCP Server** (project_doc): Serena provides semantic code intelligence for Claude Code, enabling project understanding, symbol-level navigation, and intelligent editing across multiple programming languages. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp-servers/serena.md`
- **coder-reviewer** (project_doc): Use this agent for code quality review of completed implementations — assessing maintainability, performance, test coverage, and standards compliance as the final quality gate before security review. For example: reviewing a finished frontend/backend feature and producing prioritized findings Blocker/High-Priority/Medium/Nitpick with actionable fixes. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.claude/agents/coder-reviewer.md`
- **frontend-engineer** (project_doc): Use this agent to implement user-facing features — transforming UX designs and technical specifications into responsive, accessible, high-performance user interfaces with API integration and tests. Delegate frontend build work such as UI components, styling, client-side state and data handling, or web performance optimization. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.claude/agents/frontend-engineer.md`
- **project-manager** (project_doc): Use this agent for comprehensive project planning, cross-functional team coordination, progress tracking, and delivery management of development initiatives. For example: planning a 6-week user authentication project across a UX designer, backend developer, and QA tester, or regaining control of a project facing delays and scope creep. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.claude/agents/project-manager.md`
- **tech-lead-architect** (project_doc): Use this agent for technical architecture design, technology stack decisions, and system design specifications — engage after UX/design requirements are established but before detailed implementation begins. For example: planning the architecture for an event management dashboard from completed UX designs, choosing the stack and patterns for a new microservices project, or recommending scaling strategies for perform… Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.claude/agents/tech-lead-architect.md`
- **ux-designer** (project_doc): Use this agent for UX and UI design work — user research, journey maps, wireframes, interactive prototypes, design systems, and WCAG-compliant design specifications ready for development handoff. Delegate when designs need to be created or validated before technical architecture and implementation begin. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.claude/agents/ux-designer.md`
- **Five Whys Analysis** (project_doc): Apply the Five Whys root cause analysis technique to investigate issues. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.claude/commands/five.md`
- **Create Pull Request Command** (project_doc): Create a new branch, commit changes, and submit a pull request. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.claude/commands/pr.md`
- **PR Review** (project_doc): Instructions : Execute each task in the order given to conduct a thorough code review. Update GitHub with this review. Important : The future is now—any improvements or “future” recommendations must be addressed immediately . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.claude/commands/review.md`
- **High-level flow** (project_doc): This outlines the development practices and principles we require you to follow. Don't start working on features until asked, this document is intended to get you into the right state of mind. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.claude/commands/tdd.md`
- **User Experience Designer & UI Specialist Persona** (project_doc): User Experience Designer & UI Specialist Persona Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.claude/commands/ux.md`
- **Slash Commands — Cheatsheet** (project_doc): ← Back to README ../../README.md claude-commands Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/reference/commands.md`
- **Your Role in the Development Pipeline** (project_doc): You are a senior Backend Engineer with 8+ years of experience in server-side development, API design, and distributed systems. You specialize in building robust, scalable, and secure backend applications that power modern web and mobile applications. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/system-prompts/backend-engineer-prompt.md`
- **Your Role in the Development Pipeline** (project_doc): You are a senior Code Reviewer with 12+ years of experience in software development and code quality assurance. You specialize in identifying code quality issues, performance optimization opportunities, and ensuring adherence to best practices across multiple programming languages and frameworks. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/system-prompts/code-reviewer-prompt.md`
- **Your Role in the Development Pipeline** (project_doc): You are a senior Database Engineer with 8+ years of experience in database design, performance optimization, and data architecture. You specialize in creating robust, scalable, and secure database solutions that serve as the foundation for high-performance applications. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/system-prompts/database-engineer-prompt.md`
- **Your Role in the Development Pipeline** (project_doc): You are a senior Frontend Engineer with 7+ years of experience in modern web development, specializing in creating responsive, accessible, and high-performance user interfaces. You excel at transforming design specifications into production-ready applications with excellent user experiences. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/system-prompts/frontend-engineer-prompt.md`
- **Your Role in the Development Pipeline** (project_doc): You are a senior Security Reviewer with 10+ years of experience in cybersecurity, application security testing, and compliance validation. You specialize in identifying security vulnerabilities, conducting threat assessments, and ensuring applications meet security standards before production deployment. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/system-prompts/security-reviewer-prompt.md`
- **Your Role in the Development Pipeline** (project_doc): You are a senior Tech Lead with 10+ years of experience in software architecture, system design, and technical leadership. You excel at transforming user experience requirements into robust, scalable technical solutions while mentoring development teams and ensuring architectural excellence. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/system-prompts/tech-lead-prompt.md`
- **✅ LLM Unit Testing Best Practices Checklist** (project_doc): ✅ LLM Unit Testing Best Practices Checklist Focused on testing internal logic, not API endpoints Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.claude/commands/test.md`
- **Security Policy** (project_doc): This repo ships executable examples — Python hook scripts in .claude/hooks/ .claude/hooks and skills in .claude/commands/ .claude/commands that run with your shell permissions when you copy them into a project. Review them like any shell script before use the guide itself preaches the same docs/skills.md skills-faq . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `SECURITY.md`
- **todo** (project_doc): Manage project todos in todos.md file Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `.claude/commands/todo.md`
- **Role Overview** (project_doc): The Backend Engineer serves as the server-side implementation specialist in the development pipeline, transforming technical specifications and database designs into robust, scalable, and secure server-side applications. They create the business logic layer that connects frontend user interfaces with database operations. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/Descriptions/backend-engineer-description.md`
- **Role Overview** (project_doc): The Business Analyst serves as the first point of contact in the development pipeline, responsible for transforming raw ideas and business needs into structured, actionable requirements. They bridge the gap between stakeholders and the technical team. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/Descriptions/business-analyst-description.md`
- **Role Overview** (project_doc): The Code Reviewer serves as the quality gatekeeper in the development pipeline, ensuring that all code implementations meet established standards for maintainability, performance, security, and best practices. They provide the final technical validation before code progresses to security review and production deployment. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/Descriptions/code-reviewer-description.md`
- **Role Overview** (project_doc): The Database Engineer serves as the data foundation specialist in the development pipeline, transforming technical architecture specifications into optimized, secure, and scalable database solutions. They ensure data integrity, performance, and accessibility for both Frontend and Backend Engineers. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/Descriptions/database-engineer-description.md`
- **Core Responsibilities** (project_doc): The Frontend Engineer serves as the user-facing implementation specialist in the development pipeline, transforming UX designs and technical specifications into responsive, accessible, and performant user interfaces. They bridge the gap between design vision and interactive user experiences. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/Descriptions/frontend-engineer-description.md`
- **Role Overview** (project_doc): The Project Manager serves as the central orchestrator in the development pipeline, taking validated business requirements and transforming them into executable project plans. They coordinate between all specialists to ensure timely, quality delivery within scope and budget. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/Descriptions/project-manager-description.md`
- **Core Responsibilities** (project_doc): The Security Reviewer serves as the final security gatekeeper in the development pipeline, conducting comprehensive security assessments of the complete application to identify vulnerabilities, ensure compliance with security standards, and validate that security best practices are properly implemented throughout the system. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/Descriptions/security-reviewer-description.md`
- **Role Overview** (project_doc): The Tech Lead serves as the technical decision-maker and architecture authority in the development pipeline, transforming user experience designs into robust, scalable technical solutions. They bridge the gap between design vision and implementation reality while ensuring technical excellence and maintainability. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/Descriptions/tech-lead-description.md`
- **Role Overview** (project_doc): The UX Engineer serves as the user advocate in the development pipeline, transforming business requirements and project plans into intuitive, accessible, and engaging user experiences. They bridge the gap between user needs and technical implementation through research-driven design. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/Descriptions/ux-engineer-description.md`
- **Your Role in the Development Pipeline** (project_doc): You are an expert Business Analyst with 10+ years of experience in requirements gathering, process analysis, and stakeholder management. You specialize in transforming business ideas into structured, actionable requirements that drive successful project outcomes. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/system-prompts/business-analyst-prompt.md`
- **Phase 0: Preparation** (project_doc): You are an elite design review specialist with deep expertise in user experience, visual design, accessibility, and front-end implementation. You conduct world-class design reviews following the rigorous standards of top Silicon Valley companies like Stripe, Airbnb, and Linear. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/system-prompts/design-reviewer.md`
- **Your Role in the Development Pipeline** (project_doc): You are a senior Project Manager with 12+ years of experience leading complex software development projects across various industries. You excel at turning business requirements into executable plans and orchestrating cross-functional teams to deliver high-quality solutions on time and within budget. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/system-prompts/project-manager-prompt.md`
- **Your Role in the Development Pipeline** (project_doc): You are a senior UX Engineer with 8+ years of experience in user-centered design, specializing in creating intuitive, accessible, and engaging digital experiences. You have deep expertise in user research, interaction design, and design systems, with a strong understanding of technical implementation constraints. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `specialized-agents/system-prompts/ux-engineer-prompt.md`

## Evidence Index

- Indexed 56 evidence entries.

- **Claude Code: Everything You Need to Know** (documentation): Claude Code: Everything You Need to Know Evidence: `README.md`
- **MCP Servers Documentation** (documentation): This directory contains comprehensive documentation for the four core Model Context Protocol MCP servers that enhance Claude Code's capabilities. Evidence: `mcp-servers/README.md`
- **Contributing** (documentation): Thanks for your interest in improving this guide. This is a learning resource — clear, practical, and beginner-friendly explanations beat thorough-but-overwhelming ones. Evidence: `CONTRIBUTING.md`
- **Changelog — Claude Code & Ecosystem Updates** (documentation): Changelog — Claude Code & Ecosystem Updates Evidence: `docs/reference/changelog.md`
- **Reasoning Effort Levels** (documentation): ~8 min read · ← Back to README ../../README.md prompt-engineering-deep-dive Evidence: `docs/reference/effort-levels.md`
- **FAQ — Claude Code & Claude Plans** (documentation): ← Back to README ../../README.md faq Evidence: `docs/reference/faq.md`
- **Further reading** (documentation): ← Back to README ../../README.md references Evidence: `docs/reference/further-reading.md`
- **Models — Specifications & Pricing** (documentation): ← Back to README ../../README.md the-claude-5-era-todays-model-lineup Evidence: `docs/reference/models.md`
- **License** (source_file): Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Evidence: `LICENSE`
- **Claude Skills — The Complete Guide** (documentation): ~30 min read · ← Back to README ../README.md claude-skills Evidence: `docs/skills.md`
- **Memory MCP Server** (documentation): The Memory server allows Claude Code to store and retrieve information across sessions , providing persistent context, remembering project details, and maintaining user preferences. Evidence: `mcp-servers/memory.md`
- **Playwright MCP Server** (documentation): The Playwright server provides browser automation capabilities for Claude Code, enabling web interaction, scraping, testing, and structured accessibility-based navigation. Evidence: `mcp-servers/playwright.md`
- **Sequential Thinking MCP Server** (documentation): The Sequential Thinking server helps Claude Code break down complex problems into manageable steps , improving reasoning and multi-step task execution. Evidence: `mcp-servers/sequential-thinking.md`
- **Serena MCP Server** (documentation): Serena provides semantic code intelligence for Claude Code, enabling project understanding, symbol-level navigation, and intelligent editing across multiple programming languages. Evidence: `mcp-servers/serena.md`
- **Your Role in the Development Pipeline** (documentation): You are a senior Code Reviewer with 12+ years of experience in software development and code quality assurance. You specialize in identifying code quality issues, performance optimization opportunities, and ensuring adherence to best practices across multiple programming languages and frameworks. Evidence: `.claude/agents/coder-reviewer.md`
- **Your Role in the Development Pipeline** (documentation): You are a senior Frontend Engineer with 7+ years of experience in modern web development, specializing in creating responsive, accessible, and high-performance user interfaces. You excel at transforming design specifications into production-ready applications with excellent user experiences. Evidence: `.claude/agents/frontend-engineer.md`
- **Your Core Expertise** (documentation): You are an expert Project Manager with extensive experience orchestrating complex development projects across diverse teams and methodologies. You excel at transforming business requirements into executable plans while maintaining quality, timeline, and budget constraints. Evidence: `.claude/agents/project-manager.md`
- **Your Core Mission** (documentation): You are a senior Tech Lead with 10+ years of experience in software architecture, system design, and technical leadership. You excel at transforming user experience requirements into robust, scalable technical solutions while mentoring development teams and ensuring architectural excellence. Evidence: `.claude/agents/tech-lead-architect.md`
- **Your Role in the Development Pipeline** (documentation): You are a senior UX Engineer with 8+ years of experience in user-centered design, specializing in creating intuitive, accessible, and engaging digital experiences. You have deep expertise in user research, interaction design, and design systems, with a strong understanding of technical implementation constraints. Evidence: `.claude/agents/ux-designer.md`
- **Five Whys Analysis** (documentation): Apply the Five Whys root cause analysis technique to investigate issues. Evidence: `.claude/commands/five.md`
- **Create Pull Request Command** (documentation): Create a new branch, commit changes, and submit a pull request. Evidence: `.claude/commands/pr.md`
- **PR Review** (documentation): Instructions : Execute each task in the order given to conduct a thorough code review. Update GitHub with this review. Important : The future is now—any improvements or “future” recommendations must be addressed immediately . Evidence: `.claude/commands/review.md`
- **High-level flow** (documentation): This outlines the development practices and principles we require you to follow. Don't start working on features until asked, this document is intended to get you into the right state of mind. Evidence: `.claude/commands/tdd.md`
- **User Experience Designer & UI Specialist Persona** (documentation): User Experience Designer & UI Specialist Persona Evidence: `.claude/commands/ux.md`
- **Slash Commands — Cheatsheet** (documentation): ← Back to README ../../README.md claude-commands Evidence: `docs/reference/commands.md`
- **Your Role in the Development Pipeline** (documentation): You are a senior Backend Engineer with 8+ years of experience in server-side development, API design, and distributed systems. You specialize in building robust, scalable, and secure backend applications that power modern web and mobile applications. Evidence: `specialized-agents/system-prompts/backend-engineer-prompt.md`
- **Your Role in the Development Pipeline** (documentation): You are a senior Code Reviewer with 12+ years of experience in software development and code quality assurance. You specialize in identifying code quality issues, performance optimization opportunities, and ensuring adherence to best practices across multiple programming languages and frameworks. Evidence: `specialized-agents/system-prompts/code-reviewer-prompt.md`
- **Your Role in the Development Pipeline** (documentation): You are a senior Database Engineer with 8+ years of experience in database design, performance optimization, and data architecture. You specialize in creating robust, scalable, and secure database solutions that serve as the foundation for high-performance applications. Evidence: `specialized-agents/system-prompts/database-engineer-prompt.md`
- **Your Role in the Development Pipeline** (documentation): You are a senior Frontend Engineer with 7+ years of experience in modern web development, specializing in creating responsive, accessible, and high-performance user interfaces. You excel at transforming design specifications into production-ready applications with excellent user experiences. Evidence: `specialized-agents/system-prompts/frontend-engineer-prompt.md`
- **Your Role in the Development Pipeline** (documentation): You are a senior Security Reviewer with 10+ years of experience in cybersecurity, application security testing, and compliance validation. You specialize in identifying security vulnerabilities, conducting threat assessments, and ensuring applications meet security standards before production deployment. Evidence: `specialized-agents/system-prompts/security-reviewer-prompt.md`
- **Your Role in the Development Pipeline** (documentation): You are a senior Tech Lead with 10+ years of experience in software architecture, system design, and technical leadership. You excel at transforming user experience requirements into robust, scalable technical solutions while mentoring development teams and ensuring architectural excellence. Evidence: `specialized-agents/system-prompts/tech-lead-prompt.md`
- **Settings** (structured_config): { "permissions": { "allow": "Bash mkdir: ", "Bash uv: ", "Bash find: ", "Bash mv: ", "Bash grep: ", "Bash npm: ", "Bash ls: ", "Bash cp: ", "Write", "Edit", "Bash chmod: ", "Bash touch: ", "mcp playwright browser take screenshot", "mcp playwright browser resize" , "deny": }, "hooks": { "PostToolUse": { "matcher": "", "hooks": { "type": "command", "command": "uv run \"$CLAUDE PROJECT DIR\"/.claude/hooks/post tool use.py" } } , "Notification": { "matcher": "", "hooks": { "type": "command", "command": "uv run \"$CLAUDE PROJECT DIR\"/.claude/hooks/notification.py --notify" } } , "Stop": { "matcher": "", "hooks": { "type": "command", "command": "uv run \"$CLAUDE PROJECT DIR\"/.claude/hooks/stop.… Evidence: `.claude/settings.json`
- **✅ LLM Unit Testing Best Practices Checklist** (documentation): ✅ LLM Unit Testing Best Practices Checklist Focused on testing internal logic, not API endpoints Evidence: `.claude/commands/test.md`
- **Claude Jumping** (source_file): .claude-body { animation: jump 0.5s ease-in-out infinite; transform-origin: center bottom; } .shadow { animation: shadow-scale 0.5s ease-in-out infinite; } .left-arm { animation: wave-left 0.5s ease-in-out infinite; transform-origin: right center; } .right-arm { animation: wave-right 0.5s ease-in-out infinite; transform-origin: left center; } .left-ear { animation: ear-bounce 0.5s ease-in-out infinite; transform-origin: center bottom; } .right-ear { animation: ear-bounce 0.5s ease-in-out infinite 0.1s; transform-origin: center bottom; } @keyframes jump { 0%, 100% { transform: translateY 0 scaleY 1 scaleX 1 ; } 30% { transform: translateY -16px scaleY 1.1 scaleX 0.95 ; } 50% { transform: tra… Evidence: `Images/claude-jumping.svg`
- **Create notification message with 30% chance to include name** (source_file): def get tts script path ⋮---- script dir = Path file .parent tts dir = script dir / "utils" / "tts" ⋮---- elevenlabs script = tts dir / "elevenlabs tts.py" ⋮---- openai script = tts dir / "openai tts.py" ⋮---- pyttsx3 script = tts dir / "pyttsx3 tts.py" ⋮---- def announce notification ⋮---- tts script = get tts script path ⋮---- engineer name = os.getenv 'ENGINEER NAME', '' .strip ⋮---- Create notification message with 30% chance to include name ⋮---- notification message = f"{engineer name}, your agent needs your input" ⋮---- notification message = "Your agent needs your input" ⋮---- Call the TTS script with the notification message ⋮---- capture output=True, Suppress output timeout=10 10-… Evidence: `.claude/hooks/notification.py`
- **Post Tool Use** (source_file): def main ⋮---- input data = json.load sys.stdin ⋮---- log dir = Path.cwd / 'logs' ⋮---- log path = log dir / 'post tool use.json' ⋮---- log data = json.load f ⋮---- log data = Evidence: `.claude/hooks/post_tool_use.py`
- **Stop** (source_file): def get completion messages ⋮---- def get tts script path ⋮---- script dir = Path file .parent tts dir = script dir / "utils" / "tts" ⋮---- elevenlabs script = tts dir / "elevenlabs tts.py" ⋮---- openai script = tts dir / "openai tts.py" ⋮---- pyttsx3 script = tts dir / "pyttsx3 tts.py" ⋮---- def get llm completion message ⋮---- llm dir = script dir / "utils" / "llm" ⋮---- oai script = llm dir / "oai.py" ⋮---- result = subprocess.run ⋮---- anth script = llm dir / "anth.py" ⋮---- messages = get completion messages ⋮---- def announce completion ⋮---- tts script = get tts script path ⋮---- completion message = get llm completion message ⋮---- def main ⋮---- parser = argparse.ArgumentParser ⋮--… Evidence: `.claude/hooks/stop.py`
- **Subagent Stop** (source_file): def get tts script path ⋮---- script dir = Path file .parent tts dir = script dir / "utils" / "tts" ⋮---- elevenlabs script = tts dir / "elevenlabs tts.py" ⋮---- openai script = tts dir / "openai tts.py" ⋮---- pyttsx3 script = tts dir / "pyttsx3 tts.py" ⋮---- def announce subagent completion ⋮---- tts script = get tts script path ⋮---- completion message = "Subagent Complete" ⋮---- def main ⋮---- parser = argparse.ArgumentParser ⋮---- args = parser.parse args ⋮---- input data = json.load sys.stdin ⋮---- session id = input data.get "session id", "" stop hook active = input data.get "stop hook active", False ⋮---- log dir = os.path.join os.getcwd , "logs" ⋮---- log path = os.path.join log dir… Evidence: `.claude/hooks/subagent_stop.py`
- **Generate and play audio directly** (source_file): def main ⋮---- api key = os.getenv 'ELEVENLABS API KEY' ⋮---- elevenlabs = ElevenLabs api key=api key ⋮---- text = " ".join sys.argv 1: ⋮---- text = "The first move is what sets everything in motion." ⋮---- Generate and play audio directly audio = elevenlabs.text to speech.convert Evidence: `.claude/hooks/utils/tts/elevenlabs_tts.py`
- **Security Policy** (documentation): This repo ships executable examples — Python hook scripts in .claude/hooks/ .claude/hooks and skills in .claude/commands/ .claude/commands that run with your shell permissions when you copy them into a project. Review them like any shell script before use the guide itself preaches the same docs/skills.md skills-faq . Evidence: `SECURITY.md`
- **Project Todo Manager** (documentation): Manage todos in a todos.md file at the root of your current project directory. Evidence: `.claude/commands/todo.md`
- **Role Overview** (documentation): The Backend Engineer serves as the server-side implementation specialist in the development pipeline, transforming technical specifications and database designs into robust, scalable, and secure server-side applications. They create the business logic layer that connects frontend user interfaces with database operations. Evidence: `specialized-agents/Descriptions/backend-engineer-description.md`
- **Role Overview** (documentation): The Business Analyst serves as the first point of contact in the development pipeline, responsible for transforming raw ideas and business needs into structured, actionable requirements. They bridge the gap between stakeholders and the technical team. Evidence: `specialized-agents/Descriptions/business-analyst-description.md`
- **Role Overview** (documentation): The Code Reviewer serves as the quality gatekeeper in the development pipeline, ensuring that all code implementations meet established standards for maintainability, performance, security, and best practices. They provide the final technical validation before code progresses to security review and production deployment. Evidence: `specialized-agents/Descriptions/code-reviewer-description.md`
- **Role Overview** (documentation): The Database Engineer serves as the data foundation specialist in the development pipeline, transforming technical architecture specifications into optimized, secure, and scalable database solutions. They ensure data integrity, performance, and accessibility for both Frontend and Backend Engineers. Evidence: `specialized-agents/Descriptions/database-engineer-description.md`
- **Core Responsibilities** (documentation): The Frontend Engineer serves as the user-facing implementation specialist in the development pipeline, transforming UX designs and technical specifications into responsive, accessible, and performant user interfaces. They bridge the gap between design vision and interactive user experiences. Evidence: `specialized-agents/Descriptions/frontend-engineer-description.md`
- **Role Overview** (documentation): The Project Manager serves as the central orchestrator in the development pipeline, taking validated business requirements and transforming them into executable project plans. They coordinate between all specialists to ensure timely, quality delivery within scope and budget. Evidence: `specialized-agents/Descriptions/project-manager-description.md`
- **Core Responsibilities** (documentation): The Security Reviewer serves as the final security gatekeeper in the development pipeline, conducting comprehensive security assessments of the complete application to identify vulnerabilities, ensure compliance with security standards, and validate that security best practices are properly implemented throughout the system. Evidence: `specialized-agents/Descriptions/security-reviewer-description.md`
- **Role Overview** (documentation): The Tech Lead serves as the technical decision-maker and architecture authority in the development pipeline, transforming user experience designs into robust, scalable technical solutions. They bridge the gap between design vision and implementation reality while ensuring technical excellence and maintainability. Evidence: `specialized-agents/Descriptions/tech-lead-description.md`
- **Role Overview** (documentation): The UX Engineer serves as the user advocate in the development pipeline, transforming business requirements and project plans into intuitive, accessible, and engaging user experiences. They bridge the gap between user needs and technical implementation through research-driven design. Evidence: `specialized-agents/Descriptions/ux-engineer-description.md`
- **Your Role in the Development Pipeline** (documentation): You are an expert Business Analyst with 10+ years of experience in requirements gathering, process analysis, and stakeholder management. You specialize in transforming business ideas into structured, actionable requirements that drive successful project outcomes. Evidence: `specialized-agents/system-prompts/business-analyst-prompt.md`
- **Phase 0: Preparation** (documentation): You are an elite design review specialist with deep expertise in user experience, visual design, accessibility, and front-end implementation. You conduct world-class design reviews following the rigorous standards of top Silicon Valley companies like Stripe, Airbnb, and Linear. Evidence: `specialized-agents/system-prompts/design-reviewer.md`
- **Your Role in the Development Pipeline** (documentation): You are a senior Project Manager with 12+ years of experience leading complex software development projects across various industries. You excel at turning business requirements into executable plans and orchestrating cross-functional teams to deliver high-quality solutions on time and within budget. Evidence: `specialized-agents/system-prompts/project-manager-prompt.md`
- **Your Role in the Development Pipeline** (documentation): You are a senior UX Engineer with 8+ years of experience in user-centered design, specializing in creating intuitive, accessible, and engaging digital experiences. You have deep expertise in user research, interaction design, and design systems, with a strong understanding of technical implementation constraints. Evidence: `specialized-agents/system-prompts/ux-engineer-prompt.md`
- **macOS system files** (source_file): macOS system files .DS Store .AppleDouble .LSOverride . Evidence: `.gitignore`
- **Agent Orchestration Workflow** (source_file): { "nodes": {"id":"ea2858a751c8b7b8","type":"text","text":"\n! icon-2.png \n! Project Manager Prompt \n\n! Project Manager Description ","x":-613,"y":-2,"width":540,"height":1102,"color":" bfa1a1"}, {"id":"1f89aba261b33ca9","type":"text","text":"! Icon-5.png \n\n! Business Analyst Prompt \n\n! Business Analyst Descrtiption ","x":-1200,"y":-2,"width":540,"height":1102,"color":"6"}, {"id":"a81c0548ef356102","type":"text","text":"! Icon-3.png \n\n! UX Engineer Prompt \n\n! UX Engineer Description ","x":0,"y":-2,"width":540,"height":1102,"color":" e5f0ad"}, {"id":"31bb318a93500944","type":"text","text":"! Icon-6.png \n\n! Database Engineer Prompt \n\n! Database Engineer Description ","x":600,"y"… Evidence: `specialized-agents/agent-orchestration-workflow.canvas`

## 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: `README.md`, `mcp-servers/README.md`, `CONTRIBUTING.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: `README.md`, `mcp-servers/README.md`, `CONTRIBUTING.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 and Claude Code Setup**: importance `high`
  - source_paths: README.md, CONTRIBUTING.md, Images/claude-jumping.svg
- **Skills and Slash Commands**: importance `high`
  - source_paths: .claude/commands/pr.md, .claude/commands/review.md, .claude/commands/tdd.md, .claude/commands/test.md, .claude/commands/five.md
- **Hooks System and Lifecycle Events**: importance `high`
  - source_paths: .claude/hooks/pre_tool_use.py, .claude/hooks/post_tool_use.py, .claude/hooks/notification.py, .claude/hooks/stop.py, .claude/hooks/subagent_stop.py
- **Subagents and Agent Teams**: importance `high`
  - source_paths: .claude/agents/coder-reviewer.md, .claude/agents/frontend-engineer.md, .claude/agents/project-manager.md, .claude/agents/tech-lead-architect.md, .claude/agents/ux-designer.md
- **Specialized Agent Library**: importance `medium`
  - source_paths: specialized-agents/system-prompts/backend-engineer-prompt.md, specialized-agents/system-prompts/frontend-engineer-prompt.md, specialized-agents/system-prompts/database-engineer-prompt.md, specialized-agents/system-prompts/tech-lead-prompt.md, specialized-agents/system-prompts/code-reviewer-prompt.md
- **MCP Servers and External Integrations**: importance `medium`
  - source_paths: mcp-servers/README.md, mcp-servers/memory.md, mcp-servers/playwright.md, mcp-servers/sequential-thinking.md, mcp-servers/serena.md
- **Configuration, Models, and Reference**: importance `medium`
  - source_paths: .claude/settings.json, docs/reference/models.md, docs/reference/effort-levels.md, docs/reference/faq.md, docs/reference/further-reading.md

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `1149eaa1ee5499c7fd7295da662f9073fd059568`
- inspected_files: `README.md`, `docs/reference/changelog.md`, `docs/reference/commands.md`, `docs/reference/effort-levels.md`, `docs/reference/faq.md`, `docs/reference/further-reading.md`, `docs/reference/models.md`, `docs/skills.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: Capability evidence risk requires verification

- Trigger: README/documentation is current enough for a first validation pass.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: capability.assumptions | https://github.com/wesammustafa/Claude-Code-Everything-You-Need-to-Know
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: downstream_validation.risk_items | https://github.com/wesammustafa/Claude-Code-Everything-You-Need-to-Know
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: risks.scoring_risks | https://github.com/wesammustafa/Claude-Code-Everything-You-Need-to-Know
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Maintenance risk requires verification

- Trigger: issue_or_pr_quality=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/wesammustafa/Claude-Code-Everything-You-Need-to-Know
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Maintenance risk requires verification

- Trigger: release_recency=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/wesammustafa/Claude-Code-Everything-You-Need-to-Know
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.