DEV Community: robot1996

How I’m organizing RSP-style AI photo prompts into safer, copyable templates

robot1996 — Fri, 29 May 2026 06:37:48 +0000

RSP-style photo edits are getting shared everywhere, but most prompt examples are scattered across short videos, screenshots, and comment threads. I wanted a cleaner way to save the useful parts without encouraging people to copy unsafe or misleading edits blindly.

So I put together AI Editor RSP Editing, an unofficial English hub for copyable RSP-style AI photo prompts, template recipes, Lightroom preset notes, and safer editing workflows.

Link: AI Editor RSP Editing

What I’m trying to make easier:

Copy a prompt template without rewriting it from a video screenshot.
Understand what each part of the prompt is supposed to control.
Keep a clear safety note around identity, consent, and unrealistic before/after claims.
Compare prompt recipes with Lightroom-style finishing steps.

This is not an official RSP product or affiliated resource. It is a small independent resource site for people experimenting with social profile photos and creator-style visuals.

I’m especially looking for feedback on:

Whether the prompt cards are readable enough.
Whether the safety notes feel practical instead of preachy.
Whether a creator would prefer more examples, presets, or workflow checklists next.

I built a fan-made tools hub for Universal Tower Defense players

robot1996 — Mon, 25 May 2026 15:05:32 +0000

I shipped a small fan-made tools site for Roblox Universal Tower Defense players: Universal Tower Defense Tools.

The goal is practical rather than flashy: put codes, tier list notes, value references, calculators, updates, and redeem guidance in one lightweight browser hub.

Why I built it

For Roblox game communities, information tends to be scattered across wiki pages, Discord messages, YouTube comments, Trello boards, and game-update posts. That makes it hard for a player to answer simple questions quickly:

Which codes are active or expired?
Where should I check update notes?
How should I compare units, values, or upgrade costs?
What source was used for a piece of game data?

This first version is a small SEO and UX experiment: can a focused fan-made utility page be clearer than another long article page?

What is inside the first version

Codes and expired-code tracking
Tier-list and value reference pages
Calculator-style helper pages
Update and redeem-code guidance
Source notes and fan-made disclaimers
No login, no payment, no Roblox account collection

What I am watching next

The next useful signal is not pageviews alone. I want to see whether players actually use the utility pages:

code copy clicks
calculator interactions
clicks from codes to tier/value pages
repeat visits after game updates
correction requests when data is stale

Feedback welcome

If you build SEO tools, game utilities, or fan-made resources, I would like feedback on one question:

Should this kind of site lead with the codes page, or should the homepage act as a broader tools hub first?

Link: Universal Tower Defense Tools

Disclosure: this is a fan-made resource and is not affiliated with Roblox or the Universal Tower Defense developers. Game data can change, so players should verify important details in-game or from official/community sources.

I built a small fan-made Roblox Wizard Alchemy codes tracker

robot1996 — Sat, 23 May 2026 02:05:05 +0000

I put together a small fan-made tracker for Roblox Wizard Alchemy players who just want the current code list without scrolling through a long article first.

The page is here: wizard alchemy codes

What it focuses on:

working codes first, with a copy button next to each code
a separate needs-review section when a code has conflicting public sources
an expired-codes area, even when there are no confirmed expired codes yet
simple redeem steps for new players
last-checked dates so returning players can judge freshness quickly

Implementation notes:

Next.js 15 + TypeScript + Tailwind
deployed on Cloudflare Workers
no login, no payment, no user-generated content
consent-gated analytics for basic launch observation
fan-made wording and non-affiliation disclaimers are shown on the page

The main product decision was to make the page answer-first: show the codes and copy action before explanations, then keep the caveats visible enough that the page does not imply the list is official or guaranteed.

If you build small utility/content sites, I would be curious about the structure: should the update notes stay on the same page as the code table, or is a separate update page better for this kind of tracker?

Disclosure: this is fan-made and not affiliated with Roblox, Wizard Alchemy, Muggle Academy, or the game developers. Code availability can change after updates.

I built a spoiler-safe Tadpole guide utility for Subnautica 2 players

robot1996 — Fri, 22 May 2026 05:07:46 +0000

I shipped a small fan-made guide utility for Subnautica 2 players who search for Tadpole unlock steps, fragments, upgrades, and related route notes.

Link: Subnautica 2 Tadpole guide

The site is intentionally narrow. Instead of trying to be a full interactive map, it focuses on one player task: "I want to understand the Tadpole path quickly without reading a long guide."

A few design choices:

quick answer first, then details
checklist-style sections for unlock / fragments / upgrades
spoiler-safe notes for players who do not want everything revealed at once
visible fan-made / no-affiliation wording
no login, no payment, no official assets

The product is built as a lightweight content utility with Next.js, TypeScript, Tailwind, and Cloudflare Workers.

The hard part is not the tech stack. It is keeping the page useful while Subnautica 2 is still in Early Access and information can change. The page therefore avoids pretending to be an official database and keeps source/confidence wording conservative.

I am watching whether players prefer this focused utility over a longer general article or a full map tool.

If you build small SEO/content tools, I would appreciate feedback on:

