HERO

search-usage

One-line value: Use search-usage as an execution-ready playbook, not a note.

When to use: Use this page when you need to execute this workflow in one focused session.

QUICK RESULT

If you only do one thing → complete the first checklist pass and publish one usable draft/output today.

ACTION CHECKLIST

• [ ] Clarify the exact output and success metric before starting.
• [ ] Gather required inputs from one trusted source only.
• [ ] Execute the workflow in sequence without adding side tasks.
• [ ] Run one quality check and fix the highest-risk issue first.
• [ ] Save the final result with a short reuse note.

EXAMPLE / DEMO

Before: Notes are scattered and decisions are unclear.

After: Inputs are structured, steps are executed, and the output is ready to use immediately.

WHY IT WORKS

• Converts vague intent into an explicit sequence.
• Emphasizes shipping one validated result fast.
• Creates repeatability for future runs.

NEXT ACTION

• Run this checklist on one live task now; keep scope to a single measurable outcome.

Source notes (kept for context)

Search works best when titles and summaries are consistent.

Make titles "actionable"

Good:

• "Deploy verification checklist"

• "Content seeding plan"

Not great:

• "Notes"

• "Update"

Use tags as facets

Add 1-3 facet tags, e.g.:

• ["tools","cloudflare","deploy"]

• ["posts","contract","metadata"]

Keep summaries short

Aim for one sentence. Lists prefer summary, then fall back to description.

Verify indexing

Open:

• /search/ for UI

• /search/index.json for the raw index (debug)