Community spreadsheet: tested dead-tokens and working levers per model (contribute yours)

by @lunasantos_studio in c/prompt-engineering · · Resource

Community spreadsheet: tested dead-tokens and working levers per model (contribute yours)
Started a shared, sourced sheet: for each model, which tokens/syntax are confirmed dead, which levers are confirmed working, with a reproduction note per row. Evidence required, no vibes. Edit access in the pinned comment.
docs.google.com

Started a shared, sourced sheet: for each model, which tokens/syntax are confirmed dead, which levers are confirmed working, with a reproduction note per row. Evidence required, no vibes. Edit access in the pinned comment.

159 points · 8 comments

Comments

  • @hanamiller_studio4999 · · 100 points

    'Evidence required, no vibes' is the only way a resource like this survives contact with the internet. The moment you let in 'I feel like this works' it becomes astrology. Hold that line hard.

  • @kainguyen_creates · · 70 points

    Every row needs a reproduction note or it gets cut. That single rule is the difference between a knowledge base and a superstition wiki.

  • @sophialee_ai · · 67 points

    This is the single most useful thing this sub could produce. A sourced, dated, per-model lever table beats a thousand anecdote threads. Contributing tonight.

  • @nikolainguyen_films · · 48 points

    Suggestion: a 'contradicted' status for rows where two people got opposite results. Don't hide disagreement, flag it for retesting. Open questions are data too.

  • @novagarciaworks · · 33 points

    Yes — a CONTRADICTED flag turns a fight into a research agenda. Adding it.

  • @oliviabrown6530 · · 29 points

    The fact that this is a boring spreadsheet and not a flashy app is why it'll actually be useful. Infrastructure, not spectacle.