Is the Tadpole-only scope too narrow, or is that a better fit for search intent?
Would a compact checklist beat a longer article for this type of player query?
Is spoiler control worth keeping for a guide page like this?

This is a fan-made project and is not affiliated with Unknown Worlds, Krafton, or the Subnautica team.

I built a lightweight Roblox Anime Limitless codes tracker

robot1996 — Fri, 22 May 2026 02:23:18 +0000

I shipped a small fan-made utility site called AnimeLimitlessCodes for Roblox players who search for Anime Limitless codes after an update.

Link: Anime Limitless codes

The idea is intentionally simple: many code pages are long articles, while a player on mobile usually wants three things quickly:

see current codes first
copy a code for redemption
check expired codes and redeem steps without digging through a long page

A few implementation notes:

Built as a lightweight content-first site with Next.js 15, TypeScript, Tailwind, and Cloudflare Workers.
The page is designed around fast mobile reading rather than a heavy app flow.
Code availability can change after game updates, so expired codes and update notes are kept separate from current codes.
Analytics are consent-gated; the site does not require login.
The project is fan-made and not affiliated with Roblox or the Anime Limitless developers.

The part I am watching now is whether the page solves the “I just need the code and redeem steps” use case quickly enough on mobile.

If you are interested in small SEO/content utility sites, I would appreciate feedback on:

Is the page too minimal, or is that a good fit for this search intent?
Would a sticky copy/redeem section help mobile users?
Are update notes useful on the same page, or should they be split out?

Thanks for taking a look.

I built a tiny browser game for guessing cartoon-inspired colors

robot1996 — Fri, 15 May 2026 12:39:16 +0000

I shipped a small browser game called Toon Tone Color: a 5-round color memory challenge where you read a cartoon-inspired prompt, adjust HSB sliders, submit a guess, and get a score card at the end.

Link: Toon Tone Color

Why I made it:

I wanted a lightweight game that works instantly in the browser.
The interaction is simple enough for mobile: read a prompt, tune hue/saturation/brightness, submit.
The result card is generated client-side, so players can copy and share it without uploading their gameplay data.

A few implementation notes:

Built with Next.js 15, TypeScript, Tailwind, and Cloudflare Workers.
The first version is free and does not require signup.
Analytics only load after consent; the gameplay state is kept in browser localStorage.
The site is fan-made and not affiliated with any cartoon, anime, game, comic, studio, or entertainment brand.

The part I am watching now is whether people understand the HSB slider interaction quickly enough on mobile. If you try it, I would appreciate feedback on:

Is the first round obvious without instructions?
Are the hue/saturation/brightness sliders easy enough on a phone?
Would you share the score card, or does it need a clearer prompt?

Thanks for taking a look.

Building a small fan-made Diablo IV loot filter finder

robot1996 — Sun, 10 May 2026 02:58:45 +0000

Building a small fan-made Diablo IV loot filter finder

When I looked for Diablo IV loot filter presets, I kept running into the same problem: useful filter codes were scattered across videos, Discord posts, forum comments, and build planner notes. It was hard to quickly answer basic questions like:

Is there a filter preset for my class?
Is it meant for leveling, endgame, bossing, or farming?
Where did the code originally come from?
Can I copy the import code without digging through a long page?

So I built a small web tool: Diablo4LootFilter.

It is a fan-made finder for Diablo IV loot filter presets and import codes. The goal is not to replace the original creators. The goal is to make presets easier to discover, with source attribution and a clear path back to the original source.

What the tool does

The first version focuses on a simple browse-and-copy flow:

filter presets by class, stage, and farming goal
view source-attributed preset details
copy import codes faster
open the original source when attribution is available
allow correction or removal requests through the support contact

I intentionally kept the scope narrow. For a game utility like this, trust matters more than adding too many features early.

Product decisions I made

A few choices were important for keeping this acceptable as a community resource rather than a spammy scraper:

Source attribution first

If a preset comes from a creator, guide, or public resource, the page should point back to that source.
No official wording

The site is fan-made and is not affiliated with Blizzard. I avoid words like “official”, “approved”, or “verified”.
No overclaiming import codes

Some codes may need in-game verification as the season changes. The site should not imply that every code is guaranteed to work forever.
Simple feedback loop

If a creator wants attribution changed or a code removed, the site provides a contact path.

Implementation notes

The site is built as a lightweight content/tool page rather than a full community platform. That keeps the first version easy to crawl, easy to index, and easy to update.

The main technical focus was:

fast page load for search traffic
structured pages for filter detail pages
event tracking for important actions like filter selection and copy actions
sitemap and indexability checks before doing any promotion

I wanted to avoid the common launch mistake where you send traffic before you can measure whether people actually use the tool.

What I am looking for feedback on

If you play Diablo IV or build small niche tools, I would love feedback on:

whether this finder format is useful
what metadata matters most for loot filter presets
whether source attribution is clear enough
what would make import-code pages more trustworthy

Link: https://diablo4lootfilter.com/

Disclaimer: Diablo4LootFilter is a fan-made project and is not affiliated with Blizzard Entertainment.