mirror of
https://github.com/OpenRouterTeam/spawn.git
synced 2026-05-19 08:01:17 +00:00
53c7ead179
* fix(growth): enforce brevity in tweet prompt (target ≤140, hard cap 180) Recent posted tweets were running 170-200 chars and reading as long-form marketing copy. Tighten the tweet drafting prompt: - Add a dedicated "BREVITY IS THE #1 RULE" section at the top - Target 80-140 chars, hard cap 180 chars (down from the 280 platform limit) - Good/bad length examples drawn from actual prior drafts - Require a trim pass before output - Update output format and rules to reflect the new caps * fix(growth): drop numeric char targets, lean on taste Numeric targets (target 140, cap 180) just become the new goal. The model will pad to hit them instead of writing a punchy 40-char banger. Remove all char-count anchors from the brevity guidance and let the good/bad examples carry the signal. - Rename section from 'BREVITY IS THE #1 RULE' to 'Keep it short' - Drop 80-140 target, 180 cap, char-count example annotations - Drop Chars line from output format and charCount from JSON - Keep only the qualitative rules: don't pad, don't explain twice, prefer one sentence, cut what isn't pulling weight - Platform 280 cap mentioned once as a ceiling, not a goal * fix(growth): strip all length references from tweet prompt Even mentioning '280 char limit' or 'platform limit' anchors the model to the wrong end of the range. Remove both remaining length references so the prompt is purely about taste: say less, don't pad, cut what isn't pulling weight. The platform enforces its own limit. - Drop the 'platform 280 char limit is a ceiling' paragraph - Drop 'Must fit in a tweet (under the platform limit)' from rules --------- Co-authored-by: Claude <claude@anthropic.com> |
||
|---|---|---|
| .. | ||
| rules | ||
| scripts | ||
| skills | ||
| settings.json | ||