# Instead of running prettier against every file extension it supports, we
# explicitly list the file extensions we want to format (same approach as
# affinity/affinity and affinity/affinity-claude-plugins).
*.*
!*.md
!*.json
!*.yml
!*.yaml

# Prettier skips dot-directories by default; re-include the ones whose Markdown
# and config we do want formatted (skill docs, issue templates, workflows).
!.github
!.claude

# The MCP Apps frontend has its own ESLint/TypeScript toolchain, generated
# bundles, and pnpm lockfile. Prettier must not touch it.
src/affinity_mcp/apps/

# Eval scenario fixtures: these YAML cases (and the planted-regression markdown
# fixture beside them) are hand-authored with pinned seed values and a fixed
# structure the create-eval-scenario skill depends on. Prettier must not
# restyle them.
tests/mcp_eval/cases/
