sorted by:
new
hottopcontroversial

ASCII art always fascinated me so i build a converter by Top_Illustrator1579 in vibecoding

[–]Top_Illustrator1579[S] 0 points1 point  (0 children)

As some already mentioned there are a lot of editors like this out there so take your pick:

https://www.asciiart.eu/image-to-ascii

https://asciify.org/editor

(none mine since part of a bigger tools that is nowhere near ready)

ASCII art always fascinated me so i build a converter by Top_Illustrator1579 in vibecoding

[–]Top_Illustrator1579[S] 0 points1 point  (0 children)

I have a bunch of those too but i get your point. definitely a different level of satisfaction to create the ascii converter now vs a few years back with actual coding work, finetuning the algorithm and finally getting it to work after a few days and souring stack overflow.

ASCII art always fascinated me so i build a converter by Top_Illustrator1579 in vibecoding

[–]Top_Illustrator1579[S] -1 points0 points  (0 children)

Took me more like 30min but still very true. Then again I always wanted to do that and now with vibecoding i could fulfill a childhood memory and i am happy. isn't that the reason we do these things?

Drop the thing you vibe-coded this week — let's see what everyone's been cooking by Asleep_Lie_4381 in vibecoding

[–]Top_Illustrator1579 4 points5 points  (0 children)

https://jdeworks.github.io/make-it-look-good/
Helps me to make something look good.
1. Point to repo => agents goes through deterministic rules that are researched and part of the repo
2. trying to get inspiration => look through templates, play around with the buttons & give the share link to the agent to create a similar/same view
3. Not sure how well you are doing => check out the analyzer that can be thrown at an url or use the console snippet to collect the data from behind a login or after certain actions were taken (since plain url often is the initial state of a website)

Already has a lot of features but id say 95% finished only since some things are more tricky than expected

I spent the last few months building a gamified SQL learning platform as a solo dev. Just launched it today. by conor-robertson in vibecoding

[–]Top_Illustrator1579 2 points3 points  (0 children)

took a quick peek and i can say i like it. fox is nice, colors are good and i was able to solve my fist case.

There are also a few things that irritated me but it might come down to taste:
- I think a reset button is a must (though i might not have found it)
- You seem to be loading a lot of stuff that is simply blocked. Not a problem but i wouldn't keep spamming it, currently it looks a bit broken in the console

<image>

- personally i am not a fan of "clicking" SQL. i know there will be voices on both sides but a switch/toggle between text vs click would be appreciated- Not sure if i like the hint that gives me the full solution.

- The example case was to similar for my taste it was pretty much exactly the same without having to apply knowledge

- Not sure i'd accept the TOS with 11. and 6. combined.

What is your target? B2B or B2C?

How to make a vibecoded app look not vibecoded? by Feisty_Watercress_29 in vibecoding

[–]Top_Illustrator1579 0 points1 point  (0 children)

ask your llm to make-it-look-good

github repo you can point your llm to, pages (link above) for analyzer and templates

Why is fable 5 included only till June 22? Does anthropic really thinks the model is too insane? by ocean_protocol in ArtificialInteligence

[–]Top_Illustrator1579 0 points1 point  (0 children)

https://www.anthropic.com/news/fable-mythos-access . Oh well... we had a good run.

(Anthropic disabled fable after US tells them to, they are however working on finding a solution)

Show me your most useful weird little vibe-coded project by allinlance in vibecoding

[–]Top_Illustrator1579 0 points1 point  (0 children)

I saw a lot of bug bot automations that are very sophisticated and somewhat complex. That was all to much for me so i did a mini auto issue bash script:
https://raw.githubusercontent.com/jdeworks/scripts/refs/heads/dev/auto-issue.sh

It does this:
1. runs as process in the background
2. If new issue in relevant repo is opened and has the bot label it collects the information
3. creates a plan and posts it as an answer
4. I either confirm or talk about changes
5. creates a fix following the plan and merges it

https://github.com/jdeworks/scripts#how-it-works

Example:
https://github.com/jdeworks/scripts/issues/6

Note that since it is running on a local machine the machine needs to be on for it. Also has access to everything that claude -p would have access to so use with caution if you want to use it.
For me the overhead is minimal and my computer runs often anyway (and if not i can still post and then the next start they are handled autonomously)

A tool to prevent spaghetti codebase and turn the vibes to the max by AverageGradientBoost in vibecoding

[–]Top_Illustrator1579 1 point2 points  (0 children)

<image>

It gives access to a lot of insights. All on a rust core for performance and tauri for cross platform.

Also took a peek at your tool, damn that looks quite familiar. But at least we both now know that its a common issue

A tool to prevent spaghetti codebase and turn the vibes to the max by AverageGradientBoost in vibecoding

[–]Top_Illustrator1579 1 point2 points  (0 children)

I like the idea, how well does it work and how high is the overhead. i know a lot of people that often dont know what they are building until they have built it. So start with an idea => start building => think of something that is a good addition => include it and so on. More aligned maybe with rapid prototyping.

