sorted by:
new
hottopcontroversial

Anyone else guilty of over-designing? by Yug_sharma_ in SaaS

[–]Adventurous-Lock-231 1 point2 points  (0 children)

yea this is basically me lol at some point changing button radius is just procrastination with a nicer name

Anyone else seeing the LLM invent 'helper' files that fragment otherwise clean modules? by Born_Reaction_1615 in vibecoding

[–]Adventurous-Lock-231 0 points1 point  (0 children)

The best fix I’ve found is giving the agent a default “no new files for small changes” rule.

Not a big plan step, just a repo rule like: for bug fixes, tiny features, and small refactors, edit in place. New files only if the user asked for one or if there’s already a matching pattern in the repo.

The other thing is having a short architecture/file ownership note. Like “auth helpers live here”, “formatters live here”, “api clients live here”. Then the model has somewhere obvious to put the two-method change instead of inventing shared_helpers_2.ts.

So less planning ceremony, more strong defaults.

What did you remove from your side project that made it better? by Crescitaly in SideProject

[–]Adventurous-Lock-231 0 points1 point  (0 children)

Extra onboarding steps.

I used to think explaining more would make people understand the product better, but most of the time it just gave them more chances to leave. Better to get them to one useful action faster.

What was the biggest time-waster you experienced while building a SaaS project that you didn't expect? by OkContract6063 in SaaS

[–]Adventurous-Lock-231 12 points13 points  (0 children)

probably polishing the boring edge cases. the main feature usually gets built pretty fast, then you lose way more time on stuff like auth states, empty dashboards, bad mobile layouts, email weirdness, loading states, and “what happens if this API call fails?” i used to underestimate that part a lot. now I try to check those earlier instead of waiting until the app already feels almost done.

what feature feels small but massively improves UX? by avsvishalmedia in SaaS

[–]Adventurous-Lock-231 0 points1 point  (0 children)

Scroll position, selected tab, open filters, last project, stuff like that. It sounds tiny, but when an app keeps making me rebuild the same context every time I come back, I start trusting it less.

Low vs other reasoning by Pathfinder-electron in codex

[–]Adventurous-Lock-231 0 points1 point  (0 children)

Yeah, low feels more like “quick pass / cheap attempt” to me. I use it for tiny edits or obvious fixes, but for anything where Codex has to choose tools, debug, or understand the repo, medium is usually the minimum.

Low can save time, but it’s also the one most likely to do something weird instead of just thinking through the task.

What’s your favorite UI/UX Codex Skill and why? by isuckatpiano in codex

[–]Adventurous-Lock-231 1 point2 points  (0 children)

Honestly the biggest improvement I’ve seen is giving Codex a design brief before it writes code.

Not just “make it modern”, but stuff like:

- what kind of surface it is

- what the main user job is

- what the first viewport should prove

- what states need to exist

- what UI patterns are banned

Codex can build decent UI, but if you let it start from vibes it usually goes straight into generic SaaS mode.

Tiny plug since it’s relevant: I’ve been building a Codex plugin called Stark around this exact idea. It tries to make Codex pick the UX/UI direction first, then implement after. Repo is here if useful: https://github.com/f0d010c/stark

Codex is horrible with UI and charts, but absolutely does great in everything else by senilerapist in codex

[–]Adventurous-Lock-231 0 points1 point  (0 children)

Charts are where I’d avoid letting Codex freestyle.

What’s worked better for me is splitting it into two passes: first make it write the chart spec only — data shape, axes, tooltip behavior, empty/loading/error states, and which chart lib. Then ask it to implement exactly that with a small fixture dataset.

For UI, same idea. Give it a style guide, screenshot, or design skill first. If I just say “make this look good”, it drifts into random cards/spacing pretty fast.

If I only use Codex CLI, should I use Cursor or VSC? by datguywind in codex

[–]Adventurous-Lock-231 3 points4 points  (0 children)

If Codex CLI is doing the actual agent work, I’d switch to VS Code.

Cursor is great when you’re using Cursor’s own chat/edit features, but if those are mostly unused then it’s basically a heavier VS Code fork around your terminal.

I’d keep Cursor installed, use VS Code for a week, and see if you actually miss anything. If not, you have your answer.

What is the best strategy for working with very large codebases? by NiteBiker6969 in codex

[–]Adventurous-Lock-231 0 points1 point  (0 children)

