New in Claude Cowork: teach Claude a skill.
Record your screen while you do a task, talk through it as you go, and Claude turns it into a skill it can run again. Find it under Record a skill in the + menu of the Claude desktop app.
Available on Pro, Max, and Team plans.
✅ Claude Code
✅ Claude Cowork
✅ Claude Design
✅ Claude Finance
✅ Claude Science
✅ Claude Teacher
⬜ Claude HR
⬜ Claude Analytics
⬜ Claude Marketing
⬜ Claude Sales
⬜ Claude Legal
⬜ Claude R&D
⬜ Claude Procurement
⬜ Claude Accounting
⬜ Claude Engineering
One of the new, buzzy jobs in Silicon Valley is the AI Forward Deployed Engineer (FDE), an engineer who is embedded within a client organization to help customize solutions, such as building and tuning agentic workflows that suit the client’s particular needs. I’ve heard from people who are wondering anew about the FDE career path since OpenAI and Anthropic started building new teams to place FDEs within client organizations.
The rise of FDEs for AI workloads is one way AI is creating new jobs (and why the jobpolcalypse narrative of upcoming job market collapse is false -- there will be many AI and non-AI jobs). However, I believe there will be far more AI Engineer jobs than FDEs, as I explain below.
The FDE role was pioneered about two decades ago by Palantir, which sent engineers to government locations to work on secure, air-gapped networks. In addition to having good technical skills, FDEs need communication skills and sometimes business skills. For example, they may need to speak with clients to understand their needs, formulate a strategy to prioritize projects, explain complex technology, and respectfully push back if a client asks for something unrealistic. They’re enjoying a resurgence because of the amount of work involved in taking an off-the-shelf LLM and building it into a custom agentic workflow that fits particular business needs.
However, I believe the number of AI Engineer jobs will be far larger. A company might accept a few FDEs to be embedded within its organization. But most companies will want far more of their own employees working on their projects. While my organizations do hire FDEs, we hire far more AI Engineers! Also, a common client concern is that it is hard to find vendor-neutral FDEs — they are, after all, there to deeply integrate a particular vendor’s product into a company. In this moment when it’s hard to predict which AI service will be the best one in a year’s time, optionality (the ability to pick whatever vendor turns out to fit best in the future) is very valuable. In contrast, letting FDEs tightly bind a company’s processes significantly reduces optionality.
Right now, I see surging demand for AI Engineers who can build software applications using AI software components (like LLM prompting, agentic frameworks, evals, etc.) and effectively use AI coding agents (like Claude Code, Codex, Antigravity CLI, and OpenCode). As the AI Engineer role matures, I expect it to fragment into more specialized roles, like the generic Software Engineer role from decades ago fragmented into frontend, backend, mobile, data engineering, devops, and so on.
What will be the future, specialized AI engineering roles? I don’t know. Perhaps there will be AI FDEs, LLMOps Engineers, Evals Engineers, AI Data Engineers, Harness Engineers, and other roles we don’t have names for yet. But for now, I see a lot of AI engineers who are generalists create a lot of value. Skilled AI Engineers are in very high demand! As our field continues to mature over the coming decade, I look forward to new specializations within AI Engineering that create even more job opportunities.
[Original text: The Batch newsletter]
We must, then, avoid the “Babel syndrome,” namely the idolatry of profit that sacrifices the weak, a uniformity that neutralizes differences, and the pretense that a single language — even a digital one — can translate everything, including the mystery of the person, into data and performance. This is the risk of dehumanization: building a future that excludes God and reduces the other to a means.
Anthropic just showed a 24-minute workshop on how to actually prompt Claude.
Taught by the people who built it.
Free. No signup. No paywall.
I've watched $300 courses that don't cover what they teach in the first 8 minutes.
SOMEONE JUST KILLED THE REAL ESTATE INDUSTRY
A guy scanned an entire house with his phone. Uploaded it.
Now anyone on Earth can walk through it in a browser tab. No app. No VR. No agent. No appointment.
Click → you’re inside. Every room. Every angle. Every shadow. Photoreal.
The numbers are insane:
- Agent fee on a $500k home: $15,000
- Cost to make this scan: ~$200
- Time to “tour” 50 houses: one evening
- File size: smaller than a TikTok
The science is wild too:
It’s called 3D Gaussian Splatting instead of polygons (how games render), it uses millions of tiny glowing “splats” of color and depth.
AI reconstructs reality from your photos. The result loads on a phone and looks like you’re THERE.
The grift opportunity is even wilder:
Freelancers are already charging $300–$800 per scan for realtors, Airbnbs, venues, car dealers, museums.
One person + one phone + one weekend = a business.
Open source. Built on PlayCanvas.
Free GitHub: https://t.co/ew6Ql8Ad6u
Did you know Korea sells “one-a-day” banana packs?
Instead of every banana ripening at once, each one is at a different stage.
One is ready today.
The next one is ready tomorrow.
The last one is still spiritually in college, “experimenting.”
Simple. Genius. Solves the entire banana problem.
What do you think?
Would you prefer your bananas this way?
Patrick Winston taught engineering at MIT for 50 years.
This is his last lecture.
He died 5 months after recording it.
It was his final gift to the world.
1000s of the greatest minds passed through his classroom and went on to engineer the world.
He has some wisdom…
How to turn Claude Cowork into your ultimate AI coworker in 5 minutes 🔥
🔹 Step 1: Get the App. Download the desktop app (macOS/Windows) and get on the Pro plan. Don't overthink it, takes 2 mins.
🔹 Step 2: Optimize the Engine. Open the Cowork tab, select Opus 4.7, and turn ON Extended Thinking. Wrong model = bad output.
🔹 Step 3: Build your Workspace Hub. Create one master folder called "Claude-Work". Inside, create 4 specific subfolders: ABOUT ME, PROJECTS, TEMPLATES, and OUTPUTS.
🔹 Step 4: Create your Context Files. Inside your 'ABOUT ME' folder, add 3 markdown files: about-me.md (your day-to-day), my-voice.md (your tone/samples), and my-rules.md (strict boundaries & planning).
🔹 Step 5: Lock in Global Instructions. Go to Settings → Cowork. Tell Claude your exact role and command it to always read your files and ask questions before executing.
🔹 Step 6: Stop Prompting, Start Clicking. Paste your task and force Claude to generate a plan with clickable execution buttons. Let it force you to be clear.
🔹 Step 7: Install Plugins. Browse and install plugins to unlock powerful slash commands for specific workflows (Marketing, Data, Legal).
🔹 Step 8: Connect Your Ecosystem. Hook up Google Drive, Slack, Notion, and Figma directly. Claude will now read your tools mid-conversation—no more copy-pasting!
(infographic credit: @gudanglifehack)
Claude can now meal prep your entire week and hit your exact nutrition goals like a $200/hour registered dietitian from the Mayo Clinic. For free.
Here are 12 prompts that plan meals, calculate macros, and save you $500/month on groceries:
(Save this before it disappears)