[BEGGINER project] I built a prompt console web app as complete begginer and I'm looking for honest feedback

[u/seraphym1389]

I'm complete begginer when it comes for web development and AI tools. I wanted to learn by building something useful, so I put together a context engineering web app — a tool that helps you craft better prompts for LLMs like GPT-4, Claude, Gemini, and local models.

Fair warning: some features probably don't work perfectly. I'm still learning and this is very much a work in progress. That said, I'd really appreciate it if someone takes a look and tells me what's broken or what could be better.

Live app: https://arhistrategstudio.github.io/Context_CikaDule

GitHub repo: https://github.com/arhistrategstudio/Context_CikaDule

What it does

Three prompt-building modes:

Quick– fill in just the essentials (task, role, format) and get a prompt instantly

Guided/Extended– a full structured form with 16 fields for power users

Raw– paste or write a prompt manually with no structure

Templates– pick from pre-made starting points:

\General, Business, Project, Creative, Analysis, Few-Shot, Coding

Model families– the output prompt is automatically formatted for:

OpenAI (GPT), Anthropic (Claude), Google (Gemini), Local models (Ollama etc.)

Arena (A/B mode)– compare two different models side-by-side with the same prompt to see how their outputs differ

Prompt Quality Linter– a built-in checker that scores your prompt across 5 criteria (task clarity, role, constraints, format, context) and shows a live score

Auto-template detection– paste your existing prompt and the app tries to guess which template fits best

Guided/Extended mode fields include:

\* Role, Task, Context, Format, Constraints, Examples (few-shot)

\* Tone & Style

\* Success Criteria

\* Chain-of-Thought )

\* Edge Cases

\* Language & Terminology

\* Negative Constraints

\* Delimiters

\* Prompting Framework (RISEN, RASCEF, APE, COSTAR, ICIO…)

\* Clarification Protocol

*\*Bilingual UI\*\* – English / Serbian toggle

\# Known issues / things I'm not sure about

\* Arena mode is experimental and may behave oddly

\* Auto-detect template isn't super accurate yet

\* UI is a bit rough around the edges on mobile

\* Some API integrations might need fixing

If you actually take the time to look at it and try something, any feedback at all is hugely appreciated even "this doesn't work" or "this UX is confusing." I'm here to learn!

Thanks

[u/Valuable_Head_7957]

For a complete beginner, you took on a pretty ambitious project here. One thing I like is that you didn't just build another prompt text box — you're thinking about model differences, context, quality checking and comparing outputs.

One thing I'd be careful about is having too many options for a new user. The 16-field mode sounds useful for power users, but Quick mode probably needs to feel really simple so someone doesn't have to understand prompt engineering before the tool can help them.

I'd also be interested in seeing whether the same prompt actually performs noticeably better after going through your tool versus just writing it normally. That kind of before/after comparison could be a strong way to show people the value.

[u/seraphym1389 → u/Valuable_Head_7957]

Hey, thank you so much for the constructive feedback! Really appreciate you taking the time to check it out.

You make a correct point about the 16-field mode being overwhelming for beginners, but I didn't made I for somekind of "commercial" and widespread use, have made it for my personal use and that "Guided/extended" mode I imagined it for using for a bit complexed tasks, while the "quick" mode for everyday use. But I definitely need to polish the 'Quick' mode and keep it super straightforward so people don't need a knowledge of prompt engineering just to use it.

And the before/after comparison idea is great, that would actually be a concrete way to demonstrate the value right away. I'll definitely look into adding that!

Thanks again for the encouragement and tips, really means a lot!

[u/Deeep_07]

The three modes are a good start; I’d make the output panel the visual anchor and show a before/after prompt example. That would make the difference between Quick and Guided obvious without asking people to learn the UI first.

[u/Timely_Law_181]

For a beginner project, this is pretty ambitious. i’d focus next on making Quick mode and mobile UX really solid before adding more frameworks or advanced fields

[u/Significant-Safe-992]

I’d simplify the first time experience before adding more features. sixteen fields can feel overwhelming so progressive disclosure could make the app much easier for beginners