Effective AI Prompting

  • Updated on Mar 12, 2025
  • Published on Nov 27, 2024
  • 3 minute(s) read

A Guide to Writing Effective AI Prompts

Introduction

Writing clear and effective prompts for AI systems is crucial for obtaining the desired results. This guide aims to outline the key principles and best practices for crafting AI prompts, as well as highlighting common pitfalls to avoid.

Key Ways to Think About Clarity for Prompts

  1. Be specific: Clearly state what you want the AI to do or provide.
  2. Use context: Provide relevant background information when necessary.
  3. Break complex tasks into smaller steps: This helps the AI understand and process your request more effectively.
  4. Use examples: Illustrate your expectations with concrete examples when possible.

Be Precise

  1. Choose your words carefully: Use unambiguous language and avoid vague terms.
  2. Quantify when possible: Use numbers or specific measurements instead of general terms like "many" or "few."
  3. Specify output format: Clearly state how you want the information presented (e.g., list, paragraph, table).
  4. Define parameters: Set clear boundaries for the AI's response, such as word count or time frame.

Best Practices

  1. Start with a clear objective: Know what you want to achieve before writing your prompt.
  2. Use appropriate tone and style: Adjust your language to match the desired output.
  3. Proofread your prompt: Ensure there are no spelling or grammatical errors that could confuse the AI.
  4. Iterate and refine: If you don't get the desired results, adjust your prompt and try again.
  5. Leverage system messages: Use them to set the AI's role and behavior for the conversation.

Things to Avoid (Bad Results)

  1. Don't be too vague: Avoid open-ended questions without context or specifics.
  2. Avoid contradictory instructions: Make sure your requirements are consistent throughout the prompt.
  3. Don't overload with information: Keep prompts focused and avoid unnecessary details.
  4. Avoid using jargon or slang: Unless specifically required, use clear and standard language.
  5. Don't assume AI knowledge: Provide necessary context, especially for current events or specialized topics.
  6. By following these guidelines, you can significantly improve the quality and relevance of AI-generated responses to your prompts.

Good Prompt vs. Bad Prompt

Good Prompt:

Create step-by-step instructions for a Windows 10 user to change their time zone to Pacific Time (US & Canada), set their region to United States, and change the short date format to MM/dd/yyyy. Include how to access the necessary menus and any confirmation steps required.

Why it's good:

  • Specifies the Windows version.
  • Clearly outlines all required tasks.
  • Asks for step-by-step instructions.
  • Requests information on accessing menus and confirmation steps.

Bad Prompt:

Tell me how to change some Windows time settings.

Why it's bad:

  • Vague and lacks specificity.
  • Doesn't mention which settings need to be changed.
  • Fails to specify the Windows version.
  • Doesn't ask for step-by-step instructions.
  • Suggestion for improvement: "Provide detailed, step-by-step instructions for changing the time zone, region, and short date format in Window.

Good Examples

Here are some automated prompts for evaluating a user's work in a lab environment:

Windows Lab

  • Batch Script for Backup:

    • Batch script file named backup.bat exists in c:\backup.
    • Script contains a command to copy files to a network drive F:.
    • Task Scheduler has a task named "Daily Backup" set to run backup.bat at 6 PM daily.

  • Static IP Configuration:

    • Network settings dialog box is open.
    • Setting named "IP address" has a value of 192.168.1.x.
    • Setting named "Subnet mask" has a value of 255.255.255.0.
    • Setting named "Default gateway" has a value of 192.168.1.1.

  • Docker Installation:

    • Docker Desktop application is installed and the executable Docker Desktop.exe is present in C:\Program Files\Docker\Docker.
    • A desktop shortcut named "Docker Desktop" exists on the user's desktop.
    • Docker service is running, verified by the command Get-Service -Name com.docker.service returning a status of "Running".
    • Command docker --version returns the installed Docker version, e.g., Docker version 20.10.7, build f0df350.

  • Performance Troubleshooting:

    • Task Manager is open.
    • No processes are using more than 80% CPU.
    • No processes are using more than 75% memory.
    • Disk Cleanup utility has been run.

Linux Lab

  • Shell Script for Log Management:

    • Shell script file named archive_logs.sh exists in the directory /var/log/scripts.
    • Script contains a command to compress and archive log files older than 30 days using tar and gzip.
    • Cron job is set to run archive_logs.sh daily at 2 AM, verified by the entry in the crontab file (crontab -l).

  • Static IP Configuration:

    • Network configuration file /etc/netplan/01-netcfg.yaml exists.
    • File contains settings for a static IP address.
    • Command netplan apply has been run successfully.

  • Apache Installation:

    • Apache service is installed.
    • Apache service is running.
    • Command apache2 -v returns the installed Apache version.

  • Boot Issue Troubleshooting:

    • Boot logs have been checked using journalctl -xb.
    • Command fsck has been run on the root filesystem.
Related articles