How to use
Get the most out of the library in 4 steps
Every prompt follows a clear structure: expert role, topic, inputs, task and output format. Choose the right prompt and fill in real data.
Choose a discipline
Use the menu on the left, or describe the job in the search box to get the matching prompt.
Choose a task
Each discipline has 15–25 tasks such as method statements, RCM, MOC or weekly reports.
Choose a prompt style
The style shapes the output: checklist, comparison, email, root cause analysis and more.
Fill in and copy
Type your project name and data into Quick fill, click Copy and paste into ChatGPT, Claude or Copilot.
Anatomy of a prompt
Knowing each part helps you adapt the prompt to your situation.
You are a senior QA/QC engineer.expert roleTopic: Checklists & ITPstaskProject: [Project name]fill inContext: [Paste your data…]real data gives better answersTask: Build a field-ready checklist…what the AI must doColumns: No. | Check item | Acceptance…output formatReading a prompt code
Each prompt has a code like MEP-04.13: discipline – task number – style number. Type the code into the search box to reopen it.
The 20 prompt styles and when to use them
| No. | Prompt style | Use when |
|---|---|---|
| 01 | Draft from Scratch | You need a complete first version fast. |
| 02 | Review & Improve | You already have a draft and want it checked. |
| 03 | Compare Options | You must choose between two or more solutions. |
| 04 | Organize My Notes | You have messy notes or raw data to clean up. |
| 05 | Ask Me First | The scope is unclear and you want the AI to interview you. |
| 06 | Field Checklist | You need something to verify work step by step. |
| 07 | Step-by-Step Method | You want to understand how to do it properly. |
| 08 | Formal Document | The output goes into an official document. |
| 09 | Code & Spec Compliance | You must trace work to a standard or specification. |
| 10 | Risk Register | You need to identify and control what could go wrong. |
| 11 | Executive Brief | Management needs the picture on one page. |
| 12 | Professional Email | You must communicate clearly with a client or contractor. |
| 13 | Root Cause Analysis | Something went wrong and must not happen again. |
| 14 | Action Tracker | You need to follow up many open items. |
| 15 | Bilingual VI–EN | The output must serve Vietnamese and English readers. |
| 16 | Meeting Preparation | You want a meeting that ends with decisions. |
| 17 | Data Insight | You have numbers and need to know what they say. |
| 18 | Learning Path | You or your team want to build the skill. |
| 19 | Interview Coach | You are hiring, or preparing for a technical interview. |
| 20 | AI & Automation | You do this work often and want to save time. |
Chain prompts for bigger work
Complex work goes better in steps: one prompt per step, in the same conversation.
Write a new document
- Ask Me First
- Draft from Scratch
- Review & Improve
- Formal Document
Handle an incident
- Root Cause Analysis
- Risk Register
- Action Tracker
- Executive Brief
Make a decision
- Organize My Notes
- Compare Options
- Executive Brief
- Professional Email
Keyboard shortcuts
Using AI responsibly in engineering work
- The more real data you provide (figures, standards, drawings, scope), the better the result.
- AI output is a draft. Anything affecting safety, design, cost or contracts must be reviewed by a competent engineer.
- Ask the AI to state its assumptions and references; do not accept code clause numbers you have not verified.
- Do not paste confidential client or company data into public AI tools without authorization.