rzen
7e1b200bea
UI / dev tooling - /find/ index: sort by file birthtime desc (sub-day chronology even when many finds share the same frontmatter date); render the captured-at on its own line under the host (~0.65rem mono muted) - New dev-only filter at the top of /find/: All / Not in lists, persisted in localStorage; "not in lists" hides finds referenced by any superpost - New editorial-tags chip strip on each find card (dev-only): selected tags visible by default, full picker on hover/focus-within with a "…" button for arbitrary tag entry; clicks copy /edit-find-tag <slug> <tag> to the clipboard via the existing EditConfirm singleton - New optional editorialTags: string[] field on the find collection - New src/data/editorial-tags.json — master list of available tags (initial set: ["delete"]); display order follows file order /grid/ now uses the JS Masonry component instead of CSS column-count, so the middle column no longer "dips"; tile hover updated to match the home page's accent-glow / no-translate style Content - New review: apex-markdown-processor (graduated from find of same slug; hero reused from the find folder) - New review: sindre-sorhus-older-mac-apps (graduated; intentionally hero-less per the source page's text-only design) - New review: superkey (added by user; hero wired in src/lib/hero.ts) - 24 new finds captured by /daily-finds across travel, jokes, quotes, product picks, and indie tools - 2 new finds superposts: 2026-05-04-a-small-atlas, 2026-05-04-off-until-needed Misc - daily-finds.log.md and candidate-sources.md updated with the day's runs - build-finds skill prompt iterated by user
125 lines
5.9 KiB
Markdown
125 lines
5.9 KiB
Markdown
---
|
||
name: build-finds
|
||
description: Draft a 'finds' superpost (editorial roundup) for unique.rzen.dev. Selects find items from src/content/find/, groups them under a theme, and writes a new file at src/content/finds/. Use when the user runs /build-finds, asks to "draft today's finds post", "build a roundup", or "make a catch".
|
||
disable-model-invocation: true
|
||
---
|
||
|
||
# build-finds
|
||
|
||
Author one editorial superpost (collection: `finds`) that references existing find items. Each superpost has a theme, a short blurb, and an `items` array listing find slugs. The grid layout is rendered by the page template — this skill only writes the MDX.
|
||
|
||
Invoke from inside the `unique.rzen.dev` repo.
|
||
|
||
## Inputs
|
||
|
||
- `src/content/find/*.mdx` — the available pool of finds.
|
||
- `src/content/finds/*.mdx` — existing superposts (used to detect already-referenced finds).
|
||
- Optional argument: a theme phrase (e.g. "single-virtue tools", "things-disguised-as-other-things").
|
||
- Optional argument: an explicit list of find slugs the user wants in the post.
|
||
|
||
## Procedure
|
||
|
||
### 1. Determine candidate pool
|
||
|
||
- **If the user provided explicit slugs (seed mode)** — usually the case when the user clicks the "Make a finds collection" button on `/find/`. Treat the slugs as a *seed*, not a final list.
|
||
1. Read each seed find's frontmatter (`tags`, `topics`, `subtitle`, `description`) and body.
|
||
2. Infer the through-line — the smallest phrase that captures what these finds have in common (a virtue, a use, a feeling, a structural pattern). Lean specific. Good: *"single-virtue tools"*, *"things that pour clean"*, *"objects that exist for no reason except someone wanted them to"*, *"vintage-leaning everyday carry"*. Bad: *"useful things"*, *"cool stuff"*.
|
||
3. Compute the **unreferenced pool**: every find that does NOT appear in the `items[]` array of any existing `src/content/finds/*.mdx` superpost. The seed slugs may or may not be in this pool — they're the seed regardless.
|
||
4. From the unreferenced pool, find every entry that fits the inferred theme. Use frontmatter signals (tags, topics, subtitle) and body content. Don't reach: three weakly-fitting items is worse than zero. If a candidate's fit feels strained, drop it.
|
||
5. Combine `seed + qualifying unreferenced matches`, deduped. Cap at **8 total** (per sizing notes below). If the combined list exceeds 8, drop the weakest fits — never drop a seed slug; if the seed itself is more than 8, ask the user which to drop.
|
||
6. Produce one cluster (theme phrase + final items list). Continue to step 2 to confirm before writing.
|
||
|
||
- **If the user provided a theme phrase only:** scan all finds, surface the 8–12 that best fit the theme.
|
||
|
||
- **If neither:** scan recent (last ~14 days) finds that are not yet referenced by any existing superpost. From the unreferenced pool, propose 1–3 thematic clusters of 5–10 finds each, with a candidate theme phrase per cluster.
|
||
|
||
Re-use is allowed — a find can appear in multiple superposts under different themes. But by default, prefer surfacing **unreferenced** finds first; only reach for re-uses when the theme genuinely calls for them.
|
||
|
||
### 2. Confirm the cluster
|
||
|
||
Always show the proposed cluster(s) before writing anything. The exact format depends on which path step 1 took.
|
||
|
||
**Seed mode** (slugs given) — split the seed from the expansion so the user can see what the inferred theme pulled in:
|
||
|
||
```
|
||
Theme inferred from seed: "<theme phrase>"
|
||
|
||
Seed (your selection):
|
||
- <slug>: <name>
|
||
- ...
|
||
|
||
Expansion (unreferenced finds matching the theme):
|
||
- <slug>: <name>
|
||
- ...
|
||
|
||
Final list (capped at 8): <N> items
|
||
```
|
||
|
||
**Multi-cluster mode** (no input):
|
||
|
||
```
|
||
Cluster A — "<theme phrase>"
|
||
- <slug>: <name>
|
||
- <slug>: <name>
|
||
- ...
|
||
|
||
Cluster B — "<theme phrase>"
|
||
...
|
||
```
|
||
|
||
Wait for the user to confirm, refine the theme phrase, or drop/swap items. Don't write anything until confirmed.
|
||
|
||
### 3. Write the superpost
|
||
|
||
File: `src/content/finds/<YYYY-MM-DD>-<theme-slug>.mdx` (theme-slug = kebab-case of the theme phrase, lowercase, ~30 chars max).
|
||
|
||
Frontmatter:
|
||
|
||
```yaml
|
||
---
|
||
title: "<Theme phrased as a noun phrase, max ~60 chars>"
|
||
date: YYYY-MM-DD
|
||
tags: [daily-finds, <topic-tag-1>, <topic-tag-2>]
|
||
description: "<One-line description for meta tags. Reuse the title if nothing better.>"
|
||
blurb: "<One short editorial sentence; appears as the post's secondary line in the home feed.>"
|
||
items:
|
||
- <slug>
|
||
- <slug>
|
||
- ...
|
||
---
|
||
```
|
||
|
||
Body: a brief audience-facing intro paragraph (1–2 sentences max) — open with "Today's catch" or a close variant; name what links these finds; vary the wording day to day. **No** numbered candidates, no headings inside the body, no list items — the grid renders from `items[]`.
|
||
|
||
Example body:
|
||
|
||
```mdx
|
||
> Today's catch from a morning sweep across the daily feeds. Five small things, each one built around exactly one virtue — a single sound, a single diagnostic, a single disguise, a single object made, a single quiet joke.
|
||
```
|
||
|
||
### 4. Verify
|
||
|
||
- Confirm every slug in `items[]` exists at `src/content/find/<slug>.mdx`. If any is missing, abort and report — never reference a non-existent find.
|
||
- Run `npm run build` to confirm the new superpost compiles.
|
||
|
||
### 5. Update the log
|
||
|
||
Append to `daily-finds.log.md`:
|
||
|
||
```
|
||
## YYYY-MM-DD — superpost: <theme>
|
||
|
||
Slug: <date>-<theme-slug>
|
||
Items referenced:
|
||
- <slug>
|
||
- <slug>
|
||
...
|
||
```
|
||
|
||
## Notes
|
||
|
||
- Default to 5 finds per superpost. Use 3 for tighter themes, up to 8 if the theme really supports it. Beyond 8 the grid stops being scannable.
|
||
- The body is for the audience, not the user. Never write "pick one", "candidates", "today's pick" — those are internal terms.
|
||
- Never edit existing find files when building a superpost. The find body and metadata are stable; the superpost only references them.
|
||
- If a find that's referenced has been graduated to a review (its frontmatter has `promotedTo`), it can still appear in the superpost — the grid card simply links to the find page, which itself links forward to the review.
|