[alidotforrest]

Description

Coding agents working in this repo do not currently have a durable pointer to the MetaMask content guidelines, so user-facing copy can be written without those rules. This adds a short section to AGENTS.md telling agents to read and follow .claude/skills/mms-content-guidelines/SKILL.md before writing or changing user-facing strings, to run yarn skills if that file is missing, to edit English source strings in locales/languages/en.json rather than the generated skill copy, and to change rules in MetaMask/skills rather than in this repo.

The guidelines live in MetaMask/skills at domains/ui/skills/content-guidelines/ and sync into this repo as the generated mms-content-guidelines skill. That skill is the agent-readable implementation of the MetaMask Content Design Style Guide. The section also tells agents to flag any conflict between the skill and the Style Guide to the content owner rather than invent a rule. The updated guidelines are in MetaMask/skills#221, which is not merged yet. This pointer becomes useful once that PR merges and yarn skills runs. No app strings or code change in this PR.

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Refs: MetaMask/skills#221

Manual testing steps

N/A — agent documentation only; no app behavior to exercise.

Screenshots/Recordings

Before

N/A

After

N/A

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

  

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud