Skip to main content
Agent skill

Dating Web

A consumer-feeling dating / matchmaking dashboard — left rail navigation, ticker bar of community signals, headline KPIs, a 30-day mutual-matches bar chart, and a match-rate trend block. Editorial typography, restrained accent. Use when the brief asks for a "dating site", "matchmaking", "community dashboard", "social network dashboard", or any consumer product where the data is the story.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Dating Web when an AI agent needs a reusable SKILL.md workflow for this job: A consumer-feeling dating / matchmaking dashboard — left rail navigation, ticker bar of community signals, headline KPIs, a 30-day mutual-matches bar chart, and a match-rate trend block. Editorial typography, restrained accent. Use when the brief asks for a "dating site", "matchmaking", "community dashboard", "social network dashboard", or any consumer product where the data is the story.

When not to use it

Skip Dating Web when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/dating-web
# Save SKILL.md to ~/.claude/skills/dating-web/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/dating-web/SKILL.md. For a shared project, commit the folder at .claude/skills/dating-web/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Dating Web skill for this task: Read the active DESIGN.md (injected above). Lean into a serif display. Confirm any required inputs or files before making changes.

What supports this recommendation?

74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
82/100
Practical detail
74/100
Source evidence
63/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Dating Web Skill

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.

Intended uses

  • Read the active DESIGN.md (injected above). Lean into a serif display
  • Pick a brand voice — wry, observational, slightly literary. Generate
  • Layout, in order:
  • Top ticker — single-row horizontal strip across the top in a
  • Left rail — 220–260px sidebar. Brand wordmark in serif italic at
  • Main content:
  • KPI grid — 3 columns × 3 rows (or 9 cells). Each cell: small
  • Bar chart panel — "mutuals — last 30 days". Tall thin black
  • Trend panel — "match rate — last 12 weeks". One line of body
  • 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.
  • Self-check:
  • Reads as restrained, editorial, slightly funny — not horny.
  • Single accent token used in 3–4 places max (one KPI, two highlight
  • No swipe deck, no hearts, no fire emoji.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.