Tips and tricks

Issue #1: Agent Responses Are Inconsistent

Symptom: The same agent gives different answers to similar prompts.

Solution:

• Review the agent configuration for vague rules
• Add specific examples to the agent’s training
• Use “Always” and “Never” statements for critical rules

Example Fix:

❌ Bad Rule: “Write engaging hooks”

✅ Good Rule: “Always start hooks with a question or bold statement. Never use generic openings like ‘In this video…’”

Issue #2: Claude Code Seems Slow

Symptom: Agents take 3–5 minutes for simple tasks.

Solution:

• Reduce file references (only @mention necessary files)
• Break complex tasks into smaller agent steps
• Check internet connection (Research Agent requires web access)

Issue #3: Agents Ignore My Instructions

Symptom: Agent output does not match your requirements.

Solution:

• Add instructions to permanent memory (/init file)
• Include concrete examples in prompts
• Use numbered lists for multi-step requirements

Issue #4: Can’t Find Previous Work

Symptom: Claude Code cannot locate files it previously created.

Solution:

• Always specify save location: Save to @filename.md
• Use consistent naming conventions
• Create a dedicated /outputs folder for agent-generated content

Issue #5: Running Out of Context

Symptom: Long projects cause quality degradation due to context limits.

Solution:

• Create new agents for new project phases
• Summarize previous work into new /init files
• Use the Research Agent to condense large files

Pro Tip: Create a “Master Index” agent that tracks all project files and can quickly locate anything across multiple workflows.