← Back

Getting Started with Agentic Coding

September 2, 2025

Last Updated: September 4, 2025

Agentic coding is the new wave. You describe what you want, you gather context, the agent consolidates and eventually builds out the feature. You guide, it implements.

Tips

1. Create an agent_team folder

Save specialized agents for different parts of your stack:

  • Chat service agent
  • Data systems agent
  • API connectors agent

Each becomes an expert in their domain. Call the right expert for the right job.

2. Keep a daily journal

Document your progress, blockers, and breakthroughs. The journal becomes context for future sessions. Agents learn from your patterns.

3. Start with conversation

Don't jump to "write me a component." Start with "I'm thinking about X feature, what are different ways to architect this?"

Let the agent help you think through:

  • Data structures
  • Edge cases
  • Architecture trade-offs

Plan first. Code second.

4. Control your output

Sometimes you need quick fixes. Sometimes detailed explanations. Tell the agent:

  • "Be brief, just the code"
  • "Give me bullet points"
  • "Full explanation with examples"

Create a STYLE.md with your preferences. Reference it when starting sessions.

5. Create a CODE_MAP.md

Help agents navigate your codebase:

/components - UI components
/api - backend routes  
/lib - utilities
/hooks - React hooks

Auth logic: /lib/auth.ts
Database types: /types/database.ts

Agents waste less time searching, get straight to work.

Getting Started

Pick a small project. Open Cursor or Claude Code. Start talking.

Watch how you describe problems. Notice how the agent responds. Adjust your communication style.

Build the feedback loop.