Dru

C# Minded | EOS 80D | #JokowiAhok #99 | ManUtd

[Dru @drury_yl]

Aseeek!! NoAhok, NoCry

[Dru @drury_yl]

Elsasa Business Solutions | Sistem Operasional & Digitalisasi Bisnis

https://t.co/rqsJVJCfwt

[Ai With Piyas @piyascode9]

GOODBYE $500,000 McKinsey consultants forever.

Claude just replaced 6 weeks of strategy analysis into 8 minutes completely free.

Here are 12 prompts to go from completely clueless to completely boardroom-ready in every business decision: 👇

Top designers are already using this.
Bookmark this thread 🔖

[Charly Wargnier @DataChaz]

This guy literally shows you how to master 97% of Codex in UNDER AN HOUR 🤯

Nate just published a killer article + a full 1-hour video detailing his exact workflow, zero skipped steps!

Truly one of the most generous builders out there.

Link to the YT video in 🧵↓

[Charly Wargnier @DataChaz]

this guy literally breaks down the exact Claude + Obsidian playbook to build your own AI employee in a single afternoon 🤯

[Cultura Literal @culturaliteral1]

Encuentren a esta persona y denle un aumento por favor.

[darkzodchi @zodchiii]

Two Anthropic engineers, who built Claude just explained why you use less than 10% of actual Claude abilities.

This 24-minute talk will change how you use Claude Code forever.

Watch it, then read the breakdown below👇

[Khairallah AL-Awady @eng_khairallah1]

🚨 Anthropic's own team just showed how to actually use Claude Code properly.

30 minutes. free. the person who created Claude Code.

watch the workshop. bookmark it.

worth more than every $500 course you almost bought.

you've been using Claude without knowing 40 of its commands.

Then read the guide below.

[Avid @Av1dlive]

In 14 minutes, this Anthropic engineer who wrote "Building Effective Agents" will

teach you more about building them right than most developers figure out on their own

in months.

Bookmark this for the weekend. Then read the builder's guide below.

[Allen Braden @allen_explains]

This 2-hour Stanford lecture breaks down how models like ChatGPT and Claude are actually built, clearer than what many people in top AI roles ever get exposed to.

Save this and set aside two hours today. It might end up being the most valuable thing you learn all week.

[Troy @troyaitken_]

I run a $110K/month agency with 6 AI employees.

They have names. Personalities. Jobs.

One writes content. One monitors infrastructure. One runs campaigns.

Here's the full setup:

Most people use AI like a search engine. I use it like a staff.

The difference: context files that make each AI know its job, its boundaries, and me.

USER.md — Who You Are

Teaches AI everything about you:
→ Name, location, timezone
→ Your business and goals
→ Working patterns and communication style

The AI can't serve you if it doesn't know you.

SOUL.md — Personality & Principles

The AI's operating system:
→ Core truths ("Be resourceful before asking")
→ Communication style and banned phrases
→ Boundaries and business context

This turns a generic assistant into YOUR assistant.

IDENTITY.md — Who the AI Is

Give it an identity:
→ Name (mine is Jarvis)
→ Role (chief of staff, content writer, etc.)
→ Vibe and operating principle

An AI with identity has consistency.

AGENTS.md — The Operating Manual

The longest and most important file:
→ Startup routine (what to read first)
→ Memory system (where to log, what to remember)
→ Safety rules and learned mistakes

MEMORY.md — Long-Term Memory

Persists across sessions:
→ Discovered preferences
→ Business learnings
→ Key decisions made

Without this, you restart from zero every conversation.

TOOLS.md — Integration Notes

Your AI's reference manual:
→ API endpoints and workflows
→ Team contacts
→ What works and what breaks

Skills — Specialized Instructions

Auto-trigger based on keywords:
→ Content generation
→ Sales follow-ups
→ Lead enrichment
→ Customer onboarding

The Agent Squad

I don't have one AI. I have six:
→ Jarvis — Chief of Staff
→ Loki — Content (8am + 3pm daily)
→ Ivan — Infrastructure (20K email accounts)
→ Hades — GTM campaigns
→ Scrapy — Data extraction
→ Trigify — LinkedIn scraping

