u/Agitated-Touch8494

Image 1 — Got rejected 3 times over 17 days for my Chrome extension. So I built a tool to stop this from happening to others.
Image 2 — Got rejected 3 times over 17 days for my Chrome extension. So I built a tool to stop this from happening to others.
Image 3 — Got rejected 3 times over 17 days for my Chrome extension. So I built a tool to stop this from happening to others.

Got rejected 3 times over 17 days for my Chrome extension. So I built a tool to stop this from happening to others.

A few months ago I built Voxfile — a Chrome extension I was genuinely excited about. Spent weeks on it. Finally packaged it up and submitted to the Chrome Web Store.

Then the waiting game started.

Day 5 — rejection email. Reason: manifest.json permissions were too broad. Fair enough, I fixed it and resubmitted.

Day 11 — another rejection. This time the store listing description length was out of compliance. I didn't even know there were character rules. Fixed, resubmitted.

Day 17 — rejected again. Different description issue this time, in the actual listing copy on the developer dashboard.

17 days. Three rejections. Each one for something a static check could have caught in 30 seconds before I ever hit submit.

And the worst part wasn't the time — it was what happened to my motivation. By day 17 I barely cared about Voxfile anymore. That submission cycle quietly killed the momentum I'd built over weeks of actual work.

I'm pretty sure this is not a unique story.

So I built ExtGuard — a pre-submission validator for Chrome extensions. You drop your .zip into the browser, it runs 25 policy checks locally (your code never leaves your machine), and in ~30 seconds you get a report showing exactly what Google's review system would reject you for — with the specific policy reference and a fix recommendation.

It catches the things that burned me:

  • Manifest V3 compliance
  • Permission scope issues (<all_urls> when you only need one domain, etc.)
  • eval() / new Function() calls buried in minified code
  • Inline scripts violating CSP
  • Privacy policy URL missing or pointing to the wrong page
  • Description length and quality issues
  • Icon sizes not physically present in the zip
  • ...and 18 more checks

The scan engine is 100% client-side (nothing leaves your browser). I made that call specifically because I'd never upload my unreleased extension source to a random SaaS — so I didn't build one that asks you to.

Free tier: 5 Scans in total, 25 core checks. Pro ($9/mo): unlimited scans, all 25+ checks, line-level code context, PDF reports, CI/CD API. There's also a $4.99 one-time scan if you just want to check before launch with no subscription.

If this could've saved even one person's 17 days, it's worth posting. Would genuinely love feedback from this community — you're exactly the people who know where the gaps are.
https://www.extguard.online/

u/Agitated-Touch8494 — 21 hours ago
▲ 1 r/swiggy

Regarding Swiggy builders club program

Is anyone of you know how much time it will take to get credentials from Swiggy builders club?

I have submitted the form for my SaaS Nutriguard (health tracker built on top of Swiggy MCP) a week ago. But didn't get any response from Swiggy team.

What to do?

reddit.com
u/Agitated-Touch8494 — 24 hours ago

People are still using ChatGPT like Google search

One thing I’ve noticed while using ChatGPT heavily for technical learning is that most disappointing answers come from vague inputs rather than weak models.

A lot of prompts look like:

  • “Teach me React”
  • “Explain APIs”
  • “Help me debug this”

The model responds correctly, but the output becomes generic because the request itself lacks:

  • context
  • constraints
  • desired depth
  • target outcome

Small changes in phrasing drastically improve results.

For example:

Instead of:

>

Something like:

>

…usually produces much more useful responses.

Same model, completely different outcome.

It feels like interacting with AI is becoming less about “searching” and more about communicating requirements clearly.

Curious whether others have noticed the same thing.

reddit.com
u/Agitated-Touch8494 — 1 day ago
▲ 4 r/chrome_extensions+1 crossposts

I got tired of weak ChatGPT prompts, so I built a Chrome extension to fix it (PromptForge)

I’m a 21-year-old software developer from an IIT, and I spend a huge amount of time using ChatGPT for studying, coding, and learning new things.

One thing that kept frustrating me was this:

The quality of ChatGPT’s answer heavily depends on the quality of the prompt.

