chore: add guidance for screenshots in front end pull requests

[whitep4nth3r]

Also improved wording of using lowercase in pull request descriptions.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ready	Preview, Comment	Feb 10, 2026 10:17am
npmx.dev	Ready	Preview, Comment	Feb 10, 2026 10:17am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
npmx-lunaria	Ignored		Feb 10, 2026 10:17am

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes update the CONTRIBUTING.md file with additional guidance for pull request submissions. The modifications introduce a requirement for frontend-related changes to include before/after screenshots in their pull request descriptions. Additionally, the documentation now emphasises the use of lowercase letters when formatting pull request titles. Minor formatting adjustments have been made to reinforce these guidelines.

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description is directly related to the changeset, mentioning improvements to lowercase wording in PR descriptions.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

CONTRIBUTING.md (1)

792-796: Clarify scope and format for screenshots.

Consider adding a brief note on when screenshots are not needed (e.g., non-visual frontend changes) and a suggested format/location for before/after images to reduce ambiguity.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}