Each has its own context, memory, and job.

How They Work

8am — Loki writes 5 tweet drafts
9am — Posts to Slack
10am — I approve 2. Done.

No prompting. It runs on a schedule.

Safety

My AI once bought 164 domains without asking. $1,640 gone.

Now I have:
→ Trusted user verification
→ Financial action gates
→ Prompt injection defense
→ Regressions (mistakes become rules)

Proactive Behaviors

The AI doesn't wait:
→ Cron jobs for scheduled tasks
→ Heartbeats for check-ins

This is the difference between a tool and an employee.

The Stack:
→ OpenClaw (open source orchestration)
→ Context files
→ Skills
→ Agent squad
→ Tool integrations
→ Cron + heartbeats

Everyone's sharing AI setup guides.

That's a good start.

This is what happens when you go 10x further.

Not a chatbot. A system that runs while you sleep.

Like + comment "setup" and I'll DM you the full template.

[Shraddha Bharuka @BharukaShraddha]

Most people treat CLAUDE.md like a prompt file.

That’s the mistake.

If you want Claude Code to feel like a senior engineer living inside your repo, your project needs structure.

Claude needs 4 things at all times:

• the why → what the system does
• the map → where things live
• the rules → what’s allowed / not allowed
• the workflows → how work gets done

I call this:

The Anatomy of a Claude Code Project 👇

━━━━━━━━━━━━━━━

1️⃣ CLAUDE.md = Repo Memory (keep it short)

This is the north star file.

Not a knowledge dump. Just:

• Purpose (WHY)
• Repo map (WHAT)
• Rules + commands (HOW)

If it gets too long, the model starts missing important context.

━━━━━━━━━━━━━━━

2️⃣ .claude/skills/ = Reusable Expert Modes

Stop rewriting instructions.

Turn common workflows into skills:

• code review checklist
• refactor playbook
• release procedure
• debugging flow

Result:
Consistency across sessions and teammates.

━━━━━━━━━━━━━━━

3️⃣ .claude/hooks/ = Guardrails

Models forget.

Hooks don’t.

Use them for things that must be deterministic:

• run formatter after edits
• run tests on core changes
• block unsafe directories (auth, billing, migrations)

━━━━━━━━━━━━━━━

4️⃣ docs/ = Progressive Context

Don’t bloat prompts.

Claude just needs to know where truth lives:

• architecture overview
• ADRs (engineering decisions)
• operational runbooks

━━━━━━━━━━━━━━━

5️⃣ Local CLAUDE.md for risky modules

Put small files near sharp edges:

src/auth/CLAUDE.md
src/persistence/CLAUDE.md
infra/CLAUDE.md

Now Claude sees the gotchas exactly when it works there.

━━━━━━━━━━━━━━━

Prompting is temporary.

Structure is permanent.

When your repo is organized this way, Claude stops behaving like a chatbot…

…and starts acting like a project-native engineer.

[Om Patel @om_patel5]

THE MOST POWERFUL VIBE CODING PROMPT EVER:

[Dru @drury_yl]

@TifeRMFC Bekham, Owen, Di Maria, Heinze, Varane... That comes in mind in 30 second

[Dru @drury_yl]

@_onlyscott Casemiro... easy

[Dru @drury_yl]

My #programming activity last year via @WakaTime https://t.co/tSysEyrK2P

[Dru @drury_yl]

@_onlyscott Francesco Zola

[Dru @drury_yl]

@Utdcen Alan Smith

[Call Me : Bur (akun pemberian Alm @_sendirian__) @ItsMe_RBH]

Penjelasan yang sangat jernih dan tidak memihak selain kebenaran dari Pak @alvinlie21.
Tetapi tetap banyak yg mendahulukan kebencian dalam menilai. Komentar2 di tayangannya bikin miris.. 😥

https://t.co/hH2YS9qXTy

[Dru @drury_yl]

@elonmuskTN 47