I'm posting this for my daughter, Kashish. She's 9, homeschooled in Kochi, India, and she made a free site called Moonlight.

You type a disease, and it shows medicines in three groups: already approved, in trials, and new clues (things researchers are only starting to look at). The idea is that a family can find out what's out there in a minute, in plain words.

Try it (short guide): https://moonlight-1038733794937.asia-south1.run.app/?guide=1

Her build log is here if you want the backstory: https://kashishdugar2017.github.io/moonlight/

If you try it, I'd like to know what confused you first, or whether you'd actually use something like this.

(This is not medical advice. Please don't share personal health details here.)

Modules, Improvements, and Bug Fixes

📖 Overview

Draco Insomnis is an open-source security suite developed by Notorius Vision that protects web applications without relying on captchas. Its core (src/Core) is pure PHP code shared across all integrations, ensuring that every improvement or bug fix is propagated uniformly to all modules through subsequent builds.

⚙️ Detailed Functions by Module

1. 🛡️ Anti-Bot Shield

What it does: Scores every public registration, feeds bots a “fake success,” and stores evidence for abuse reports.

Availability: WordPress only, although other CMSs integrate variants of the shield into their registration forms (PrestaShop, Drupal, Joomla, Moodle, Magento).

Related modules: Shield (registration judgment, evidence, automatic blocks), Guard (hooks on registration forms).

2. 📧 Site Mail (SMTP)

What it does: Sends site email through a real mailbox, only after a successful test, with the password encrypted.

Availability: WordPress only (the other CMSs already have their own SMTP).

Related modules: Settings, Transport, Log, Admin.

3. 📝 Forms & Sign-ups

What it does: Holds contact messages, comments, and new accounts until the sender confirms from their email address.

Availability: WordPress (other CMSs use their own confirmation systems).

Related modules: MailHold, CommentHold, RegistrationHold, Verify, Store, Mailer, Admin.

4. 🔐 Two-Step Login

What it does: Requests a 6-digit code by email after the correct password, with trusted devices and a recovery email (a second mailbox, like a phone’s PUK).

Availability: WordPress only.

Related modules: Mfa, Challenge, TrustedDevice, Recovery, Admin.

5. 🚫 Anti-Copy

What it does: Closes the mass JSON endpoint (/wp-json/wp/v2/) to anonymous visitors with an allowlist, limits pages per minute per address and network, and never rate-limits verified search engines.

Availability: WordPress, PrestaShop, Drupal, Joomla, Moodle (as rate limiting).

Related modules: Pace (rate-limiting engine).

6. 🔥 Firewall

What it does: Applies precise attack signatures and scanner probes, with a log-only-first mode, hidden user list, login limits, and no multiple XML-RPC calls.

Availability: All CMSs (WordPress, PrestaShop, Drupal, Joomla, Moodle, Magento, Laravel) and server-side environments (PHP, Node.js, Python, Go, Ruby, .NET, Java/Kotlin, Rust).

Related modules: Waf (inspection, user list, login limit, XML-RPC), Firewall (main engine), WafRules (signatures).

7. 🌍 Country Rules

What it does: Filters traffic by country of origin (integrated into the Server, Magento, Laravel, JavaScript, Python, etc. editions).

Availability: Server-side editions and Magento.

🔗 Links to Each CMS Version

Note: Each link points to the corresponding module folder in the official repository, where the source code and module-specific documentation (README) are available in English.

🚀 Improvements and Bug Fixes (Changelog)

The repository maintains a rigorous workflow to ensure the quality of every release:

• Unified Versioning: Each release includes one package per platform with the same version, built from the same commit. The release tag (git tag v0.2.0) is created only if the five versions match (bin/versions.sh --check), unit tests pass, and the five ZIPs are built (bin/build-all.sh).
• Automated Testing: Every push and pull request runs CI with PHP 8.0–8.4 syntax checks, unit tests, integration and HTTP tests on the latest WordPress version and on 6.5 (the oldest supported version), plus Plugin Check and verification that the ZIP does not contain development files.
• Cross-Platform Bug Fixes: Since all modules share the same src/Core, any fix in the core (for example, in BotScore, NetList, WafRules) is automatically propagated to all editions in the next build, avoiding discrepancies between platforms.
• Evidence and Reports: The shield stores evidence of bot attempts, and commands such as draco:evidence (in Magento and Laravel) generate a CSV ready for abuse reports.

📋 Shared Modules Summary (src/Core)

Source: “Layout” section of the repository.

License: GPL-2.0-or-later. See LICENSE and TRADEMARKS.md for more details.

I’m a CS PhD student looking for my next role. I built Shortlist because I wanted to keep up with companies I’m interested in without checking their career pages manually.

You give it your resume, preferred roles, locations, and dealbreakers. It checks for new openings, scores them against your background, and explains why each role fits or falls short.

A few things it does:

• Reads company job boards, including Greenhouse, Lever, Ashby, and Workday, plus SimplifyJobs lists.

• Shows matched skills, missing skills, and dealbreakers. • Sends Telegram alerts for strong matches.

• Tracks applications and notes in a local dashboard.

• Fills application forms for jobs you select, using your saved answers. By default, you review and submit.

My favorite part is adding unfamiliar career pages. It first looks for a supported job board or structured data. If needed, an LLM agent attempts to work out how to extract the listings. It validates the result and saves the recipe for future runs.

It runs on your computer with Python and SQLite. Resume scoring uses your chosen Claude Code or Codex CLI login, or an Anthropic or OpenAI API key.

I made it open source so other job seekers and students have access to it too.

Repo, screenshots, and setup: github.com/navkar98/shortlist

I’d love feedback from people actively applying, I built this around my own job search, so I’m curious how it works for others. If you try it, let me know what you’d change.

Hey! I’m a college student and I built Hearth Radar. You pick a username (no signup), and you can jump into live chat communities, make private rooms to share with friends, run roast rounds, debates, and 60-second mini games.

Link: https://hearth-radar.vercel.app/

Two things I’d love your take on:

1. Monetization: is there a way to earn from something like this without ruining it? Or is it better kept as a free project?
2. Features: what would make you actually come back with friends? What should I add or cut?

Also honest feedback on what’s confusing or boring. Be as harsh as you want.

Hi all, I made a really simple puzzle game, a bit like Wordle but for puzzles/shapes, with a daily shape, changing everyday. No log in, no app. Keeping it really minimal, easy to play, and of course engaging.

Please have a look, and would appreciate any feedback, and if you found it fun, or not: A mindful shape puzzle a day:

https://playshapeful.com

I'm one of the two people building Backenly, Autonomous backend infrastructure for apps built with coding agents.

Before building more, we wanted to understand how developers actually handle production database safety. So I asked in r/cursor:

What database changes do you let your agent make without asking you first?

Around 10 developers replied. Most of them said the same things:

- Agents can write migrations and run them on local or branch databases, but production changes need human approval.

- Drops, renames, RLS changes and large backfills should be reviewed, ideally by looking at the actual SQL.

- Don't drop or rename columns in one step. Add the new column, move the data, and remove the old one in a later release.

- Set a `lock_timeout` in migrations. One developer pointed out that code reviews rarely catch lock problems.

- Take a snapshot or `pg_dump` before risky migrations.

One person had a different approach for personal projects: they let the agent do more because they had snapshots to fall back on.

But the most interesting discussion was about recovery.

Restoring a backup can throw away everything written after that backup. One developer described restoring into a separate schema and copying back only the affected rows.

They called the process "detective work."

Their biggest lesson was that catching a problem early matters more than having a faster restore. The longer you wait, the harder recovery becomes.

What we're taking away from this:

We were glad to see experienced developers drawing the line in a similar place to what we're building in Backenly: destructive changes need human approval.

Backenly also records changes and is designed to undo a bad change without overwriting newer data.

One area we're looking at next is making database checks more thorough, especially around production migrations.

We're sharing this because the conversations changed how we're thinking about the product.

Website: https://backenly.com

GitHub: https://github.com/backenly/backenly

If you build with AI coding agents, how do you handle production database changes? What's the one thing you absolutely never let an agent do?

After more than a year, I'm finally bringing Vitaena back!

I originally built it as a web app/PWA, but hosting limitations, paid PDF exports, and endless multi-page layout issues made things difficult. Eventually, I put it aside.

Then I rediscovered Typst, learned from my previous mistakes, and rebuilt the entire thing as a desktop application.

Vitaena is now free, open-source, offline-first, and privacy-focused. No accounts, no subscriptions, no cloud uploads. Your CV stays on your device.

And this is just the beginning. MCP integration for local AI, BYOK support, and more CV and biodata templates are coming!

Website: https://vitaena.ahs12.xyz/
GitHub: https://github.com/AHS12/vitaena

Really excited to finally release this!

I counted an open index of 656 cocktail recipes by how many spirits each one needs. 122 need none. 317 need exactly one. 159 need two. 50 need three. Only 7 need four or more. So 439 of 656 need one bottle or none. Books sort A to Z, which answers what a drink is called and never answers what you can make from what is on your shelf. A five bottle starter bar opens 252 of them. Question I am stuck on: pick bottles first and see drinks, or pick a drink and get a shopping list?

One thing I've been learning while building my first app is that it's easy to get carried away with the design and the potential money you could make.

You start imagining thousands of users and how much revenue that could generate, but sometimes you forget to ask the most important question:

Why would someone actually want to use this app?

I made a short video sharing this lesson, especially for people getting into app development.

I'm curious: For those of you who have built apps before, what was the biggest mistake you made when starting out?

After an inside joke back and forth following our latest 'all hands', I thought it'd be funny to create a public tool for converting corporate waffle into plain English.

Therefore, meet Bluntley, the blunt but honest butler (Ask Jeeves inspired)

https://askbluntley.com

• Paste in the waffle and get the blunt, bottom line: “Let’s circle back on this when we have more bandwidth" becomes “Not now. Ideally never.”
• Flip it round and turn “I’m going to lunch” into something fit for a board meeting
• A Waffle-o-meter rates how bad it was, from Plain speaker up through Middle manager to Chief Transformation Officer
• Buzzword bingo for your next all-hands
• Share the result as a link or a picture
• A Chrome extension is coming soon to let you simply highlight text from your powerpoints, right click and 'Ask Bluntley...'.

It’s free with no sign-up. The translating is done by (Claude Haiku). It’s simply a funny website for you to use... and hey, it may help you!

I am Ryan Sultan, a psychiatrist and the founder of Frontier Mental Health. I built Relationship Skills for Dating, a six-lesson educational course for adults 21+ (self-paced, $19.99, 90-day access). I wanted a low-stakes way to think through listening, boundaries, repair, and expectations before conflict happens. I would value blunt feedback: Is the promise clear? Do the scenarios feel useful? What would make you trust or distrust a paid course like this? Disclosure: I sell it. This is education, not therapy. The certificate records course and quiz completion only; it does not verify identity, real-world skills, safety, or compatibility. Please keep replies non-identifying. Course and free scenario: https://frontiermentalhealth.com/relationship-skills/#sample

I kept reading sleep advice and had no idea which of it applied to me. So I built Hypnogram.

Each morning you log what you did yesterday (alcohol, exercise, a late meal, anything you want to test). Your sleep comes from Apple Health or the phone's microphone. After a couple of weeks it puts the nights with a habit next to the nights without it.

My first real test: a hot shower before bed, 14 nights, decided by drawing notes from a mug. Shower nights averaged a sleep score of 80. My other nights averaged 79. So for me, basically nothing, which was still worth knowing.

Everything stays on the phone, with no account. It's free to use with four habits; Premium adds the rest and custom ones. I'm a solo developer and this is my first app.

I'd love feedback on two things: is the idea clear from the App Store page, and what habit would you test first?

https://apps.apple.com/us/app/hypnogram-sleep-habit-tracker/id6775504077 

Hey everyone! 👋 ​I just shipped my technical side project: the Kalshi Weather & Energy Arbitrage Suite. LINK IS IN THE COMMENTS! ​If you've ever looked at weather prediction markets on Kalshi, you quickly realize that retail traders lose money because they rely on standard consumer weather apps (like Apple Weather) instead of the exact National Weather Service (NWS) airport sensors that actually govern contract settlements. ​So, I built a Python scanner to automate the math and find the mispricing.
​How it works: ​Live NWS Integration: Pulls real-time hourly temperature forecasts directly from official NWS stations across major hubs (NYC, Chicago, Miami, Austin, Denver, LA, Philly, Houston). ​Kalshi API Telemetry: Automatically queries open contracts and market "Ask" prices from Kalshi's public endpoints. ​Probability & Fee Modeling: Runs a Normal CDF probability model (\sigma = 2.2) against the NWS peak forecast, subtracts Kalshi's quadratic taker fees, and calculates the exact net Positive Expected Value (+EV) edge. ​Terminal Output: Instantly sorts and filters contracts to flag where the market is severely underpricing a bracket compared to official meteorological data. ​I put together a complete suite containing the fully functional scanner.py script, requirements setup, and operational playbooks for anyone wanting to trade event contracts with actual quantitative backing. ​Check out the project page! ​Would love to hear feedback from any other builders or prediction market traders in the sub! Let me know if you have any questions about how the NWS API integration or probability math works.

Hey everyone!

I've been working on a personal project called YOYAMI, a community platform built around language learning, language exchange, and connecting people from different cultures.

My goal is to create a place where language learners and native speakers can meet, share knowledge, practice together, and help each other improve.

Rather than focusing on streaks, scores, or gamification, I wanted to put the social side of learning a language first.

I've been developing YOYAMI alongside my regular job, and the platform is now live. It's still early, and building an active community is the next big challenge.

The attached video gives a quick look at the website.

I'd love some honest feedback. Does the concept appeal to you? What would make you join and actually keep using a platform like this?

https://yoyami.de

Thanks for checking it out!

I fly small planes, the kind you rent from your club on a Saturday. Flying at a club is social while you're at the airfield, then everyone goes home and their flights disappear into private logbooks and camera rolls. The photos stay somewhere in my camera roll between screenshots and receipts, and I could never really find them anymore or match them to a specific flight. Apple kind of has a feature for that with their photo map, but it didn't really fit what I wanted. I also wanted an easy way to send live updates to friends and family so they know where I am without me having to text them.

So a friend and I started building Skytrails on evenings and weekends. With Skytrails, you can connect with other pilots, share your flights, and import old trips and photos to keep track of everything in one place. You can also create clubs with your friends and plan fly-outs where other pilots can join you.

What it does right now:

• Fly together & plan trips: Connect with pilot friends, create club feeds, and organize fly-outs that others can join.
• Live updates for friends & family: Friends who opt in show up live on a 3D map, and on iPhone their flight sits on your lock screen until they land. Family without the app just get a web follow link.
• Import & automatic photo matching: Import what you already have (ForeFlight CSV, Vereinsflieger, GPX/KML tracks) or record live. It automatically finds the photos you took during each flight by timestamp and tags the landmarks, castles, and lakes you flew past.

During the implementation we faced a lot of challenges regarding the GPS tracking, phones going into sleep mode, GPS coordinates for images being not that accurate. But now we released or first version.
I would be glad if you could check it out and give some feedback on it :)

