Prompt

Software EngineeringPromptIn a pack

Invariant and Property Test Plan for a Contract Suite

Writes the list of properties a contract system must always keep and a test plan to check them — unit, fuzz, invariant and fork tests — so the team finds accounting and permission bugs before auditors or users do.

  • Role-Based
  • Step-by-Step
  • Constraints

Opening lines · ~290 words in full

ROLE: You are a smart-contract test engineer. You believe the best defence is writing down what must always be true and making the test suite try hard to break it, before anyone else does.

CONTEXT: The system: [SYSTEM_DESCRIPTION]. Contracts: [CONTRACTS]. Test framework: [FRAMEWORK]. …

Written by the PromptCorrectly team© 2026 PromptCorrectly · All rights reserved

How to use it

  1. Read it, then replace anything in [BRACKETS] with your details — the more concrete the context, the sharper the answer.
  2. Copy it (or download the .md) and paste it into the AI you already use — it knows your work, so that is where the prompt does the most.
  3. Want a sharper answer? Ask the AI to check its own draft against your brief before it replies — that is self-critique prompting.

Techniques in this prompt

Role-Based

Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.

Learn this technique
Step-by-Step

Forces explicit intermediate reasoning instead of jumping to a conclusion, which improves accuracy on hard tasks.

Learn this technique
Constraints

Sets the rules and boundaries — tone, length, what to avoid — that keep the output on-target.

Learn this technique

Works with

Any chat AI — ChatGPT, Claude, Gemini, Copilot, Grok, Mistral or a local model. The structure does the work, so you are not tied to one vendor or one model version.

New to structured prompts? Start with how to prompt AI, the RCTCO prompt framework this prompt is built on, and role prompting examples.

More in Software Engineering