Replicate — Explore

Browse & DiscoverySee it livereplicate.com

Two unrelated feeds run side by side, each owning its own tab strip, and the active tab in both is drawn as a bordered box with no bottom edge — so it visually fuses into the panel it controls instead of sitting above it.

Replicate — Explore — captured interface — Page excerpt · scroll inside to explore

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

Search & discovery Navigation

Why this pattern works

The open-bottomed active tab: a 1px-bordered box around the tab label with the border removed on the bottom edge, so the tab and the content panel below it read as one continuous shape, like a folder tab. Steal this for any module where the active-state indicator should feel structurally attached to its content rather than just a color change. Also take the twin-panel layout — two independently-tabbed regions side by side (Latest/Blog Posts on the left, Popular Models on the right) — so one page can serve two unrelated content types without a shared filter bar trying to do both jobs.

Design notes

Surface: Replicate /explore page, logged out, default view
Navigation: No global nav visible in this crop — the page opens directly on a bold 'Explore' heading with heavy top whitespace, then splits into two independent content panels, each with its own local tab strip and no shared top-level tabs.
Layout: Two-column layout below the heading: a wider left panel (~775px) and a narrower right panel (~500px) with a gutter between them. Each panel scrolls its own content vertically; there's no fixed sidebar in the crop.
Density: Comfortable list rows (~90-100px) with generous line-height on descriptions; thumbnails are small and secondary (~90px square or a ~320px banner) so each row reads primarily as text, with the image as an anchor rather than the focus.
Color: White canvas, near-black headings, mid-grey body text. One accent — a red-orange (~#f15f31) — is reserved entirely for run counts, 'Get started'/'View more' links, and the tab icons. Nothing else on the page uses color.
Type: The page heading is bold at ~40px; tab labels are small (~13px), uppercase, bold, letter-spaced so they read as section labels rather than buttons; model and post titles are ~16-24px bold; run counts are bold and colored — the only colored numerals on the page.
Pattern: The fused tab-to-panel border: the active tab is drawn with a top and side border but no bottom border, sitting flush against a full-width rule that continues from where its missing edge would be — so the tab reads as a flap opening directly into its content.
States: No loading or empty state visible — both panels are fully populated on load. Officially-verified model rows carry a small checkmark 'Official' badge next to the run count, a trust signal shown inline rather than as a separate filter.
Don't: Don't give both panels a shared tab row at the top of the page — the whole value is that Latest/Blog Posts and Popular Models are unrelated feeds with independent state, and merging their tabs into one strip would force them to share a selection they don't share content for.

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: Replicate — Explore
Source: https://replicate.com/explore
Swipefile reference: https://swipefile.design/ref/replicate-explore/
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: Replicate /explore page, logged out, default view
- nav: No global nav visible in this crop — the page opens directly on a bold 'Explore' heading with heavy top whitespace, then splits into two independent content panels, each with its own local tab strip and no shared top-level tabs.
- layout: Two-column layout below the heading: a wider left panel (~775px) and a narrower right panel (~500px) with a gutter between them. Each panel scrolls its own content vertically; there's no fixed sidebar in the crop.
- density: Comfortable list rows (~90-100px) with generous line-height on descriptions; thumbnails are small and secondary (~90px square or a ~320px banner) so each row reads primarily as text, with the image as an anchor rather than the focus.
- color: White canvas, near-black headings, mid-grey body text. One accent — a red-orange (~#f15f31) — is reserved entirely for run counts, 'Get started'/'View more' links, and the tab icons. Nothing else on the page uses color.
- typography: The page heading is bold at ~40px; tab labels are small (~13px), uppercase, bold, letter-spaced so they read as section labels rather than buttons; model and post titles are ~16-24px bold; run counts are bold and colored — the only colored numerals on the page.
- pattern: The fused tab-to-panel border: the active tab is drawn with a top and side border but no bottom border, sitting flush against a full-width rule that continues from where its missing edge would be — so the tab reads as a flap opening directly into its content.
- states: No loading or empty state visible — both panels are fully populated on load. Officially-verified model rows carry a small checkmark 'Official' badge next to the run count, a trust signal shown inline rather than as a separate filter.
- dont: Don't give both panels a shared tab row at the top of the page — the whole value is that Latest/Blog Posts and Popular Models are unrelated feeds with independent state, and merging their tabs into one strip would force them to share a selection they don't share content for.

Useful for: The open-bottomed active tab: a 1px-bordered box around the tab label with the border removed on the bottom edge, so the tab and the content panel below it read as one continuous shape, like a folder tab. Steal this for any module where the active-state indicator should feel structurally attached to its content rather than just a color change. Also take the twin-panel layout — two independently-tabbed regions side by side (Latest/Blog Posts on the left, Popular Models on the right) — so one page can serve two unrelated content types without a shared filter bar trying to do both jobs.

## 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.

Replicate — Explore

Make it your own

Keep exploring