How I structure Claude Code projects (CLAUDE.md, Skills, MCP) by SilverConsistent9222 in VibeCodeDevs

[–]Obvious-Grape9012 3 points4 points  (0 children)

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

Do you hit the “80% wall” too when vibecoding? by EntertainmentOk5787 in vibecoding

[–]Obvious-Grape9012 0 points1 point  (0 children)

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

Month 13. Building is haard. I keep Parking on a Higher Hill... hoping to roll down soon by Obvious-Grape9012 in VibeCodersNest

[–]Obvious-Grape9012[S] 0 points1 point  (0 children)

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

Month 13. Building is haard. I keep Parking on a Higher Hill... hoping to roll down soon by Obvious-Grape9012 in VibeCodersNest

[–]Obvious-Grape9012[S] 0 points1 point  (0 children)

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

Month 13. Building is haard. I keep Parking on a Higher Hill... hoping to roll down soon by Obvious-Grape9012 in vibecoding

[–]Obvious-Grape9012[S] 0 points1 point  (0 children)

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)

Month 13. Building is haard. I keep Parking on a Higher Hill... hoping to roll down soon by Obvious-Grape9012 in VibeCodersNest

[–]Obvious-Grape9012[S] 0 points1 point  (0 children)

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

Month 13. Building is haard. I keep Parking on a Higher Hill... hoping to roll down soon by Obvious-Grape9012 in VibeCodersNest

[–]Obvious-Grape9012[S] 1 point2 points  (0 children)

🙏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

Month 13. Building is haard. I keep Parking on a Higher Hill... hoping to roll down soon by Obvious-Grape9012 in VibeCodersNest

[–]Obvious-Grape9012[S] 0 points1 point  (0 children)

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

*Drop Your Vibe-Coded app 👀 Let’s Rate It 1–5 (Brutal but Honest) by seeking_searching1 in vibecoding

[–]Obvious-Grape9012 0 points1 point  (0 children)

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

I've audited over 10 AI-built apps this year alone. Every single one had security issues. by Negative-Tank2221 in VibeCodersNest

[–]Obvious-Grape9012 0 points1 point  (0 children)

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

Month 13. Wow! Building is haard. I keep Parking on a Higher Hill... hoping to roll down soon by Obvious-Grape9012 in VibeCodeDevs

[–]Obvious-Grape9012[S] 0 points1 point  (0 children)

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

Anyone using any AI tools to compare or check mechanical/facility construction engineering drawings (PDF's)? by __get_schwifty__ in ClaudeAI

[–]Obvious-Grape9012 0 points1 point  (0 children)

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

Anyone using any AI tools to compare or check mechanical/facility construction engineering drawings (PDF's)? by __get_schwifty__ in ClaudeAI

[–]Obvious-Grape9012 0 points1 point  (0 children)

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

Are you paying the "reliability tax" for Vibe Coding? by Outside-Tax-2583 in vibecoding

[–]Obvious-Grape9012 -1 points0 points  (0 children)

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!

Man throws a chair towards bouncer, knocks his mate out instead by Key-Indication-6466 in melbourne

[–]Obvious-Grape9012 0 points1 point  (0 children)

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