Custom Claude Project: Your Personal Recruiting Assistant

What This Builds

A persistent Claude workspace pre-loaded with your agency's brand voice, your common client profiles, your top-performing submittal examples, and your typical job description templates. Every conversation you open starts from this shared understanding — no more explaining who you are, what market you work in, or how you like things formatted. Instead of pasting a new paragraph of context before every prompt, you open Claude and it already knows you're a recruiter at a light industrial staffing firm in the Southeast, you work with 12 regular manufacturing clients, and your submittals follow a specific three-paragraph structure your clients expect.

Prerequisites

• Claude Pro account ($20/month at claude.ai)
• 2–3 examples of your best-performing candidate submittals
• A copy of your agency's standard job description format or brand guidelines
• Notes on your 3–5 most common requisition types (titles, typical requirements, common client names or industries)

The Concept

Think of it like onboarding a new assistant who shadows you for two weeks before their first day. When they finally sit down, they already know your clients by name, they've read every submittal you've sent, and they know you prefer direct language over corporate fluff. A Claude Project works the same way — you do the onboarding work once (loading in your context documents and writing a system prompt), and then every conversation you have inside that Project starts from that foundation. You don't repeat yourself. The AI doesn't ask what an "ATS" is.

Build It Step by Step

Part 1: Set Up Your Claude Project

1. Log in to claude.ai with your Pro account
2. In the left sidebar, click Projects (or the "+" next to Projects)
3. Click New Project
4. Name it something like "Recruiting Assistant — [Your Market]" (e.g., "Recruiting Assistant — Light Industrial Southeast")
5. You'll land on the Project configuration screen with two sections: Project Instructions and Knowledge

Part 2: Write Your System Instructions

Click into Project Instructions and paste the following, customizing the bracketed sections:

You are a professional recruiting assistant for a staffing agency specializing in [light industrial / professional / healthcare / etc.] placements in [your region/market]. You help write candidate submittals, job descriptions, outreach messages, pipeline update emails, and interview coaching documents.

About my agency:
- Name: [Agency Name]
- Market focus: [geographic markets you cover]
- Specialties: [top 3 role types — e.g., warehouse supervisors, CNC machinists, forklift operators]
- ATS: [Bullhorn / Greenhouse / Lever / etc.]

Writing preferences:
- Submittals: 3 paragraphs. Paragraph 1 = candidate's strongest qualification linked to the client's requirement. Paragraph 2 = skills match and relevant experience details. Paragraph 3 = availability, compensation, and recruiter recommendation. Professional and confident tone. Never use hollow phrases like "strong work ethic" or "team player" without specifics.
- Job descriptions: Lead with a 2-sentence role summary. Bullet point responsibilities (7–9 bullets). Separate "Required" from "Preferred" qualifications. Close with a brief statement about the work environment.
- Outreach messages: 3 sentences max for LinkedIn InMail. Reference the candidate's specific background. Direct. Do not use "I came across your profile."
- Client emails: Confident and proactive. Lead with good news or clear status. Be direct about bottlenecks. Close with a specific ask.

My common clients include: [list 3–5 client types or actual client industries — e.g., "automotive parts manufacturers," "regional distribution centers," "food processing facilities"]. When writing submittals or client communications, use language that reflects these industrial environments.

Always ask for clarification if the candidate's screen notes or job requirements are incomplete before drafting.

Adjust every bracketed section to match your actual practice. The more specific you are here, the better every output will be.

Part 3: Add Your Knowledge Documents

Click Add Content in the Knowledge section. Upload or paste each of the following:

Document 1: Your Top Submittal Examples Paste in 2–3 of your best-performing submittals (ones that led to interviews or placements). Remove candidate names and client names if you prefer, replacing with "[Candidate]" and "[Client]." Label the document "Submittal Examples."

Document 2: Common Requisition Types Create a simple text document with your most common req types and what clients usually want:

COMMON REQUISITION TYPES

Warehouse Supervisor / Shift Lead
- Typically requires: 3+ years supervisory experience, WMS familiarity (SAP or Manhattan preferred), forklift certified or willing
- Common client priorities: hands-on with the team, manages 15–30 people, comfortable with metrics tracking
- Comp range typical: $55,000–$75,000 salary or $26–$32/hour

CNC Machinist (Setup & Run)
- Typically requires: Haas/Fanuc controller experience, blueprint reading, 2+ years production machining
- Common client priorities: ability to set up independently, quality-focused, stable work history
- Comp range typical: $22–$30/hour

[Add your other common roles in the same format]

Document 3: Your Agency Job Description Template Paste your standard JD format so Claude always mirrors it exactly.

Part 4: Test and Refine

