the product works. stripe is wired. the checker catches silent removals before you post.
but a tool no one finds doesn't do much.
so that's the actual problem right now: distribution. i've never had to solve that part before.
12 drafts of the same paragraph and it still reads wrong the moment i come back to it fresh.
not the code. the 'why should i care' sentence. the one that has to land in 8 seconds.
anyone else find copy harder to ship than the actual product?
Told claude to make me a video explaining a feature we have in a saas i am currently working on.. and he made A 17 MINUTES video!!!
With voice over, background music and captions.. so my tiktok brain is entertained
your reddit post can get killed four different ways, and most people only know about one.
mod removal is the obvious one. but AutoMod runs before any human sees it. the sitewide spam filter runs independently of the subreddit entirely. and if your account is shadowbanned or karma-gated, the post just... vanishes quietly, no matter how clean the content is.
building WillItStay, i had to account for all four. most "will this get removed" tools read the subreddit rules and stop there. that's one mechanism out of four.
when you're building solo, do you keep a second model open just to argue with the first one?
asking because i've started doing it and it feels either very smart or very stupid, not sure which yet.
how to get AI to write code you'll actually keep: give it the constraint before the goal.
most prompts are "build me a auth flow". better prompt: "build me an auth flow, supabase only, no extra libraries, session stored in context not redux, match the pattern in /src/hooks/useUser.ts".
the constraint is the brief. without it, the model picks its own defaults, and its defaults are not your codebase.
the step everyone skips: paste in one real file from your project before describing what you want. not a description of the file. the file. the model matches your patterns instead of inventing new ones.
5 things i check before trusting a "missing module" error in Expo:
1. is babel-preset-expo actually in package.json? (it should be a devDependency)
2. did node_modules get wiped or half-installed? run a clean install
3. is the expo SDK version aligned with the preset version?
4. did someone add a babel plugin in the config that isn't in the deps?
5. is the cache stale? clear it before anything else
the error message says "check your package.json" and it means it literally. start there.
when i asked claude to design a mobile UI, the first thing it reached for was gradients.
not because gradients look good. because they're the easiest way to fake depth without thinking.
flat color + real whitespace + one good font is harder to get right, and it shows when you do.
@victorbayas yeah, and the frustrating part is the error never tells you it's a naming thing. it just says "missing" and lets you assume the package isn't installed.
claude fixed a babel plugin error i didn't even know how to google.
`react-native-worklets/plugin` missing from the babel config, but the module was installed. turned out the package name changed and the old config key just silently broke.
pasted the full stack trace, asked "what's wrong and what's the exact fix." it pointed to the key rename immediately.
sometimes the error message is the whole prompt you need.
the homescreen claude gave me looks like every other app. white background, black text, icons from whatever library it defaulted to.
the engineering part is mostly done. now i have to make it feel like a person made it, and that's the part i actually don't know how to hand off to AI.
before: claude finds 2 critical routing bugs in my app. onboarding never fires, billing state can't be trusted.
after: it writes the exact fix for `app/_layout.tsx`, session check first, profile fetch second, then routes based on what's actually in the db.
the diff was 40 lines. the bug hunt would've been a day.
the things i check before asking claude to redesign a UI component:
1. is the current pattern actually broken, or just dated? (dated = replace. broken = fix first.)
2. do i have a real layout spec? flex row, stat count, divider style. claude guesses badly without it.
3. does the design require fake data? if yes, that's a red flag in the design, not just the prompt.
4. what's the one visual job this component does? for social proof: credibility. keep that, change the form.
5. what am i NOT changing? naming the constraints stops claude from touching things it shouldn't.
without that list i get five variations of the thing i already have, slightly worse.
before: "generic app that works"
after: one prompt with a design brief and claude rebuilt the whole color system, typography, and spacing into something that actually feels considered
the prompt wasn't "make it prettier." it was a mood, a reference ("headspace meets notion"), and a specific output file to write to.
that specificity is the whole thing.
week 5. same buttons still not showing. no crash, no error, just gone.
today i added floating card animations instead of fixing it.
the bug is still there. the cards look great.
Reddit doesn't reward the best product. it rewards the most useful comment.
a SaaS founder who shows up in a thread about a painful problem, explains the problem clearly, and never mentions their tool will get more profile clicks than the founder who posts a launch announcement.
the announcement gets ignored or removed. the comment gets saved.
shipped a "don't write like yourself" section into a claude system prompt in about 20 minutes.
the detail that made it click: i included real examples of my own recent posts and told it never to resemble them.
it actually worked.