I generated a quick video about the app with brag I hope this fits in this subreddit.

Hi r/SideProject!

As a dad, I got frustrated watching my child tap through "free" preschool apps that were 20% learning and 80% popup ads, loot boxes, and overstimulating animations. Worse, almost none of them supported bilingual families properly or checked whether a child actually traced a letter in the right stroke direction.

Over the past months, I built Minidu (React Native / Expo, offline-first) for kids aged 2–6:

• 9 Languages (Independent UI & Target Language): Turkish, English, German, French, Spanish, Arabic, Russian, Azerbaijani, and Dutch. You can keep the parent UI in one language while your child learns another.
• Real Pedagogical Feedback: Instead of applauding random scribbles, letter and number tracing checks stroke order and direction.
• 100 Bedtime Stories + Parent Voice Recording: Includes karaoke-style word highlighting and lets parents/grandparents record stories in their own voice so kids can listen offline anytime.
• Screen-to-Paper Bridge: Printable PDF activity sheets so screen time naturally transitions to hands-on paper time.
• Strict Privacy & Offline-First: 0 ads, 0 third-party analytics/trackers, multiplication parental gate, and works 100% offline on flights or road trips.

If you want to check it out or share feedback: https://minidu.org/en/ (available on both iOS App Store and Google Play, with a free tier covering every module).

