Expand editorial search and add task categories for skills

[benvinegar]

Problem

Project search matches names, repository identity, taglines, hooks, and languages, but excludes summaries, technique explanations, and takeaways. Useful examples can therefore be missed even when the analysis addresses the reader’s query. The 749-skill directory offers project and supporting-file filters but no task categories.

Proposed change

Expand project search to include editorial content and technique names. Support a small, explicit set of common aliases and show a short passage explaining why a result matched. Add a modest task taxonomy to skill discovery while preserving upstream descriptions and project ownership.

Acceptance criteria

• Queries can find relevant summaries, techniques, and takeaways, with useful matching context.
• Common terms and multiword queries have documented, predictable matching behavior.
• Skill categories are clearly editorial metadata, separate from upstream descriptions.
• Filters compose correctly, support clearing, and retain useful empty states.
• Keep search data compact and source/tokenization work outside browser bundles.
• Cover meaningful search cases and verify keyboard/mobile behavior; run lint, typecheck, and build if data loading changes.

Relevant files: components/agents-md-data.ts (matchesQuery), components/project-explorer.tsx, components/skill-explorer.tsx, lib/skill-list.ts.