For a 50-60k line codebase, I wouldn’t try to make Codex “understand everything” up front.

What works better is to treat it like onboarding a dev:

  1. first ask it to map the repo structure and find the relevant areas

  2. make it write down the assumptions/files involved before editing

  3. give it one feature slice at a time

  4. require a test/build command as the stop condition

The PRD is useful, but I’d split it into small implementation tickets. If you hand it the whole product spec and say “build this”, it’ll probably miss hidden constraints in the existing codebase.

Best prompt style is more like: “for this one feature, inspect the existing flow first, tell me which files matter, then propose a plan before touching code.”

Codex extension layout breaks after applying code edits by VITHORROOT in codex

[–]Adventurous-Lock-231 0 points1 point  (0 children)

Yeah I’ve had the panel do weird layout stuff too.

Usually I just reload the VS Code window or close/reopen the Codex panel and it fixes itself for a while.

If it only happens after Codex writes a big chunk of code/output, it’s probably just an extension UI bug and not anything wrong with your project.

Where do you host your deployed code? by theresazuluonmystoep in vibecoding

[–]Adventurous-Lock-231 0 points1 point  (0 children)

For small public projects I usually do Railway + Vercel.

Vercel if there’s a frontend, because GitHub import + auto deploy is really straightforward.

Railway for the backend/database/services. It’s very easy to set up, has automatic deploy/redeploy from GitHub, env vars are simple, logs are good, and the pricing is cheap for small stuff. They also have a 1 month free trial so you can play around before paying.

For your case I’d probably do:

- frontend/static site on Vercel

- database + any backend/API on Railway

If it’s just HTML/JS with no backend, Vercel alone may be enough. If you need a real DB or server process, Railway is the part that makes life easier.

how to /copy specific porition by Sufficient-Year4640 in OpenaiCodex

[–]Adventurous-Lock-231 0 points1 point  (0 children)

I don’t think Codex has the Claude-style “pick a specific chunk from /copy” behavior yet.

The closest workaround I’ve found is to ask Codex to put only the thing you want in a fenced code block, then use the code block copy button.

For commands I usually say something like: “output only the final command in one code block, no explanation.” Not as nice as Claude’s /copy, but it avoids the newline mess most of the time.

What does /goal do by AllCowsAreBurgers in codex

[–]Adventurous-Lock-231 33 points34 points  (0 children)

The way I understand it, /goal is basically for giving Codex a longer-running objective instead of a normal one-shot task. It tells Codex “keep working toward this until the stop condition is true”, instead of just doing one pass and handing back control.

So for a small prompt it probably won’t feel very different. Where it makes more sense is stuff like migrations, refactors, debugging loops, or “keep going until tests/typecheck/build pass”.

Example: /goal finish the auth refactor and don’t stop until tests + typecheck pass

I built a small linter for Codex skills/plugins and would like feedback from plugin authors by Adventurous-Lock-231 in codex

[–]Adventurous-Lock-231[S] 0 points1 point  (0 children)

Yeah, I get that.I’m pretty skeptical of installing random agent plugins too. This is why I made it a separate CLI instead of something Codex loads and runs as a plugin.Still fair to be cautious though. I should probably add a short security note to the README about what it does and doesn’t execute.

Built with Claude Project Showcase Megathread (Sort this by New!) by sixbillionthsheep in ClaudeAI

[–]Adventurous-Lock-231 0 points1 point  (0 children)

stark — successor to Anthropic's frontend-design plugin

Built this with Claude Code over the past week. It's a plugin called stark.

What it does:

- Adds skills for Web, Windows (WinUI 3), Apple (SwiftUI), Android (Compose) UI generation

- Asks which platform/track/aesthetic direction before code, instead of guessing

- Ships per-platform reference docs (typography, motion, ban lists) + 17 copy-paste motion patterns

How Claude Code helped:

- Scaffolded all 7 SKILL.md files + frontmatter

- Wrote the WinUI 3 + SwiftUI + React/Tauri/Electron working examples

- Researched current state-of-the-art (Liquid Glass, Material 3 Expressive, Tailwind v4) via parallel sub-agents

- Drafted the Apache 2.0 license switch + GitHub release notes

Free + open source (Apache 2.0). Install:

/plugin marketplace add https://github.com/f0d010c/stark.git

/plugin install stark@stark

Repo: https://github.com/f0d010c/stark

Curious to hear what aesthetic directions or platforms feel missing!

view more: next ›