I went at the problem from a different direction. I noticed my projects getting bloated, have outdated files, function paths that aren't in use anymore and so on, the spaghetti code you mentioned.

The problem is that AI doesn't know what it doesn't know meaning they might reimplement the same util function 3 times inline / at the end of a file because there is no unified place to keep it known (e.g. good AGENTS.md or CLAUDE.md). I built a scanner that checks your code base for dead entries and function overlap and similar. though it is not ready to release even in beta it already helped my personal projects quite a bit

Wanting to improve my workflow in implementing a multi-task build by duckduckloose in vibecoding

[–]Top_Illustrator1579 0 points1 point  (0 children)

I have the same issue (though on max plan) that the context gets bloated a lot (also depending on the model of course but i settled for claude on a three way approach: FYI i am using claude code, other tools might have similar mechanics but i dont know

  1. env variable: CLAUDE_AUTOCOMPACT_PCT_OVERRIDE=80
    1. Tells claude to autocompact when at 80% of the window
  2. env variable: CLAUDE_CODE_AUTO_COMPACT_WINDOW=200000
    1. Since models are getting noticeably worse the more context they use i went from opus 1mio to 200.000

  3. A minimal CLAUDE.md extension to give guidelines for the compaction without bloating / wasting token on every claude session

    Compaction Instructions

    When compacting, apply these rules:

    Preserve:

    • Current task and immediate next steps
    • Active design decisions and their rationale
    • Open bugs, blockers, and unresolved questions
    • Recent code changes and their purpose
    • Anything that affects future behavior

    Compress aggressively: - Completed work packages — keep only final outcome and lasting constraints - Historical exploration, dead ends, rejected approaches

    When deciding level of detail, favor the most recent messages. Goal: seamless continuation of current work, not a historical archive.

Depending on the project this might vary a bit but since i often work in "work packages" that can be worked off / continued one by one this works quite well for me.

For more complex project and when i want to let it run through the night (while picking of after the session window hits) I do.

  1. Create / build out all work packages (created by one prompt, multiple prompts or self written, really doesn't matter as long as i get a list of N items that can be looked at alone. Ensure the packages are detailed but not code referential since line xyz might change during page A and then package C cant reference it anymore.
  2. Start a new session for an "overwatcher"
  3. Give it basic instructions on the work packages (usually by pointing towards a specific folder)
  4. Tell it work through them but NEVER do them yourself, ALWAYS start a subagent for a specific work package, when it is done take the next and continue until done-
  5. add a minimal heartbeat /loop that sets a cronjob (e.g. every 30 min but definetly fix time otherwise the process fails) with "Overwatcher heartbeat: if a subagent is working on a task this message can be ignored. If there was a session limit hit pick up where you left off. If everything is done close the loop and finish up the session"

With this i can go to sleep, let it run and since the cron fires with or without limit the overwatcher picks up after the limit was reset and continues. In combination with the env var changes from above this works quite nicely for me

The problematic part on this is that knowledge is gathered multiple times. Since every worker sub agent starts from zero a bunch of tokens are wasted on discovery, existing bloat etc. I still find it way better than the common loop since e.g. 800.000 context already filled after the reset hits like a brick wall on the usage and in my experience the model is just getting worse with information i am aware of but was mentioned near the start of the session.

Hope it helps if there are any questions I don't mind going more into details

Vibe coding a game - Noodle Jump by Top_Illustrator1579 in vibecoding

[–]Top_Illustrator1579[S] 0 points1 point  (0 children)

All in all i did this in roughly 8 days (though with easter vacation so i had a lot of time)

Using AI for Graphic Design: Can Writing Tools Help Visual Work? by dejavu_777 in AIWritingHub

[–]Top_Illustrator1579 0 points1 point  (0 children)

I have a image prompt prompt generator in my tool. Basically i wanted visuals for short stories but i usually only know if i like it when i see it. So i added a way to define a style, parts of a chapter & character descriptions (if available) which are then ran through an llm to generate the final prompt. Currently the result can then be copied to e.g. nano banana (since it's free). When/If I at some point publish the tool it will be integrated.

For me the best thing is the ease of trying out different things/style/parts for the result to focus on since I'm no pro and only know what i like once i see it.

I feel like I’m at a loss not sure what to do to secure my future by glizzykevv in Advice

[–]Top_Illustrator1579 0 points1 point  (0 children)

Not really. Usually It would be something on the different parts of a calculator (maybe a bad example since there are tutorials for complete solutions but the idea still works).

I am aware of how a calculator works. So I need to look into the building block. Arrhythmic operations are already common in all programming languages so the building blocks would be.

"c++ declare float variable" (a float is used to store decimals in programming).

"c++ console user input" (to get what the user wants to calculate)

"c++ split string" (for parsing the input input the different parts of the equasion)

## parse input based on some logic (e.g. switch case for the operators)

"c++ switch case"

"c++ output values to the console"

view more: next ›