- Her AI Drop
- Posts
- Agentic Coding is AI’s Main Character, Here’s How to Start 🤖💻
Agentic Coding is AI’s Main Character, Here’s How to Start 🤖💻
Fall break feels + 10 Claude Code tips to get your AI dev team up and running. Workshop coming soon, but start here.
The Gold standard for AI news
AI keeps coming up at work, but you still don't get it?
That's exactly why 1M+ professionals working at Google, Meta, and OpenAI read Superhuman AI daily.
Here's what you get:
Daily AI news that matters for your career - Filtered from 1000s of sources so you know what affects your industry.
Step-by-step tutorials you can use immediately - Real prompts and workflows that solve actual business problems.
New AI tools tested and reviewed - We try everything to deliver tools that drive real results.
All in just 3 minutes a day
This Week's Drop 💧
Fall break energy is real… cozy socks, fewer Slack pings, and Claude Code agents quietly building apps while we chase our kids around.
We’ve heard from so many of you that you’re curious about Claude Code (hi, fellow power users 👋) and are excited about a Claude Code workshop. Good news: we’re working on it! While we line up the workshop and decode the nerdy bits, we put together a list of 10 Claude Code tips to help you get started.
Why it matters: Agentic coding, where AI acts like a dev team you can direct, is the number one use case for AI right now. If you’re looking for one place to upskill in AI, this is our top recommendation. Even if you don’t code, learning how to work with AI like a product manager or tech lead will future-proof your workflow.
Whether you’re hands-on with code or just Claude-curious, these are the moves that make using AI for dev work feel way more intuitive, and dare we say, fun.
Let’s get into it 👇
✨ Was this forwarded to you? Join the party and subscribe here.
Claude Code Tips ⚡
1. If you’re a visual person: run Claude Code in an Integrated Development Envrionment (IDE)
Claude Code’s default interface is the terminal, fine if you love command lines, but a bit abstract if you crave visual cues.
What to do: Download an IDE (like Visual Studio, Cursor, or Windsurf) and integrate Claude Code so you can see what files are being edited, easily switch between different coding sessions, and highlight just the part of the code you want Claude to work on (this acts like your context‑window).
Bonus tip: You can make each session correspond to a branch or feature area (so you’re visually segmenting work) and use the editor’s built‑in diff/compare view to see what Claude changed.
2. Create a context.md
file to outline the project
Think of this as your “what we’re building & how we roll” document. Create a Markdown file (e.g., context.md
) at the root of your project. In it, outline the high‑level project requirements, constraints, style guidelines, team roles, etc. You can even ask Claude to generate a first draft based on your high‑level bullet points.
What’s the difference between .md
and .txt
?
.txt
is plain‑text, no formatting, just raw text..md
(Markdown) supports simple formatting (headers, bullet lists, code blocks, links). That makes it easy to read/edit and visually scan. Because it’s mostly text (no code), even non‑coders on your team can open/edit it.
Why it matters: context is everything for Claude Code, the better you define the project upfront, the more accurate (and less surprising) its output.
Mini‑hack: Add sections like: “Project vision”, “Key features (MVP)”, “What won’t be included”, “Tech constraints”, “Style & naming conventions”, “Git branching strategy”. Then ask Claude: “Please refer to context.md
before making any changes.”
3. Always start each section by asking Claude to refer to the context.md
file
At the beginning of a session open VS/Claude Code and prompt: “Please read context.md
and keep its contents in mind as you work.”
Why it matters: Starting fresh reminds Claude of the “big picture” before diving into details, this reduces drift, mis‑interpretation, and weird tangents.
4. Always double‑check its work… even if you don’t know how to code
Claude Code is powerful, but it’s not omniscient. After Claude makes changes, ask it:
“Why did you do this change?”
“Which file/line is this function implemented?”
It will walk you through it. Over time you’ll pick up patterns (even if you’re not a full‑on coder).
Why it matters: Claude Code is like a very smart assistant who sometimes forgets what just happened. It can “drift” from your original instructions or act like it missed a step entirely. That’s why it’s key to keep checking its logic and asking it to explain itself.
5. Create “agent roles” that mimic SDLC team roles
Here’s where it gets fun: you’re not just using Claude, you’re organizing a mini‑team of agents. Define agents like:
Product Manager
Frontend Developer
Backend Developer
QA (Quality Assurance) Engineer
DevOps Engineer
You can even add roles like “UX Designer”, “Data Engineer”, “Accessibility Specialist”.
Why it matters: This helps you frame prompts more precisely. Example: “Backend Developer agent: implement the API endpoint for user login per spec.” Your “QA agent” could then run tests. It’s a workflow separation that scales.
Mini‑hack: In your orchestration (see tip #6 in link below), label each agent and build hand‑offs: e.g., after “Frontend Developer” finishes UI, the “QA agent” checks browser compatibility, then “Security agent” reviews auth flows. That way it’s clear who did what.
Her AI Vault 🗂️
Your go-to stash of top resources we’ve created so you never have to dig through old emails to find that one gem.
📘 5 Ways To Get Started With AI At Work: Quick-start guide to delegate the “ugh” tasks and focus on what actually matters.
🔐 AI Privacy Guide: What your AI tools really collect and how to lock down your settings like a pro.
🔍 Her AI Glossary: 40+ essential AI terms, broken down in plain English.
🧠 AI Model Cheat Sheet: Claude, ChatGPT, Gemini... we decoded who does what best, so you can stop guessing and start impressing.
🛠️ Build-Your-Own Productivity Tool: A one-prompt web app for tasks, timers, and focus that is custom-built by Claude and copy-pasted by you.
Before You Go... 💭
We started Her AI Drop with one goal: to make AI less intimidating and way more useful for women, whether you're a founder, freelancer, side hustler, or climbing the corporate ladder. Because this tech shouldn’t just be for the “move fast and break things” crowd. It should help you move smarter, save time at work and home, and yes, make more money.
If something in this drop made your life easier, your inbox lighter, or your brain say “oooh,” let us know. And if something didn’t land? We want to hear that too. Requests, ideas, spicy feedback? Questions about AI we should address? We’re all ears.
💌 Email us anytime at [email protected]
📣 Know someone who should be reading this? Forward it their way. Let’s get more women using AI with confidence, clarity, and zero overwhelm.
✨ PS: Was this forwarded to you? Join the party and subscribe here.
