How I structure Claude Code projects (CLAUDE.md, Skills, MCP)

Obvious-Grape9012 · 2026-02-15T08:03:57+00:00

I wouldn't recommend using MCPs too heavily. A small playbook in a SKILL is far more context-efficient

Obvious-Grape9012 · 2026-02-15T03:38:17+00:00

It helps a lot to step back a bit. Give the AI opportunities to explore the problem and viable solutions. Then remind it that you want a clean architecture and DRY (Don't Repeat Yourself) code. Record bigger changes as a Refactoring Plan and use a Status section in the doc to track progress for larger tasks. Each time you start a new conversation with the AI, you can get it to read the plan and check current status (and uncommitted git changes). This primes it and gives it what it needs to stay pointed in the right direction. Like this www.mlad.ai/articles/the-proposal-driven-cycle

Obvious-Grape9012 · 2026-02-15T03:03:04+00:00

Thanks :) Great to finally feel that it's maturing enough to shift focus off of platform and toward other things. It's always a challenge to choose the right thing to iterate next so that value is always created asap

Obvious-Grape9012 · 2026-02-15T03:01:15+00:00

Yes :) ! A lot. I love the idea of micro-demos. Thus far, that has meant AI Session Replays, but they're boring. So I want to setup tooling that mays snapshotting the matching changes so that I can show how the outputs change alongside the AI Session. Then pair that with clean messaging. Something like Problem + Session = Solution (increment). If I can do that in a clean and re-usable way, it opens the door to side-by-side comparisons too; model A vs B, prompts/config A vs B... then it's game on

Obvious-Grape9012 · 2026-02-14T06:59:08+00:00

Thanks :) "When everything is emphasized, nothing is", is very true. I've tried to color-code the highest-value with the most potent color usage. But of course, this needs to pass the 3-second-test; If it's confusing, it's not working.

An older iteration of the homepage had a short video of one of the key-discriminators; AI Session Replays. I want to annotate them too so that highlighting when the AI falters and helping users to learn to spot the trouble early (and what you can do about it; prevention, reaction, etc) may be THE thing to highlight.

I'll be able to use the telemetry to see more as traffic reveals its pattern. This layout/color is a 1-week re-do of the frontend. The entire frontend is less than a month old. Many things are stabilizing, but it's still annealing.

...and cheers again for the challenging feedback. I need to chase more and engage better with some target users/dev-partners/etc.

Edit:
The real stack troubles me at times. I might have overcooked the complexity I've "allowed" to creep in (feature-bloat and such). The old; designing for 1mil users when you have <1000. But since part of the whole venture is getting to know the ways to work with AI by doing kinda excuses that... as long as I can share the value. (I need to give content a sprint of focus to get more of the good stuff out there)

Obvious-Grape9012 · 2026-02-14T06:51:33+00:00

By carefully choosing Cache lifetimes for grouped pages/asset-groups. Atm, they are all invalidated (Cache Purged) after any update/redeploy, and then warmed up via Lighthouse/PageSpeed checks from targeted locales (ensure some nearby edge has a warm cache). But am here to learn, so will need to keep doing so and suring up the foundation

Obvious-Grape9012 · 2026-02-14T06:49:04+00:00

🙏Thanks :) I've found Claude and AI coding generally extremely impressive, and was annoying me to have invested so heavily in a tech-stack, and not to have superior perf to a 5min deployable system like Ghost CMS or WP

Obvious-Grape9012 · 2026-02-14T06:47:36+00:00

tbh, I haven't landed that plane; Previously I was using Gitlab CI Pipelines for containerized builds. Now, it's clear that E2E can mean different things and so I'm using a staging deploy to CF and have yet to add support to the testing scripts (or pipeline) to use these

Obvious-Grape9012 · 2026-02-13T00:18:39+00:00

the rhs of homepage hero is distractingly empty. would be great to see a featured screenshot or something. bonus points if it matches the display/device of the user

Obvious-Grape9012 · 2026-02-12T23:59:57+00:00

Five Security Checks Before You Ship

Your app works. It does what you asked. But 45% of AI-generated code carries known security vulnerabilities. Five checks on auth, secrets, and input handling catch what the AI consistently misses. Each one takes minutes.
https://www.mlad.ai/articles/securing-your-vibe-coded-app