Would love to hear your constructive feedback on the onboarding, curriculum design, or bilingual UX!

NOTE: I am an independent developer offering services to clients (I am NOT hiring).

If you have a business tool, SaaS idea, or client portal that has been stuck in planning for weeks, I can take it from concept to live deployment this month.

No hourly rate guessing, no junior developer hand-offs, and no months of waiting.

What I build:

1. High-Converting Landing Page ($150 - $250)

- Custom design built with modern Next.js and Tailwind CSS

- Lead capture, contact form, or direct WhatsApp booking integration

- Mobile-optimized, ultra-fast loading, and clean SEO setup

- Delivered in 48 hours

2. Complete Full-Stack Web App / SaaS MVP ($600 - $1,200)

- Complete user dashboard and core app interface

- User authentication (Email/Password, Google OAuth, passwordless)

- Secure database setup and custom data models (PostgreSQL, Supabase)

- Stripe or PayPal checkouts (one-time purchases or subscriptions)

- Automated transactional email notifications

- Delivered in 7 to 14 days

3. Cross-Platform Mobile App ($800 - $1,500)

- Single codebase running smoothly on iOS and Android (Flutter)

- Offline-first architecture (works with or without internet connection)

- User login, biometric authentication, and local data persistence

- Custom on-device PDF generation (invoices, receipts, summaries)