Sometimes I’d ask something technical, and instead of going deep, it would just give surface-level topic names or explain something completely different from what I actually wanted.

I also don’t enjoy sitting through long YouTube tutorials, so I rely a lot on AI for learning.

So I built PromptForge — a Chrome extension made specifically for ChatGPT that instantly enhances your prompts into more detailed, high-value prompts before sending them.

Features

  • Enhances prompts in ~3–5 seconds
  • Generates more structured and deeper AI responses
  • Stores enhanced prompt history locally using Chrome storage
  • Works directly inside ChatGPT

It just got published on the Chrome Web Store today after surviving one rejection 😭

Would genuinely love feedback from people who use AI heavily for coding/studying.

Chrome Store link: https://chromewebstore.google.com/detail/promptforge-%E2%80%94-ai-prompt-e/mhjailanhenjkhjgkjakoobkmgjpkgjp?authuser=0&hl=en-GB&utm_source=chatgpt.com

Would also love suggestions on:

  • features you’d actually use
  • what annoys you most while prompting AI
  • whether this should stay ChatGPT-only or support Claude/Gemini too
u/Agitated-Touch8494 — 1 day ago

Need help and advice

Hey all!
I have built my first chrome extension ( PromptForge- AI prompt enhancer), i tested it and submitted it on the chrome web dashboard, after three days i got a rejection email because of a very small thing in my privacy policy. On the same day I re-submitted it and it's not still got approval. It's now 5 days.
I don't know what to do?
Does web store usually takes this much of time or web is treating me specially?
Have anyone of you faced the same?

reddit.com
u/Agitated-Touch8494 — 2 days ago

I spent weeks testing why ChatGPT ignores instructions

I spent weeks testing why ChatGPT ignores instructions.

The biggest anti-patterns I found:

  • Huge walls of text
  • Conflicting instructions
  • “Write professionally”
  • No output format
  • Generic prompts like “don’t hallucinate”

The weird discovery:
Prompting works better when you treat it like writing an API contract instead of chatting casually.

I built these rules into a Chrome extension I’ve been working on called PromptForge.

Looking for a few heavy ChatGPT users who enjoy breaking products.

reddit.com
u/Agitated-Touch8494 — 5 days ago

I spent weeks testing why ChatGPT ignores instructions

I spent weeks testing why ChatGPT ignores instructions.

The biggest anti-patterns I found:

  • Huge walls of text
  • Conflicting instructions
  • “Write professionally”
  • No output format
  • Generic prompts like “don’t hallucinate”

The weird discovery:
Prompting works better when you treat it like writing an API contract instead of chatting casually.

I built these rules into a Chrome extension I’ve been working on called PromptForge.

Looking for a few heavy ChatGPT users who enjoy breaking products.

reddit.com
u/Agitated-Touch8494 — 5 days ago
▲ 2 r/PromptEngineering+1 crossposts

Why longer ChatGPT prompts often give worse results

I realized most bad ChatGPT outputs are caused by bad instruction structure, not the model itself.

The framework that improved my prompts the most:

  • Context → who the AI is
  • Rules → hard constraints
  • Examples → tone anchors
  • Format → exact output structure

The biggest mistake:
People keep adding more instructions when the output gets worse.

Usually shorter + clearer prompts work better.

I got tired of rewriting prompts manually every day, so I built a small Chrome extension that restructures them automatically while using ChatGPT.

Still waiting on Chrome approval, but curious if anyone else noticed prompt quality dropping with longer prompts.

reddit.com
u/Agitated-Touch8494 — 5 days ago

Small business owners were telling me the same problem every time I talked to them.

They post on Instagram Stories. People watch. People are interested. But they say "DM us" — and most people just scroll away without ever DMing.

So I built Flowlink — a simple link that goes in your Story. Customer taps it, enters their WhatsApp number, and instantly gets your product info automatically. Business gets the lead in a clean dashboard.

Just went live with a landing page: https://storysync.base44.app/

Would love honest feedback on the concept — is this something small businesses would actually pay for?

u/Agitated-Touch8494 — 14 days ago