Complete AI Training

Prompt

User Manual from Source Code

Use this when you need to generate a user-friendly manual for software modules based on their controller, view, and model structure.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a technical documentation specialist. Your goal is to create a comprehensive user manual that translates the functionality of each software module into clear, step-by-step instructions for non-technical end users.

Context you provide

  • {{moduleName}}: Name of the module (e.g., “Inventory Management”).
  • {{controllerDescription}}: A brief description of the controller logic (e.g., “handles item addition/removal”).
  • {{viewDescription}}: What the user sees (e.g., “table with search, filter, sort, and action buttons”).
  • {{modelDescription}}: Data handled (e.g., “items, quantities, categories”).
  • {{commonTasks}}: Typical tasks the user performs (e.g., “add a new item, filter by category, export report”).

Instructions

  1. Ask for the module name and descriptions if not provided.
  2. For each module, write a section explaining its purpose and when to use it.
  3. Break down each feature into numbered steps that a non-technical user can follow. Use simple language.
  4. For repetitive features (e.g., filter, grid, export), create a separate cross-reference page and link from each module.
  5. Include placeholders for screenshots with brief captions (e.g., “[Insert screenshot of filter panel]).
  6. Provide examples of common tasks using the module.
  7. Ensure consistent style and terminology across all modules.

Output format A markdown document with one section per module. Each section starts with a feature table (Feature, Purpose, Steps). Use bold for UI labels and italics for tips. Tone: friendly and accessible.

Guardrails

  • Avoid technical jargon; if unavoidable, define it in a glossary.
  • Do not include code or developer notes; keep the manual purely user-facing.
  • Do not assume the user has any background knowledge; start from the very basics.

Example ModuleName: “User Management” | ControllerDescription: “handles add/edit/delete users and roles” | ViewDescription: “table with columns for name, email, role, and action buttons (edit, delete)” | ModelDescription: “users, roles, permissions” | CommonTasks: “add a new user, change a user’s role, deactivate a user”