docs: add clarity around naming and target audience

[whitep4nth3r]

No description provided.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Feb 3, 2026 6:20pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Feb 3, 2026 6:20pm
npmx-lunaria	Ignored		Feb 3, 2026 6:20pm

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates documentation in CONTRIBUTING.md and README.md. CONTRIBUTING.md replaces the previous goals with a concrete goal for npmx.dev, adds a Core values section (Speed, Simplicity, Community‑first), reorganises the Table of Contents, and adds a naming guideline requiring the project name to appear lowercase as "npmx" in the UI alongside existing code‑style/pre‑commit guidance. README.md changes the registry link text from "npmjs.com" to "npm" (same URL) and renames the "Compatibility" bullet to "URL Compatibility" while preserving the URL‑replacement behaviour.

🚥 Pre-merge checks | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The pull request has no description provided by the author, making it impossible to verify that the changeset intent is adequately communicated.	Add a pull request description that explains the naming clarity improvements, the rationale for changes to CONTRIBUTING.md and README.md, and how these changes benefit the project.

_{✏️ 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

---

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

[coderabbitai]

Actionable comments posted: 1

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[graphieros]

Clarity, elegance and style.

[serhalp]

LGTM

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

CONTRIBUTING.md (1)

28-33: ⚠️ Potential issue | 🟡 Minor

Add the new "npmx name" subsection to the table of contents.

The new "npmx name" subsection (lines 153-156) is missing from the TOC. All other subsections under "Code style" are listed, so this should be included for consistency and discoverability.

📝 Proposed fix to add the missing TOC entry

 - [Code style](`#code-style`)
+  - [npmx name](`#npmx-name`)
   - [TypeScript](`#typescript`)
   - [Server API patterns](`#server-api-patterns`)

🧹 Nitpick comments (1)

CONTRIBUTING.md (1)

153-156: Consider simplifying the phrasing for clarity.

The guidance is clear, but the phrasing on line 155 could be slightly more natural.

✏️ Suggested phrasing improvement

 ### npmx name
 
-When adding the name of the project to anywhere in the UI, use `npmx` in all lowercase letters.
+When displaying the project name anywhere in the UI, use `npmx` in all lowercase letters.

[coderabbitai]

Actionable comments posted: 1

[coderabbitai]

Actionable comments posted: 1

[serhalp]

💯