Dating Web Skill

SkillMedia

dating-web is a skill that guides an AI agent to build a single-page dating site dashboard in HTML. It produces a consumer-feeling screen with left-rail navigation, a ticker bar, headline KPIs, a 30-day mutual-matches bar chart, and a match-rate trend panel, styled with editorial typography and a restrained accent.

Available today. Use it from your connected AI after setup.

Have an agent environment that supports loading skills.

Then ask your AI: use the Dating Web Skill skill

What your AI can do with it

  • Generates a single-screen HTML dating or matchmaking dashboard
  • Builds a left-rail navigation with user card and grouped nav sections
  • Adds a top ticker bar with tagline and next-tier signal
  • Lays out a 3x3 KPI grid with oversized serif numerals and footnotes
  • Renders a 30-day mutual-matches bar chart with a mono caption
  • Includes a 12-week match-rate trend panel with supporting copy

Getting started

  1. Have an agent environment that supports loading skills.
  2. Add the dating-web skill to the agent's available skills.
  3. Ensure a DESIGN.md with color, typography, layout, and components sections is available, since the skill requires a design system.
  4. Ask the agent for a dating or matchmaking dashboard, optionally using the example prompt about a daily digest dashboard with stats and a community ticker.
  5. Preview the generated index.html in a desktop browser.

What this skill tells your AI

The instructions your AI receives, as published by nexu-io/open-design in design-templates/dating-web/SKILL.md and read by ahel’s review.

Produce a single-screen consumer dashboard that feels like a Sunday-paper dating column rendered as software. Editorial type, single restrained accent, lots of negative space, no swipe deck or hookup tropes.

Workflow

  1. Read the active DESIGN.md (injected above). Lean into a serif display token for the metric numerals — these screens live or die on numerals.
  2. Pick a brand voice — wry, observational, slightly literary. Generate real, specific copy. Examples: "the people who'd text back within a day", "manageable. two are now friends.", "your single greatest compatibility asset."
  3. Layout, in order:
    • Top ticker — single-row horizontal strip across the top in a sans-serif eyebrow style: tagline left, "NEXT TIER AT 2,080 MUTUALS" right, both in mono caps with letter-spacing. Thin rule below.
    • Left rail — 220–260px sidebar. Brand wordmark in serif italic at top. User card (avatar / handle / ratio / tier). Three groups of nav: "TODAY" (specimen, inbox, queue, notifications), "YOU" (your stats, mutuals & communities, blocked, settings), "ARCHIVE" (past issues, expired matches). Active item gets accent text + accent dot.
    • Main content:
      • KPI grid — 3 columns × 3 rows (or 9 cells). Each cell: small caps mono label, an oversized serif numeral (use accent or muted green for positive, muted red for caution), one-line italic footnote. Plausible specifics — "1,842 ↑ 41 this wk · healthy growth.", "14% above median for your cohort.", "4 / exes in your circle · manageable. two are now friends."
      • Bar chart panel — "mutuals — last 30 days". Tall thin black bars, last two days highlighted in accent. Caption above with "↑ TRENDING UP · +3 CLOSE MUTUALS THIS MONTH · TWO VIA THE SAME OFFSITE" in mono.
      • Trend panel — "match rate — last 12 weeks". One line of body copy below ("STEADY CLIMB FROM 8% → 14%. ATTRIBUTABLE TO ONE COMMUNITY JOIN…"). Footer rule.
  4. Write a single HTML document:
    • <!doctype html> through </html>, CSS inline.
    • Background creamy off-white, body serif, mono labels everywhere.
    • Use font-feature-settings: 'tnum' on the metric numerals.
    • SVG bar chart with ~30 bars, varied heights.
    • data-od-id on ticker, sidebar, kpi grid, chart, trend.
  5. Self-check:
    • Reads as restrained, editorial, slightly funny — not horny.
    • Single accent token used in 3–4 places max (one KPI, two highlight bars, one nav active state).
    • No swipe deck, no hearts, no fire emoji.

Output contract

Emit between <artifact> tags:

<artifact identifier="dating-slug" type="text/html" title="Dating Dashboard — Title">
<!doctype html>
<html>...</html>
</artifact>

One sentence before the artifact, nothing after.

Signals

GitHub stars
98k
Forks
11k
Last commit
Sep 2026

Others that do the same job

Questions

When should this skill be used?
When the brief asks for a dating site, matchmaking, community dashboard, social network dashboard, or any consumer product where the data is the story.
What does the output look like?
A single-screen consumer dashboard with editorial type, one restrained accent, lots of negative space, and no swipe-deck or hookup tropes.
Does it need a design system?
Yes. The skill requires an active DESIGN.md covering color, typography, layout, and components, and leans on a serif display token for metric numerals.
Advanced
Item type
skill
Key
dating-web-2
Source
github.com/nexu-io/open-design