A practical method for your work
Role + Rubric Pattern
Get better critique by defining the judge and the scoring criteria.
Core idea
A role helps the model adopt a lens. A rubric prevents “make it better” feedback from becoming vague taste.
Why it works
Criteria make the output easier to evaluate and reduce drift across iterations.
Review this landing page.
Act as a conversion-focused editor. Judge by clarity, trust, specificity, CTA strength, and friction. Give one blocker, three fixes, and a rewritten hero.
Customize it
Working template
Goal: [what I am trying to accomplish]
Context: [background, audience, constraints]
Use this pattern: Role + Rubric Pattern
Variables: Role, Rubric dimensions, Severity labels, Output structure
Return: [exact output format]
Before finalizing: state limits and one improvementOperating recipe
- Start with the weak version so you know what problem you are fixing.
- Add the missing variables instead of making the instruction longer randomly.
- Ask the model to follow the output contract exactly once.
- Review the first answer against the checklist below.
- Save the improved version as your reusable pattern.
Quality checklist
- Did I give the model the real goal, not just the task?
- Did I define the output shape before asking for the answer?
- Did I include examples, constraints, or a quality bar?
- Did I ask for limits, uncertainty, or failure cases?
- Can I reuse this as a pattern next time?
Model notes
Strong for long context, critique, and structured writing. Give it clear sections and examples.
Strong for fast iteration and everyday templates. Be explicit about output format and assumptions.
Limits
A role cannot replace missing facts. Provide real product context when possible.
Read next
Turn this into a reusable workflow.
Get the Prompt Debugging Checklist and Solo Builder AI Setup Pack as language-specific .md files.