# prettier - Doramagic AI Context Pack > Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated. ## Project - canonical_name: `prettier/prettier` - capability: Prettier is an opinionated code formatter. - expected_user_outcome: Prettier is an opinionated code formatter. ## Operating Boundaries - Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it. - Project facts must come from repo evidence, Claim Graph, or explicit source references. - When a capability is not verified, mark it as unverified instead of completing it as fact. - publish_status: `publishable` - blocking_gaps: none --- ## 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 & Internal Architecture**: importance `high` - source_paths: README.md, src/main/core.js, src/main/ast-to-doc.js, src/main/parse.js, src/document/index.js - **Language Support & Plugin Architecture**: importance `high` - source_paths: src/language-js/index.js, src/language-css/index.js, src/language-html/index.js, src/language-markdown/index.js, src/language-yaml/index.js - **Configuration Philosophy & Options**: importance `high` - source_paths: docs/options.md, docs/configuration.md, docs/option-philosophy.md, docs/ignore.md, src/main/core-options.evaluate.js - **CLI, Programmatic API & Tooling Integrations**: importance `high` - source_paths: bin/prettier.cjs, bin/prettier.js, src/cli/index.js, src/cli/format.js, src/cli/expand-patterns.js ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `7796e9aa798f4e094e3576d08bdc2ae93ce2112b` - inspected_files: `README.md`, `package.json`, `docs/vim.md`, `docs/api.md`, `docs/comparison.md`, `docs/browser.md`, `docs/cli.md`, `docs/ignore.md`, `docs/rationale.md`, `docs/sharing-configurations.md`, `docs/install.md`, `docs/watching-files.md`, `docs/precommit.md`, `docs/editors.md`, `docs/integrating-with-linters.md`, `docs/why-prettier.md`, `docs/index.md`, `docs/related-projects.md`, `docs/configuration.md`, `docs/technical-details.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: Maintenance risk requires verification - Trigger: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow. - 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: community_evidence:github | https://github.com/prettier/prettier/issues/19339 - 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: Dependency Dashboard - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Dependency Dashboard. Context: Observed when using node - Why it matters: Developers may fail before the first successful local run: Dependency Dashboard - Evidence: failure_mode_cluster:github_issue | https://github.com/prettier/prettier/issues/15461 - 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: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - 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: community_evidence:github | https://github.com/prettier/prettier/issues/15461 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - 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: community_evidence:github | https://github.com/prettier/prettier/issues/19332 - 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: Disable New line at then end of file - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Disable New line at then end of file. Context: Source discussion did not expose a precise runtime context. - Why it matters: Developers may misconfigure credentials, environment, or host setup: Disable New line at then end of file - Evidence: failure_mode_cluster:github_issue | https://github.com/prettier/prettier/issues/6360 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: 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 | github_repo:75104123 | https://github.com/prettier/prettier - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Maintenance risk requires verification - Trigger: Developers should check this migration risk before relying on the project: 3.8.4 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: 3.8.4. Context: Source discussion did not expose a precise runtime context. - Why it matters: Upgrade or migration may change expected behavior: 3.8.4 - Evidence: failure_mode_cluster:github_release | https://github.com/prettier/prettier/releases/tag/3.8.4 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Maintenance risk requires verification - Trigger: Developers should check this migration risk before relying on the project: Release v3.9 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Release v3.9. Context: Observed when using node - Why it matters: Developers may hit a documented source-backed failure mode: Release v3.9 - Evidence: failure_mode_cluster:github_issue | https://github.com/prettier/prettier/issues/19332 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: Maintenance risk requires verification - Trigger: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow. - 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 | github_repo:75104123 | https://github.com/prettier/prettier - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: 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 | github_repo:75104123 | https://github.com/prettier/prettier - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.