npm — Package page

Dev ToolsSee it livenpmjs.com

The whole right column is one idea done five times: a label, a value, sometimes a tiny inline chart, separated by hairlines — no cards, no icons doing heavy lifting, just a repeatable meta-fact module reused for install command, repo link, homepage, downloads and version/license.

npm — Package page — captured interface — Page excerpt · scroll inside to explore

Source capture · 2026-08-01Open full image ↗

Why this pattern works

Steal the meta-rail as a reusable primitive: stack single-fact modules (Install / Repository / Homepage / Weekly Downloads / Version+License) in a fixed-width sidebar, each separated only by a hairline, and let one of them carry an inline sparkline instead of a separate chart panel. Also take the color-coded tab strip: every secondary tab (Code, Dependencies, Dependents, Versions) gets its own accent color on its icon, and the tab underline is stitched together from those same colors, so the tab bar reads as a legend before you click anything.

Design notes

Surface: Package detail page for react on npmjs.com, Readme tab active
Navigation: Two stacked bars above the content: a slim secondary nav (Pro, Teams, Pricing, Documentation) and a primary nav (wordmark, a search-input-plus-button combo, `Sign Up` / `Sign In`). No breadcrumb — the package name itself is the only wayfinding once you're on the page.
Layout: Two columns under a full-width header: a wide left reading column (~65%) for rendered Markdown, a narrower fixed right rail (~30%) for metadata, split by a hairline. A dismissible banner and a thin gradient stripe sit above everything.
Density: Loose. Readme content runs at normal prose line-height; the sidebar gives each fact its own paragraph of whitespace instead of compressing into a stat grid.
Color: White page, near-black text. The loudest element is the banner's rainbow gradient stripe. Each secondary tab carries its own small accent colour on its icon (red, purple, blue, teal) that also tints its segment of the tab-strip underline. A green checkmark marks the current version; a red-orange inline link calls out `production build` inside the prose.
Type: The package name renders in a bold slab/monospace-flavoured display face, visually distinct from the humanist sans used everywhere else in the chrome. Readme headings are bold sans; code spans and the code block switch to monospace with syntax colour. Sidebar labels are small grey caps-adjacent text over larger plain values.
Pattern: The meta-rail as a stack of single-fact modules — Install, Repository, Homepage, Weekly Downloads, Version/License — each just a label and a value, with one of them (Downloads) carrying an inline sparkline instead of a separate chart card.
States: No empty or error states visible — a fully populated, high-traffic package page. The dismissible top banner is the only temporary element, with its own close affordance separate from the rest of the page.
Don't: Don't give every sidebar fact its own bordered card. The moment Install, Repository, Homepage and Downloads each get a box, the rail stops reading as one continuous spec sheet and starts looking like an unfinished dashboard — hairline-only separation is what makes it feel authored.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: npm — Package page
Source: https://www.npmjs.com/package/react
Swipefile reference: https://swipefile.design/ref/npm-package/
Captured: 2026-08-01. This is a dated reference, not a claim about the current live product.
Capture scope: a page excerpt. Do not infer unseen sections or interactions.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Package detail page for react on npmjs.com, Readme tab active
- nav: Two stacked bars above the content: a slim secondary nav (Pro, Teams, Pricing, Documentation) and a primary nav (wordmark, a search-input-plus-button combo, `Sign Up` / `Sign In`). No breadcrumb — the package name itself is the only wayfinding once you're on the page.
- layout: Two columns under a full-width header: a wide left reading column (~65%) for rendered Markdown, a narrower fixed right rail (~30%) for metadata, split by a hairline. A dismissible banner and a thin gradient stripe sit above everything.
- density: Loose. Readme content runs at normal prose line-height; the sidebar gives each fact its own paragraph of whitespace instead of compressing into a stat grid.
- color: White page, near-black text. The loudest element is the banner's rainbow gradient stripe. Each secondary tab carries its own small accent colour on its icon (red, purple, blue, teal) that also tints its segment of the tab-strip underline. A green checkmark marks the current version; a red-orange inline link calls out `production build` inside the prose.
- typography: The package name renders in a bold slab/monospace-flavoured display face, visually distinct from the humanist sans used everywhere else in the chrome. Readme headings are bold sans; code spans and the code block switch to monospace with syntax colour. Sidebar labels are small grey caps-adjacent text over larger plain values.
- pattern: The meta-rail as a stack of single-fact modules — Install, Repository, Homepage, Weekly Downloads, Version/License — each just a label and a value, with one of them (Downloads) carrying an inline sparkline instead of a separate chart card.
- states: No empty or error states visible — a fully populated, high-traffic package page. The dismissible top banner is the only temporary element, with its own close affordance separate from the rest of the page.
- dont: Don't give every sidebar fact its own bordered card. The moment Install, Repository, Homepage and Downloads each get a box, the rail stops reading as one continuous spec sheet and starts looking like an unfinished dashboard — hairline-only separation is what makes it feel authored.

Useful for: Steal the meta-rail as a reusable primitive: stack single-fact modules (Install / Repository / Homepage / Weekly Downloads / Version+License) in a fixed-width sidebar, each separated only by a hairline, and let one of them carry an inline sparkline instead of a separate chart panel. Also take the color-coded tab strip: every secondary tab (Code, Dependencies, Dependents, Versions) gets its own accent color on its icon, and the tab underline is stitched together from those same colors, so the tab bar reads as a legend before you click anything.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

npm — Package page

Make it your own

Keep exploring