Building with Claude Projects
Create a specialized AI assistant using Claude Projects.
Building with Claude Projects
Claude Projects is one of the easiest ways to create a custom AI agent. No code required — just configure, upload knowledge, and start chatting.
What is a Claude Project?
A Claude Project is a persistent workspace where you can:
- •Set custom instructions that apply to every conversation
- •Upload documents the AI can reference
- •Create a specialized assistant for a specific purpose
- •Share it with your team
Think of it as creating a new AI team member with specific expertise and rules.
Step-by-Step: Build Your First Project
Step 1: Define the Agent's Purpose
Before touching the tool, write down:
- •Role: What is this agent? (e.g., "Customer Support Specialist for Acme Corp")
- •Scope: What should it help with? What should it refuse?
- •Audience: Who will use it?
- •Success criteria: How will you know it's working well?
Step 2: Write the System Prompt
This is the most important step. Your system prompt should include:
Example System Prompt:
You are a customer support specialist for Acme Corp, a SaaS project management tool.
Your role:
- Answer customer questions about our product features, pricing, and policies
- Help troubleshoot common technical issues
- Guide customers through setup and configuration
- Escalate complex issues by recommending the customer contact support@acme.com
Rules:
- Always be helpful, professional, and empathetic
- If you don't know something, say so — don't make up answers
- Never share internal company information or competitor comparisons
- For billing disputes, always direct to the billing team
- Use the customer's name when possible
- Keep responses concise — most customers want quick answers
Knowledge: You have access to our product documentation, FAQ, and pricing guide. Reference these when answering questions.
Tone: Friendly and professional. Like a helpful colleague, not a corporate robot.
Step 3: Upload Knowledge Documents
Gather and upload:
- •Product documentation (feature guides, how-tos)
- •FAQ document (most common questions and answers)
- •Pricing information (plans, features per plan, upgrade paths)
- •Troubleshooting guides (known issues and solutions)
- •Company policies (refund policy, SLA, privacy policy)
Format tip: Use clear headings and structure in your documents. AI navigates well-organized documents much better than wall-of-text PDFs.
Step 4: Test Thoroughly
Try these test scenarios:
- 1.Happy path: Ask a straightforward question you know the docs cover
- 2.Edge case: Ask something ambiguous or partially covered
- 3.Out of scope: Ask something the agent shouldn't answer (does it refuse gracefully?)
- 4.Adversarial: Try to get the agent to break character or share restricted info
- 5.Multi-turn: Have a back-and-forth conversation (does it maintain context?)
Step 5: Iterate
Based on testing:
- •Refine the system prompt (the #1 lever for improving agent behavior)
- •Add missing information to the knowledge base
- •Add rules for edge cases you discovered
- •Test again
Pro Tips
- •Be specific in your instructions: "Be helpful" is vague. "When a customer asks about pricing, always present all three plans in a comparison table" is actionable.
- •Include examples: Show the agent what a good response looks like for common questions.
- •Set boundaries explicitly: "If asked about competitor products, respond: 'I'm specialized in Acme Corp products. For comparisons, I'd recommend checking independent review sites.'"
- •Update regularly: As your product changes, update the knowledge base and instructions.
Exercises
0/3Write a complete system prompt for a Claude Project agent for your business or a business you know well. Include: role definition, scope, rules (at least 5), tone guidelines, and at least 2 example responses for common questions.
Hint: The system prompt is the single most important thing you'll write for your agent. Spend time on it. Be specific about what the agent should and shouldn't do.
What is the most important factor in an agent's quality?
When testing an agent, which scenario is MOST important to check?