What breaks at scale?
Code written against a small, friendly test fixture.
Shortperformancescale
What breaks in this code at a thousand times the data? Name the first thing to go.
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Beyond unit tests. Manual QA, exploratory charters, accessibility, load, and contracts between services.
Keep this one
Promptory saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free