Document linting, formatting, and image-caching conventions

Reflect the ESLint/Prettier quality gates, expo-image usage, and
dynamic-type capping in the contributor and agent guides.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: jnrahme

CONTRIBUTING.md

@@ -24,12 +24,15 @@ npm run web
 Before opening a pull request or pushing a material change, run:
 
 ```bash
+npm run format
 make verify
 make expo-check
 ```
 
-`make verify` runs strict TypeScript and Jest. `make expo-check` verifies that
-installed package versions match Expo SDK 56 expectations.
+`make verify` runs strict TypeScript, ESLint, and the Jest suite with coverage
+gates. `npm run format` applies Prettier (CI enforces formatting via
+`npm run format:check`). `make expo-check` verifies that installed package
+versions match Expo SDK 56 expectations.
 
 ## Engineering Principles
 
@@ -39,6 +42,10 @@ installed package versions match Expo SDK 56 expectations.
 - Prefer accessible React Native primitives with clear labels and 44pt+ touch
   targets.
 - Use the existing theme tokens rather than hardcoded per-screen colors.
+- Load remote images through `CachedImageBackground` (expo-image) so artwork is
+  cached and shows a placeholder instead of a blank frame.
+- Cap font scaling on large display text with `typography.displayMaxScale`, and
+  leave body text free to scale for accessibility.
 - Add tests when behavior changes or a contract becomes easier to regress.
 
 ## Pull Request Checklist

docs/REPO_PROFILE.md

@@ -30,6 +30,9 @@ https://jnrahme.github.io/GameTimeTest/
 - zod
 - react-navigation
 - tanstack-query
+- expo-image
+- eslint
+- prettier
 
 ## Public Surface Checklist