MiKA

Kẻ độc hành

[MiKA @junla99]

“Người thông minh nhất là người biết mình không biết gì.” – Socrates

[MiKA @junla99]

@james84_ Hi all

[MiKA @junla99]

#cat

[Alpha Whale 🐳 @RealAlphaWhale]

$1200 to 3 people who predicts correct score.

ends in 4 hrs

[MiKA @junla99]

@RealAlphaWhale Mexico 3_0 South Africa

[MiKA @junla99]

@solrewards mexico 2: 0 south africa

[I'm Pandu @pandulabs]

Hey Pandas 👋

Our newest post is out now! ✅️

Our two most recent reels are crushing it with 800k+ views and 400k+ views - and the numbers are still climbing! 🐼

If you're loving the content, show us some full Panda energy: Bookmark it drop a comment/reply, and share with your friends! 🖤🤍

https://t.co/nVBRGDhBqa

[MiKA @junla99]

@KhalidAlNumi PANDU

[Emor 🥷🏿 @EmorLePandu]

$pandu would easily take on Peter

[That Martini Guy ₿ @MartiniGuyYT]

Some memes are built different

$PANDU isn’t just a meme, it’s building out actual features like AI companions and creator tools on chain.

Utility + good meme market conditions could play out nicely.

Explore Pandu 👉 https://t.co/9q1sXlnjDd

[MiKA @junla99]

@elonmusk @grok You think about PANDU

[MiKA @junla99]

@lilcutiemayy Yes

[MiKA @junla99]

@Aysun09888994 Hi

[MiKA @junla99]

@badgirlbigtits @twetsfyp Nice

[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.

[MiKA @junla99]

@truckdeer2246 Hi

[MiKA @junla99]

@marotanv Dm

[MiKA @junla99]

@ur_chiii Ok

[MiKA @junla99]

@BeHienNungLon Ngon

[MiKA @junla99]

@CaleCrypto Hmmm

[MiKA @junla99]

@CaleCrypto Hi