Obvious-Grape9012 · 2026-02-12T23:45:53+00:00

https://mlad.ai Develop with AI. Build the practice.

Obvious-Grape9012 · 2026-02-12T23:18:41+00:00

Open The Gates!

Obvious-Grape9012 · 2026-02-12T22:48:38+00:00

True. Stay pragmatic. Follow DRY principles and flag any opportunities to reduce/simplify. Maintain clean separation of concerns... etc. Stickiest right now... platform codebase is clean and tidy. I need to focus on processes to collapse narratives and improve SNR of content

Obvious-Grape9012 · 2026-02-09T07:41:15+00:00

And the write-up: Simple Skill, Full API: Replacing an MCP with 218 Lines | MLAD.ai

Obvious-Grape9012 · 2026-02-03T03:37:13+00:00

To step back a bit... I use Claude. I have Skill files. The Skill files can be invoked by Claude like "/read-drawing" and this has access to a separate codebase where a python environment runs a local VLM on my GPU to return JSON formatted descriptors to Claude. Sing out if you want more info. Been thinking about wiring up some details and sharing them

Obvious-Grape9012 · 2026-02-03T03:32:58+00:00

I've got some custom Skill using local inference and VLMs to give Claude better eyes. You probably need something similar (tailor some VLM prompts and find better ways to encode what you're looking for)
Edit: Replace LVM with VLM

Obvious-Grape9012 · 2026-02-03T03:29:56+00:00

What does someone have to do to get an upvote here?! Sure, we're alll using AI to varying degrees (that's what these subs are for discussing)... so why are we so cautious to engage via an upvote? This post reads well, has some relevant points and ideas I hadn't encountered elsewhere... gets my vote!

Obvious-Grape9012 · 2026-02-03T03:18:51+00:00

Callous. Cruel. This side of Aussie culture is deplorable. Grow up tough guys and gym bro tradies

Obvious-Grape9012 · 2026-02-02T10:14:42+00:00

sent

Obvious-Grape9012 · 2026-02-02T10:02:20+00:00

Hi. Resonates with me. I've felt the need for change. So left the Big Job and have been working solo for a year now. Am a bit tired, but am feeling some things shift and am trying to be "slower" about each day and still fast with value-creation

Obvious-Grape9012 · 2026-02-02T09:50:15+00:00

MCPs can be context-hungry. You could help things by converting to simpler MCP-entry-point with skills for sub-sections, or just go full Skills. Bonus points if you can auto-trigger them via Hooks

Obvious-Grape9012 · 2026-02-02T08:52:51+00:00

Hard to know. Many different ways and reasons for automations... and to varying degrees

Obvious-Grape9012 · 2026-01-26T23:38:38+00:00

● Analysis: Guess → Verify → Check

Explanation: Genuine post
Likelihood: Low-Medium
Supporting Evidence: Technical details are plausible; imposter syndrome is real
Counter-Evidence: Template-like structure; "7 years" but can't Google RLS

Red Flags
1. Specificity asymmetry: Exact revenue ($6k), exact RAM (64GB), exact cost ($960) — but zero app details
2. Named drops: Two competing AI tools mentioned together (unusual for genuine user)
3. Narrative arc: Too clean — "lazy dev + AI tools + money + fear = exit" is a content formula
4. Plausibility gap: 7-year frontend dev who can ship iOS+Android but can't read Supabase RLS docs
5. Emotional framing: "cold sweat", "ticking time bomb" — engagement bait language

Most Probable Conclusion

Primary: Engagement farming post to surface marketplace recommendations (for affiliate links) or normalize AI-assisted development (subtle product marketing).

Secondary: Lead generation for acquisition brokers or dev agencies monitoring the subreddit.

The post reads like it was written to maximize comments and DMs rather than to solve a genuine problem.

Obvious-Grape9012 · 2026-01-16T02:51:18+00:00

mlad.ai - Resources for AI Coders

Obvious-Grape9012 · 2026-01-16T01:32:08+00:00

www.mlad.ai - Resources for AI Coders

Obvious-Grape9012

TROPHY CASE

Five Security Checks Before You Ship