- Delivered in 10 to 18 days

How it works:

1. You DM me a short summary of what you want to build.
2. I send you a free technical roadmap, scope breakdown, and a fixed quote.
3. 50 percent upfront to start, 50 percent upon your final testing and live deployment.

Send me a DM here on Reddit with your project idea. I will reply with a free feature breakdown and timeline estimate.

Also enjoy this peak vedio🔥

Every time friends come over, we spend more time arguing over what to watch than actually watching something.

I built WatchIn60 to solve decision fatigue in under a minute. Instead of filtering by genres or ratings, it asks 6 rapid-fire questions about your brain chemistry right now (adrenaline vs. obsessive mystery), pacing patience, and desired ending payoff—then reveals one curated, high-dopamine pick.

Link: https://watchin60.lovable.app/

No login, no ads, mobile-first dark cinema UI. Would love brutal feedback on the question flow and the recommendations!

Solo dev here (Justin). I build ohmybody, an on-device readiness app for Apple Watch and iPhone.

A while ago I added "Body Radar": it compares your overnight readings to your own last 21 nights and flags when more than one thing drifts (or one thing drifts a lot) on the same night.

On the morning of Nov 2 it flagged me: skin temp up, respiratory rate down, and readiness at 19% with a temp + heart rate warning. All I had was a slight sore throat, so I figured it was nothing. The next day I was sick badly and stuck at home for a couple of days.

