DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to add a new lab to the Discover AI app with AI Learning Guide

Generate a lab folder with the project script, then run the checks before opening a pull request.

  • Research
  • Advanced
  • 60 minutes
  • From the README
  • Any agent

Who it is forA developer or AI educator who wants to contribute a new lab on a topic the app does not yet cover.

The problemCreating a lab from scratch means matching the app's structure and content rules, which is easy to get wrong.

The outcomeA new lab folder exists in src/modules/, passes the checks, and is ready for a pull request or issue discussion.

What you need first

  • A modern web browser for the hosted version, with no install needed
  • For the desktop or local setup: Node.js 20.19 or newer (22 or newer is best) and Git
  • For the desktop app build: Rust and the Tauri prerequisites for your system
  • For the optional local AI guide: about 1.3 GB of disk space for the Qwen3.5 2B model

Steps

  1. Open an issue first to talk about the new lab, as the README asks for new labs.
  2. Run npm run new:module -- my-new-lab
  3. Write the lab's interactive, lessons and checkpoint, following docs/MODULE_AUTHORING.md and docs/CONTENT_STYLE_GUIDE.md.
  4. Run npm run check:modules and then npm run check
  5. Fork the repo, commit on a new branch, and open a pull request.

Prompt for your agent

In a local clone of Fazmin/AILearningGuide, run npm run new:module -- <lab-name> and then npm run check:modules. Expected output: a new folder under src/modules/<lab-name> and a passing module check. Verify that npm run check reports no errors before any commit.

Caveat. The README says the app finds new labs on its own, but the lab should first be discussed in an issue, since new labs need an issue before work starts.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page