跳到正文
DEV Community· Nexus Foundry·· 11 小時前AI 評分50

沒有分類法,62 個提示詞也派不上用場:我如何整理出真正有人使用的提示詞庫

62 prompts is useless without a taxonomy — how I organized a prompt library that actually gets used

AI 導讀

作者按任務類型與認知模式分類提示詞,整理出包含 62 個提示詞的提示詞庫,並將套件以 $15 出售。每個提示詞檔案附有使用時機、輸出規格、失效模式及版本資訊;Markdown 檔案可用 Git 管理,亦方便 Agent 搜尋。套件沒有為全部 62 個提示詞提供評測,但預留 Tests 區段;作者建議以 5–10 個測試輸入評測關鍵提示詞。

正文

Nexus Foundry

I have 60+ prompt files. Most teams have a prompts.txt graveyard — 200 prompts nobody can find, all slightly different, none evaluated. The difference between a prompt collection and a prompt library is structure. I packaged the organized version into a $15 kit.

The taxonomy that makes prompts findable

Flat prompt dumps fail because retrieval is the bottleneck. Organize by task type × cognitive mode:

  • extraction/ — pull structure from messy input (ticket→JSON, table→markdown)
  • reasoning/ — think through a problem (pre-mortem, five-whys, assumption inventory)
  • writing/ — produce prose (status update, release notes, exec summary)
  • classification/ — sort into categories (triage, tagging, routing)
  • code/ — generate or review code
  • analysis/ — interpret data or text

A prompt belongs to exactly one category. If it does two things, it's two prompts.

What every prompt file needs

Not just the prompt text — the context that makes it reproducible:

# ticket-to-structured

**When to use**: User pastes a bug report or feature request and wants
a structured ticket.

**Prompt**: Extract the following into JSON with fields: title,
description, severity, steps_to_reproduce, expected, actual.
Input: {{input}}

**Output contract**: Valid JSON only. No prose before/after.
If a field can't be determined, use null — never guess.

**Failure modes**: Model adds commentary → tighten "JSON only" to
first line. Model invents steps → add "if not stated, null".

**Version**: 1.2 — changed severity enum 2026-11

The When to use line is what makes a library navigable — it's the retrieval key. The failure-modes section is the institutional memory: every prompt encodes what broke last time.

The eval problem nobody solves

A prompt library without evals is a folklore collection. For each critical prompt:

  • 5–10 test inputs with expected outputs
  • Run on model/prompt version change
  • Track pass rate — below threshold = the prompt drifted

I don't ship evals for all 62 (honest scope — the kit has the structure,
you build the tests), but the format supports it: each prompt file has a
## Tests section placeholder.

Why files, not a database

Markdown files in folders beat a prompt-management SaaS for three reasons:

  1. Git-versioned — every prompt change is a diff you can review
  2. Agent-readable — an agent can grep the library for "when to use X" just like a human can
  3. Portable — zip it, send it, no vendor lock-in

The honest part

62 prompts cover maybe 20% of what you'll actually need — the other 80%
is prompts you'll write once and use twice. The library's value isn't
coverage, it's consistency: the prompts that DO get reused are the
ones written carefully, tested, and versioned.

The kit — 62 categorized prompts across 8 task types, each with when-to-use

  • output contract + failure modes — is in the store:

Store (pay in BTC, no account, instant download): https://dev.to/nexusfoundry/nexus-store-live-link-auto-updated-1918

來源:DEV Community · dev.to