If you’ve been using AI for your job search, you already know the difference between “write me a resume” and a prompt that produces something you can actually submit. The secret is directives: short, repeatable instructions that tell the AI what to do, what to avoid, what inputs to use, and what quality bar to hit.

Below is a practical, current directive library you can copy/paste and reuse for employers in and around Grand Rapids, Minnesota—from healthcare and education to manufacturing, county roles, retail, and seasonal tourism.

What an “AI directive” is (and why it works)

A directive is a stable instruction you keep in your toolkit. You then add job-specific details (the posting, your experience, your constraints) as variables.

A good directive usually includes:

  • Role and goal (What are we producing? For whom?)
  • Inputs (Job post, resume, accomplishments, constraints)
  • Rules (Length, tone, formatting, keywords, truth-only)
  • Quality checks (ATS scan, gap analysis, clarity pass)
  • A next step (Questions the AI must ask if info is missing)

If you treat directives like reusable “macros,” you’ll get consistent results and spend less time rewriting.

How to use these directives (2-minute setup)

  1. Create a single note called “Grand Rapids Job Search — AI Directives.”
  2. For each application, paste in:
    • The full job posting text
    • Your master resume (or work history)
    • 3–6 measurable wins (even small ones)
    • Any constraints (schedule, commute radius, pay floor)
  3. Choose the directive that matches your task.

Truth rule: Never ask AI to invent degrees, certifications, job titles, or dates. Use AI to present your story, not fabricate one.

Directive 1: Local fit summary (the “why you, why here” paragraph)

Use this when you need a fast, credible opener for small-market employers who value reliability.

DIRECTIVE: Write a 90–120 word “local fit” summary for a job application.
INPUTS: (1) Job posting text, (2) my experience bullets, (3) my location/commute limits.
RULES: Plain language, no buzzwords, no exaggerations. Mention 2 relevant skills + 1 reliability signal (attendance, safety, shift coverage, customer trust, teamwork).
OUTPUT: One paragraph + 3 optional sentence variations.
ASK FIRST if missing: role title, schedule, top 3 requirements.

Directive 2: Resume tailoring (ATS + human readable)

This is your main workhorse.

DIRECTIVE: Tailor my resume to this job without changing facts.
INPUTS: Job posting + my master resume.
RULES:
- Keep it to 1 page unless my experience clearly requires 2.
- Use employer-friendly wording; avoid clichés.
- Integrate the job’s keywords naturally (no keyword stuffing).
- Add metrics only if I provide them.
OUTPUT:
1) Revised resume in clean sections.
2) A “keyword coverage” checklist: Required vs Present vs Missing.
3) 5 questions to improve accuracy (metrics, tools, scope).

Directive 3: Achievement bullets from “regular work”

If you’ve done dependable work (retail, custodial, warehouse, food service, CNAs, admin), you still have achievements. This directive pulls them out.

DIRECTIVE: Convert my duties into 8 achievement bullets.
INPUTS: My job title, tasks, tools used, who I served, and any constraints (time, staffing, volume).
RULES: Use action + result. No numbers unless I give them. Emphasize safety, accuracy, customer trust, reliability, teamwork.
OUTPUT: 8 bullets + 3 suggested metrics I could estimate responsibly.

Directive 4: Cover letter that doesn’t feel generic

Keep it short. In many Grand Rapids–area hiring processes, the letter is skimmed—so make it skimmable.

DIRECTIVE: Draft a short cover letter.
INPUTS: Job posting + tailored resume.
RULES:
- 180–250 words.
- 3 short paragraphs: (1) interest + fit, (2) 2 proof points, (3) availability + thanks.
- Match the employer’s tone: practical, respectful, community-minded.
OUTPUT: Final letter + 2 alternate opening lines.

Directive 5: Application risk check (red flags before you submit)

This prevents “oops” mistakes.

DIRECTIVE: Review my resume + cover letter for risks.
CHECK FOR:
- Date inconsistencies
- Overclaims (software, certifications, leadership)
- Vague phrases (“responsible for”) that should be specific
- Missing shift availability or licensing details
OUTPUT: A punch list of fixes ranked High/Medium/Low risk.

Directive 6: Networking message for small-town realism

Networking in smaller communities is often about reputation and clarity, not hype.

DIRECTIVE: Write a networking message I can send to a local contact.
INPUTS: Who they are, how we know each other, the role I want, my 2 relevant strengths.
RULES:
- 70–110 words.
- No “pick your brain.”
- Ask one clear question OR request a 10-minute call.
OUTPUT: Text message version + email version.

Directive 7: Interview prep that fits local hiring

This builds answers that sound like a real person.

DIRECTIVE: Generate interview prep for this role.
INPUTS: Job posting + my resume + any concerns (gap, career change, limited experience).
OUTPUT:
- 8 likely questions + strong sample answers in my voice
- 5 stories in STAR format (safety, conflict, customer issue, mistake recovery, teamwork)
- 6 questions I should ask the employer (training, schedule, success metrics)
RULES: Answers must be 45–75 seconds when spoken.

Directive 8: “Tell me about yourself” (30-second + 90-second)

A clean opener can change the whole interview.

DIRECTIVE: Write two versions of “Tell me about yourself.”
INPUTS: My recent roles, target job, and strongest 3 skills.
OUTPUT: A 30-second version and a 90-second version.
RULES: No fluff. End with why I’m applying and what I’m looking for next.

Directive 9: Pay and schedule negotiation script (respectful, firm)

Negotiation is easier when you plan the words.

DIRECTIVE: Create a negotiation script.
INPUTS: Offer details (pay, schedule, benefits), my minimum, and my top 2 reasons for higher pay.
OUTPUT:
- Phone script (60–90 seconds)
- Email counteroffer
- If/then options (if they can’t raise pay, ask about steps, differential, hours, PTO, review timeline)
RULES: Professional, grateful, non-apologetic.

Directive 10: Weekly job search plan (lightweight, consistent)

Small markets reward consistency and follow-through.

DIRECTIVE: Build a 5-day job search plan I can repeat weekly.
INPUTS: My target roles, commute radius, hours available, and any barriers (childcare, transportation).
OUTPUT:
- Daily checklist (30–60 minutes/day)
- 2 applications/day max with quality tailoring
- Follow-up schedule and message templates
RULES: Include one networking action and one skill action per week.

Directive 11: Skills gap bridge (fast upskilling plan)

Use this if postings ask for tools you don’t have yet.

DIRECTIVE: Identify my top 3 skill gaps for this job and propose a 14-day plan.
INPUTS: Job posting + my current skills.
OUTPUT:
- Gap list ranked by hiring impact
- 14-day practice plan with daily 20–30 minute tasks
- A resume bullet I can add only after I complete real practice
RULES: No pretending. Emphasize demonstrable work samples.

Directive 12: Guardrails (privacy + accuracy rules you keep on)

Paste this at the end of any AI request where you’re sharing sensitive info.

GUARDRAILS:
- Do not invent facts, dates, credentials, or job titles.
- If information is missing, ask questions before writing.
- Do not include my full address, SSN, DOB, or unrelated medical details.
- Use plain language and keep claims defensible.

Make these directives “current” for you

The best directive set is the one you maintain. Once per month, update:

  • Your master resume (add a new bullet for every meaningful win)
  • Your preferred schedule and commute radius
  • Your top 10 target employers/industries nearby
  • Your current training (even informal practice counts if it’s real)

If you want, paste a job posting and your current resume text, and I can help you choose which 3 directives to run first—and what inputs will make the output strongest.