AI Prompt Genius: a Chrome extension for curating a custom prompt library

What AI Prompt Genius solves, and for whom

Most people who use ChatGPT regularly end up with the same problem: the prompts that worked are scattered across chat history, text files, and memory. AI Prompt Genius is a Chrome extension that addresses that by letting you "curate a custom library of AI Prompts", in the README's phrasing. The library lives in the browser extension rather than in a separate web app, so the act of saving and reusing a prompt happens in the same window where you are already working.

The intended user is an individual knowledge worker, not a team. Nothing in the README describes shared libraries, roles, or an organisational account. Syncing exists, and it runs through Google Auth, which is the reason the project gives for Firefox being unsupported. That single design decision tells you most of what you need to know about the target audience: someone with a Google account, on Chrome, who wants their prompts to follow them between machines.

If your prompts are short one-liners, the overhead of a library is not worth it. The extension earns its place when you have prompts long enough that retyping them is annoying, and when you want to find them by name later.

How the extension is put together

The repository is a Vite-built React application written in TypeScript. The package name is prompt-genius-v4, and the tech stack section of the README names React, Tailwind CSS, and DaisyUI. The build script runs `tsc --noEmit` before `vite build`, so a type error stops the build rather than shipping.

Persistence is handled by Dexie, a wrapper around IndexedDB, which is what you would expect for a browser extension that needs to store a local library larger than localStorage comfortably allows. State management uses Zustand. The prompt editor is built on Lexical, the same editor framework Meta maintains, which suggests prompts are treated as rich text rather than plain strings. CSV import and export come from papaparse, and virtualised list rendering comes from virtua, which matters if a library grows into the thousands of entries.

The repository layout shows two output targets: a plugin/ directory with its own changelog, and a worker/ directory. The README does not explain what the worker does, so treat any claim about background sync as unverified. What is documented is the split between the extension UI and a build script, build_plugin.sh, which produces the packaged extension.

Installing AI Prompt Genius from the Chrome Web Store

The README gives exactly one installation path for end users: the Chrome Web Store listing. There is no documented sideloading procedure, and no published build artefact in the release list that a user could install directly. The most recent release is tagged v3.2.9_final_legacy, and the name suggests the packaged releases are not the current line of development.

Open the store listing and add the extension to Chrome. The README links to it here:

https://chrome.google.com/webstore/detail/chatgpt-history/jjdnakkfjnnbbckhifcfchagnpofjffo/

After installation, the extension appears in the Chrome toolbar. Signing in with Google is what enables syncing across devices, and it is also the reason the project gives for not supporting Firefox. If you skip sign-in, expect the library to stay local to that browser profile.

Building from source is a separate exercise. The repository is a standard Vite project, and the scripts block in package.json is the only documented set of entry points:

{
  "dev": "vite",
  "build": "tsc --noEmit && vite build",
  "typecheck": "tsc --noEmit",
  "test": "vitest run",
  "css": "npx tailwindcss -i ./input.css -o ./src/App.css --minify",
  "lint": "npx prettier src/ plugin/ --write",
  "preview": "vite preview"
}

Those entries are copied from the scripts field in package.json. The README does not document what build_plugin.sh produces, where the output lands, or how to load it as an unpacked extension. That is a gap if you intend to modify the code rather than just use it.

Where AI Prompt Genius is the wrong tool

Firefox users are excluded by design. The README states that Firefox is not supported due to Google Auth for syncing, and that is not a temporary gap you can work around with a flag. If your team standardises on Firefox, this extension is not a candidate regardless of how good the prompt library is.

The licence is the second constraint. The repository is licensed under CC BY-NC-SA 4.0, which is a Creative Commons licence rather than a software licence. The NonCommercial clause restricts commercial use, and ShareAlike means derivative works must carry the same licence. For an individual using the extension in a browser, this is unlikely to matter. For a company that wants to fork the extension, embed it in a product, or ship a modified version internally, the terms are materially different from MIT or Apache 2.0, and the README's attribution requirement asks for a specific comment block in a prominent file. This is not legal advice; if the commercial question is live for you, read the licence text itself.

The third limitation is durability of the data. The README does not document what happens to your library if you uninstall the extension, clear browser storage, or lose access to the Google account used for sync. There is no documented export path in the README even though papaparse is a dependency, which implies CSV handling exists somewhere in the UI. Verify that yourself before you invest hours in building a library.

AI Prompt Genius compared with storing prompts in a notes app

The obvious alternative is not another prompt manager. It is a plain notes app, or a text file in a synced folder. The difference is in where the prompt has to travel. A notes app requires you to switch windows, find the note, copy the text, and paste it into the chat box. AI Prompt Genius puts the library inside the browser, which removes the window switch and, more importantly, the search step, because the list is rendered with virtualisation and can be filtered as you type.

That advantage shrinks if your prompts are few. A dozen prompts fit in a pinned note. The extension starts to pay off somewhere past the point where scrolling a note becomes slower than typing the prompt again.

The second difference is structure. A notes app stores text. Lexical as the editor dependency suggests prompts are stored as structured rich text, which is what allows per-prompt metadata, tags, or formatting to survive. Whether the current UI exposes that structure is not documented in the README, and the repository's descriptions/ directory suggests prompt content ships with the extension, but the README does not describe a browsing interface for it.

A third option worth naming is building your own with IndexedDB and a small React app. You would get exactly the data model you want, but you would also own the Google Auth integration, the store review process, and the update cycle. For most individuals, that trade is not worth making.

Maintenance, upgrades, and what the licence asks of you

The last push to the repository was on 2026-09-07, which is recent. The release list, however, stops at v3.2.9_final_legacy from 2023-11-24, and the tag itself says legacy. The gap between the two dates is the interesting signal: commits are landing, but tagged releases are not, and the package.json version is 0.0.0, which is the Vite template default rather than a real version number. If you depend on release artefacts, there is nothing current to depend on.

Upgrade cost for a user is close to zero. Chrome extensions update themselves, and the README describes no manual upgrade procedure. The risk is on the other side: an extension that updates silently can change or remove a feature you relied on, and there is no documented changelog for the extension itself, only plugin_changelog.md, which covers the plugin directory rather than the whole product.

For anyone building from source, the toolchain is conventional and current: TypeScript 5.9, Vite 4, React 18, Vitest for tests. There is a test script, but the README does not state what the tests cover or whether they run in CI. The repository contains a .claude/ directory and a PRODUCTION-HANDOFF.md file, neither of which the README explains; they are worth reading before you assume the project has a documented release process.

On the licence, the practical points are the attribution block the README asks you to include in a prominent file, the NonCommercial restriction, and the ShareAlike requirement on derivatives. Those three terms are what separate this from a permissive software licence, and they apply to the code, not to the prompts you write yourself.

Editorial conclusion

Adopt AI Prompt Genius if you write prompts repeatedly and want them in a browser sidebar rather than a notes app, and if Chrome is your daily browser. Do not adopt it if you work in Firefox, since the README states Firefox is not supported due to Google Auth for syncing, or if you need a library you can run on your own servers. Before committing, verify three things: that the extension is still installable from the Chrome Web Store listing, that your prompts export cleanly, and that the CC BY-NC-SA 4.0 licence fits how you intend to use the code.

Frequently asked questions

Official sources

1. AI-Prompt-Genius/AI-Prompt-Genius on GitHub
2. Issues
3. Project website
4. README
5. Releases