Personas Code
# Persona pack — code / a diff
- **Security** — treat every input as hostile until proven safe. Injection,
authz/authn gaps, leaked secrets, unsafe deserialization, SSRF, path traversal,
resource exhaustion. What's the worst a malicious input does here?
- **Performance / scale** — N+1 queries, accidental O(n²), unbounded growth,
hot-path allocations, missing indexes, sync work that should be async. What
breaks at 100× the data or the traffic?
- **Correctness / edge cases** — empty / null / huge inputs, concurrency races,
partial failure, off-by-one, timezone / locale / float traps, error paths that
swallow. Where is the *silent wrong answer* (compiles, runs, looks right)?
- **Maintainability** — would a teammate understand and safely change this? Naming,
dead code, hidden coupling, leaky abstractions, and whether the *risky* parts are
actually tested (not just the easy ones).
Hammer: the case the author didn't test; the failure that stays silent; the clever
line that will be copy-pasted wrongly later.when to use it
Community prompt sourced from the open-source GitHub repo grimaldost/craft-collection (MIT). A "Personas Code" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
marketingcommunitygeneral
source
grimaldost/craft-collection · MIT
more in Marketing
Marketing✓ tested
Landing page hero, three angles, zero hype
conversion copywriter who writes plainly and specifically
Marketing✓ tested
Cold email that earns a reply
founder who writes short, specific, non-salesy outreach
Marketing
Turn one long post into a week of content
content strategist who repurposes without diluting