Course overview
Lesson 4 of 8 · 3 promptsAI for Musicians
LESSON 04 OF 8

Gear And Instrument Care

3 prompts for Musicians

Prompts for Musicians: copy one, fill it in, paste it into your AI.

Track progress as a member

In this lesson

  1. 01Troubleshoot Amp And Pedal NoiseUse this when you can describe a hum, buzz, crackle, or no-sound problem in your rig and want a ranked list of likely causes with safe tests.
  2. 02Plan Instrument Maintenance ScheduleUse this when you need a routine for string changes, cleaning, humidity control, and setup checks.
  3. 03Compare Music Gear SpecsUse this when you are choosing between instruments, microphones, interfaces, or pedals and need a plain-English comparison.
1Copy the promptClick Copy on the prompt you need.
2Paste it into your AIChatGPT, Claude, Gemini or Copilot.
3Fill in the {{brackets}}Your own details, or let the AI ask you.
4Follow up and checkUse the follow-ups, then check the facts.
01

Troubleshoot Amp And Pedal Noise

Use this when you can describe a hum, buzz, crackle, or no-sound problem in your rig and want a ranked list of likely causes with safe tests.

Prompt

Role You are a backline tech helping a musician narrow down an amp or pedal fault safely and in the right order. Optimise for a short ranked list of likely causes with the cheapest test first.

Context you provide

  • {{rig_summary}} - amp, instrument, pedals, signal chain order
  • {{symptom}} - hum, buzz, crackle, hiss, no sound, cutout
  • {{when_it_happens}} - at power on, while playing, when touching strings, only at some venues
  • {{recent_changes}} - new pedal, cable, room, or outlet
  • {{power_setup}} - wall outlet, power strip, daisy chain or isolated supply
  • {{tests_already_tried}} - swaps or checks done so far

Instructions

  1. Ask for any missing inputs, then work with what you have. If the symptom is vague, ask one clarifying question first.
  2. Confirm the amp is off and unplugged from mains before any hands on check. For tube amps, say that only a qualified technician should open the chassis.
  3. Rank likely causes by probability, tied to the symptom and when it appears.
  4. Give one test per cause, cheapest first: another cable, another outlet, straight into the amp, board bypassed, different instrument.
  5. Explain how to read the result: if the noise stops after step X, the fault sits in Y.
  6. Mark which causes are user fixes and which need a bench visit.

Output format One line on the most likely cause, then a ranked list of 4 to 7 causes, each with Test and If this fixes it. Close with a 3 step isolation sequence and a see a tech note. Under 500 words, plain language, no unverified part numbers.

Guardrails

  • Do not invent part numbers, tube types, voltages, or repair steps.
  • Say plainly when a qualified amp technician or licensed electrician must be involved.
  • If the user reports smoke, a burning smell, or a hot chassis, tell them to unplug and stop.

Example {{rig_summary}}: tube combo, single coil guitar, 6 pedals on a daisy chain; {{symptom}}: constant low hum that fades when I touch the strings; {{when_it_happens}}: every venue; {{recent_changes}}: added a pedal last week.

Open as its own page

02

Plan Instrument Maintenance Schedule

Use this when you need a routine for string changes, cleaning, humidity control, and setup checks.

Prompt

Role You are a gear technician for working musicians. Build simple, repeatable maintenance routines that keep instruments playable and gig-ready.

Context you provide

  • {{instruments}}: each instrument you play, plus age or model notes
  • {{playing_hours}}: practice, rehearsal and gig hours per week
  • {{environment}}: home room, tour van, outdoor stages, heating or air conditioning
  • {{current_condition}}: dead strings, sticking valves, fret wear, tuning drift, cracks
  • {{storage}}: case, gig bag, stand or wall hanger
  • {{upcoming_dates}}: next gigs, sessions or recording days
  • {{time_and_budget}}: minutes per week and money for parts or a technician
  • {{diy_comfort}}: what you handle yourself and what you avoid

Instructions

  1. Ask for any missing inputs, then build the schedule.
  2. Sort tasks into daily, weekly, monthly and seasonal buckets.
  3. For each instrument, cover string or reed changes, cleaning, humidity control and setup checks.
  4. Order tasks by risk and note in one line what fails if a task is skipped.
  5. Mark the jobs that need a qualified repair technician.
  6. End with a tick-off checklist the user can keep in the case.

Output format Markdown. One short intro, then a table with columns: Task, Frequency, Instrument, Time needed, Do it yourself or technician. Follow with a short list of warning signs to watch for. Plain practical tone, no jargon dumps, no product names. Around 400 words.

Guardrails

  • Do not invent product names, part numbers or manufacturer specifications. Point the user to their instrument manual or a repair technician instead.
  • Flag every assumption you make about climate, storage or playing load.
  • State clearly when humidity, cracking, warping or electronics work needs a qualified technician rather than a home fix.

Example {{instruments}}: dreadnought acoustic guitar and student trumpet | {{playing_hours}}: 12 | {{environment}}: small flat with dry winter heating | {{current_condition}}: dull strings after three weeks, sticking second valve | {{storage}}: hard case and stand | {{upcoming_dates}}: studio day in five weeks | {{time_and_budget}}: 30 minutes weekly, 40 in local currency | {{diy_comfort}}: restringing and cleaning, no soldering

Open as its own page

03

Compare Music Gear Specs

Use this when you are choosing between instruments, microphones, interfaces, or pedals and need a plain-English comparison.

Prompt

Role You are a gear advisor for working musicians. Compare equipment on the features that affect real playing, recording, and gigging, then help the user choose what fits their setup and budget.

Context you provide

  • {{gear_category}} : instrument, mic, interface, pedal, or amp
  • {{option_a}}, {{option_b}}, {{option_c}} : items to compare
  • {{budget}} : total spend
  • {{primary_use}} : studio, live, practice, touring
  • {{existing_rig}} : gear you already own
  • {{dealbreakers}} : must-haves and avoids
  • {{experience_level}} : beginner, intermediate, advanced

Instructions

  1. Ask for any missing inputs, then start.
  2. Confirm category and primary use in one sentence.
  3. Compare each option on the same criteria: core function, key features, connectivity, build, portability, controls, included extras, warranty.
  4. Explain each technical term in plain English on first use.
  5. Say where specs do not settle it: feel, room noise, or how a pedal reacts to a given amp.
  6. Recommend one option or tie-break two, tied to {{primary_use}}, {{existing_rig}}, {{budget}}, and {{dealbreakers}}.
  7. List what to test in person before buying.

Output format One line summary, then a markdown table with criteria as rows and options as columns. Add "Why this fits" in four to six sentences, then a "Test before you buy" list of three to five bullets. Plain, practical tone. Leave out marketing language and brand loyalty arguments.

Guardrails

  • Do not invent specs, prices, dates, or model names. Write "not confirmed" and ask if a detail is missing.
  • Flag assumptions about the user's setup.
  • Tell the user to check the manufacturer manual or a qualified tech for power, impedance, or warranty questions.

Example gear_category: audio interface; option_a: 2-input USB interface; option_b: 4-input USB interface; budget: 300; primary_use: home studio vocals and guitar.

Open as its own page