Open your first conversation inside the Project (click "New Chat" while inside the Project). Run these three tests:

Test 1 — Submittal draft:

Screen notes: 7 years warehouse exp, currently team lead at a regional DC, managed 18 people, familiar with RF scanners and SAP WMS, available in 3 weeks, asking $70K, very interested, relocating back to family in the area. Role: warehouse supervisor at an automotive parts distribution center. Client cares most about hands-on supervisory experience and SAP.

Check: Does the output follow your three-paragraph structure? Does it avoid generic phrases? Does it lead with the right strength?

Test 2 — JD draft:

Write a job description for a CNC Setup Machinist. Requirements: Haas experience required, blueprint reading, 3+ years, second shift (3pm–11pm), $26–$29/hour, full benefits, Tier 1 automotive supplier in [your city].

Check: Does it follow your preferred format? Is the tone right for your market?

Test 3 — Outreach message:

Candidate: Production Supervisor at a regional food manufacturer, 9 years, managed 2 lines of 12 people each, lean certified. Role: I'm filling a plant supervisor position at a $150M manufacturer nearby. Step up in scope, direct report to the Plant Manager, $90K.

Check: Is the InMail under 3 sentences? Does it reference their specific background?

If any output is off, go back to your system instructions and add a clarification. Common fixes:

• Output is too long → add "Keep submittals under 200 words."
• Tone is too formal → add "Write as a human recruiter, not a corporate HR document."
• Wrong industry language → add specific terminology you use with clients

Real Example: Monday Morning Submittal Run

Setup: Project configured for a light industrial staffing desk in the Mid-Atlantic, with 3 submittal examples loaded and CNC/warehouse req types defined.

Input (pasted into Claude, no context-setting needed):

Submittal needed.

Candidate screen notes: Maria G. — 12 years total manufacturing exp, currently quality inspector at a plastics manufacturer, 4 years in that role, previously production lead for 6 years managing a 10-person team. Associate's degree in manufacturing technology. ISO 9001 internal auditor certified. Available in 2 weeks, asking $68K, very motivated — current company just announced layoffs. Drug screen cleared. No relocation needed.

Job: Production Supervisor at a precision metal fabrication shop. 50 employees, they want someone who can enforce quality standards while managing the floor. This is a step up for her but I genuinely think she can do it.

Output (what Claude returns): A polished three-paragraph submittal in your house format: opens with her progression from production lead to quality inspector as evidence she bridges floor management with quality systems, links her ISO 9001 auditor cert to the client's precision environment, closes with availability and the observation that her motivation (looming layoff) makes her timeline especially strong. Your rec to move forward is framed with confidence.

Time saved: Writing that submittal from scratch typically takes 20–25 minutes. With the Project, it takes under 3 minutes — copy screen notes, paste, review, send.

What to Do When It Breaks

• Output doesn't follow your submittal structure → Check that your system instructions explicitly describe paragraph order. Add "Do not deviate from this three-paragraph structure" if needed.
• Claude asks too many clarifying questions → This is actually desirable when screen notes are thin, but if it happens on complete notes, add "Only ask for clarification if a required field (availability, compensation, target role) is missing."
• Knowledge documents aren't being used → Large documents sometimes get deprioritized. Break them into shorter, clearly labeled sections. Add "Refer to the Submittal Examples document to calibrate tone and length" in your system instructions.
• Project behaves like a normal chat session → Make sure you opened a chat from inside the Project (you should see the Project name in the top-left of the chat). If you opened a new chat from the main sidebar, it won't have the Project context.
• Output sounds wrong for your market → Add 2–3 sentences to your system instructions describing your market's culture. "My clients are no-frills manufacturing and logistics operations. They value practical specifics over polished corporate language."

Variations

• Simpler version: If you don't want to upload documents yet, start with just the system instructions. Even without knowledge documents, a detailed system prompt produces significantly better outputs than a blank chat.
• Extended version: Add a document with your top 10 clients' specific preferences ("Client X always wants comp on page one," "Client Y prefers bullet-point submittals over paragraphs"). Claude will start calibrating each submittal to the receiving client automatically.

What to Do Next

• This week: Run your next 5 submittals through the Project. Compare the output quality to your manual drafts. Refine the system instructions based on what's off.
• This month: Add a second knowledge document with your best outreach messages. Use the Project for all your writing tasks — submittals, JDs, client emails, interview coaching docs. By the end of the month, you'll have a Claude that sounds more like you than generic AI.
• Advanced: Export your Project's best outputs periodically and add the strongest examples back into your Knowledge documents. The system improves as you use it.

Advanced guide for staffing recruiter professionals. These techniques use more sophisticated AI features that may require paid subscriptions.