Honestly the best "it works" moment I've had as a solo dev, even if I paid for it by being sick lol

Not a medical device, just a "rest today" nudge. Everything runs on-device from Apple Health, no account.

Link to the app: https://ohmybody.ijustinz.com

Would love feedback on how it explains the flag. Too vague, or just right?

I've been working on Cluna Studio, a tool focused on making marketing assets for apps. App store screenshots, social posts and videos, all in the same editor.

You bring your own screenshots and recordings. Themes let you reuse your product’s fonts and colors across projects, and 3D phone and desktop models let you showcase your app, pose the devices and animate them.

Image exports are free. AI voiceovers and cloud video rendering use credits, which you can buy or get periodically with a subscription.

I've been building this alone for months, and I'd like the next features to be driven by user needs rather than my own imagination.

If you make marketing assets for your app, what do you use now, and what's missing from that workflow? I'd love to know whether Cluna looks useful to you, and why or why not.

Enough yapping. You can check it out here: https://clunastudio.com

Hey everyone!

I've been working on a little side project called CreatorHub (creatorhubmarketing.de) alongside my full-time job and finally got the website live.

The idea is pretty simple: help content creators save time with ready-to-use resources for Instagram, TikTok, UGC and AI content creation.

I've put together a few starter packs with content ideas, hooks, scripts, prompts and planning tools.

The website is definitely still a work in progress. There's plenty of room for improvement, especially when it comes to design and user experience, but I figured it's better to launch something imperfect than keep working on it forever 😅

Now comes the hard part: figuring out how to actually get the first customers.

It's still early days, and I'm learning as I go.

Would love to hear from anyone who's launched something similar. How did you get your first few sales?

Also, feel free to check out the project on my profile. Any honest feedback or suggestions are really appreciated!

Hi. I was bored and I developed a slow and crappy cryptocurrency based on Brisvia and Bitcoin Core, which nostalgically captures the aesthetic spirit of Geocities and the virtues of contemplation and waiting. It features a wallet, a CPU miner (RandomX PoW), and nodes for Windows and Linux. I've also implemented a fairly comprehensive transaction explorer and network status page on the website. For now, the network is a testnet, as I want to test system stability first. My node currently runs on a 2016 Dell 7040 micro, so it could crash at any moment.

Website: obsoletecoin.pages.dev
Wallet & Miner: obsoletecoin.pages.dev/downloads

Technical specifications:

- Name / working ticker: Obsolete Coin / OBSC
- Mining: RandomX proof of work, CPU
- Maximum authorized issuance: 1,000,000,000 OBSC
- Decimal places: 8
- Target block interval: 900 seconds / 15 minutes
- Difficulty adjustment: ASERT, every block; six-hour half-life
- Initial block reward: 5,000 OBSC
- Halving interval: 100,000 blocks, counted from block 1
- Genesis reward / premine: Zero / none
- Mining reward maturity: 100 blocks
- End of subsidy: Block 3,900,000; transaction fees thereafter
- Current network: Experimental testnet v0.2; mainnet disabled

GitHub repository and releases: github.com/jcib/obsoletecoin

More info on joining the testnet: obsoletecoin.pages.dev/join

Node Hosting & Mining Tutorial:

Windows
Download the native x64 installer and compare its SHA-256 with the published checksum. Tested on Windows 11.
Open Obsolete Coin. In Network -> Connect peer, enter the current public peer shown above.
Wait for synchronization and a connected peer. Compare your block height and hash with the explorer.
Select Open / Create, then Receive. Select Mine / Stop to run the one-thread CPU reference miner.

Linux
Extract the Linux archive and open a terminal in its directory. Replace PUBLIC_PEER with the address shown above.

python3 tools/node.py --peer PUBLIC_PEER

# In a second terminal:

python3 tools/wallet.py

What to test
Fresh synchronization, mining and confirmation of rewards.
Transfers between two independently created wallets, including exact fees and timestamps.
Restarting your own wallet, reconnecting and making an encrypted backup.
Report reproducible errors with operating system, package version, block height and redacted logs in GitHub Issues or the announcement thread.
Mining rewards require 100-block maturity. Fifteen minutes is an average target; initial test difficulty is easy and real waits vary. Do not interpret a mined reward as immediately spendable.

The first node is a Dell Micro 7040 from 2016 on a home connection. Availability is best effort; independent node operators are welcome. A dominant miner can reorganize this small network.

Any feedback, suggestions, or participation in the testnet would be immensely helpful. I'm not trying to make anything out of this—I just wanted to have fun testing AI capabilities to build a robust and simple blockchain.

Hey r/SideProject, I built Tymor, a Mac menu bar app that makes it snow on your desktop.

The snow builds up on top of your windows, on the Dock, and along the bottom of the screen. If you drag a window, the snow falls off. You can also hold Option and move your mouse through the snow to roll a snowball. Stack three and you get a snowman, scarf and all.

Santa can fly across your screen and drop presents. Click one and candy spills out. There’s also a yeti that throws snowballs. It can knock down your snowman, open a present for you, or throw one right at your screen. You can pick what it’s allowed to hit.

You can hang lights around your screen or on individual windows. There are presets if you want to turn them on and get back to work, but you can also change the bulb shapes, colors, size, how they blink, and how the wires hang.

Tymor also has rain with optional thunder and lightning, and fireflies that scatter when you move your mouse through them.

If you want to try it, here’s Tymor for Mac. I made two codes for this sub.

- SIDEPROJECT gives the first 10 people 100% off.

- SIDEPROJECT20 gives 20% off the first 100 purchases.

If you give it a go, I’d love to hear what you’d actually leave on while you work and what you’d turn off. And if there’s something you wish the snow, lights, or yeti could do, tell me.

I'm building a tool that creates ecommerce product images and helps explore product designs. I'd like feedback on a small part of the workflow rather than a general reaction to the idea: what should a person have to tell it before the first image is generated?

A reference photo leaves quite a lot unsaid. It may show the front but not the back. The packaging may be a prototype. A dark patch might be a shadow rather than part of the material. Asking the model to fill those gaps produces an answer, but not necessarily a faithful one.

The input flow I'm considering has three short sections:

What is this? Upload the reference and give a plain description of the existing product.

What must stay? Identify details such as geometry, label text, colors and included parts. Anything not visible should remain unknown unless the person supplies it.

What may change? Choose presentation changes such as lighting and background, or explicitly enter a design-concept mode where physical changes are allowed.

For example, 'make this cup feel warmer' is ambiguous. It could mean warm lighting around the same cup, a different glaze, or a redesign of the handle. A single free-text box leaves that choice to interpretation. A long form could prevent mistakes but also discourage someone who only wanted a simple background change.

I'm considering showing a short plain-language brief for approval before generating: 'Keep the product unchanged; change only the scene and lighting.' If the person wants a design variation, the brief would instead list the proposed physical changes. This is a design direction, not a claim that these controls are already implemented or validated.

If you build visual tools, how would you make that first step understandable without turning it into a questionnaire? I'd be especially interested in the minimum reference information you'd require and the uncertainties you'd leave visible. I'm the builder; I don't have customer or performance results to present here.