<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Raushani Kumari</title>
    <description>The latest articles on DEV Community by Raushani Kumari (@raushanichaudhary77).</description>
    <link>https://dev.to/raushanichaudhary77</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4156480%2Fe7fe578e-7067-4a3a-9f0a-65d6b807966e.jpeg</url>
      <title>DEV Community: Raushani Kumari</title>
      <link>https://dev.to/raushanichaudhary77</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/raushanichaudhary77"/>
    <language>en</language>
    <item>
      <title>App Graveyard: find and bury the leftovers of uninstalled apps, judged by Gemma 3 on your own machine</title>
      <dc:creator>Raushani Kumari</dc:creator>
      <pubDate>Sat, 31 Oct 2026 12:57:58 +0000</pubDate>
      <link>https://dev.to/raushanichaudhary77/app-graveyard-find-and-bury-the-leftovers-of-uninstalled-apps-judged-by-gemma-3-on-your-own-1aph</link>
      <guid>https://dev.to/raushanichaudhary77/app-graveyard-find-and-bury-the-leftovers-of-uninstalled-apps-judged-by-gemma-3-on-your-own-1aph</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week4-2026-10-26"&gt;Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;A few weeks ago I set up a new Mac and did what everyone does with a new laptop: tried a pile of apps. A couple of browsers, a fancier terminal, a clipboard manager, two beta builds of things I already had. Most of them went to the Trash within days. The icons disappeared, so I assumed the apps had too.&lt;/p&gt;

&lt;p&gt;They hadn't. Each one had left a little pile of itself in &lt;code&gt;~/Library&lt;/code&gt;: preferences, caches, a log or two, sometimes a whole container. Nothing big. But it was sitting on a laptop that was four weeks old, and nothing was ever going to look at it again. That felt like the theme, so I ran with it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;App Graveyard&lt;/strong&gt; looks through your application-data folders, works out which leftovers still belong to an app you actually have, and hands the rest to a small open-weight model running on your own machine. The model's job is to say what the app was, who made it, and whether it's safe to put to rest. Every dead app gets a tombstone, a one-line reason, and an epitaph. The model writes the epitaphs, and some of them are better than I expected.&lt;/p&gt;

&lt;p&gt;"Bury" moves an app's folders into a quarantine with a manifest. "Restore" puts them back exactly where they were. There is no delete button anywhere, and that's deliberate.&lt;/p&gt;

&lt;p&gt;It runs on macOS, Windows and Linux, offline, with no API key. The only network call in the whole codebase goes to &lt;code&gt;127.0.0.1:11434&lt;/code&gt;, which is Ollama.&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/HYClrIPK-YQ" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Open &lt;a href="https://raushanichaudhary.github.io/app-graveyard/" rel="noopener noreferrer"&gt;https://raushanichaudhary.github.io/app-graveyard/&lt;/a&gt;&lt;/strong&gt; and follow the three one-time steps on the page. The page talks to a 1 MB helper on your own machine and runs the scan from there, so the site is the app, not a landing page for it. On macOS and Linux the install line registers the helper as a login service, and after that the page is just a Scan button. On Windows it's a single .exe.&lt;/p&gt;

&lt;p&gt;If you'd rather stay in a terminal, &lt;code&gt;python -m appgraveyard&lt;/code&gt; runs the same scan and opens the graveyard at &lt;code&gt;http://127.0.0.1:7777/&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;


&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/raushanichaudhary" rel="noopener noreferrer"&gt;
        raushanichaudhary
      &lt;/a&gt; / &lt;a href="https://github.com/raushanichaudhary/app-graveyard" rel="noopener noreferrer"&gt;
        app-graveyard
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      👻 The apps you uninstalled left ghosts behind. Finds leftover app data on your machine and asks a local open-weight model (Gemma via Ollama) what it was. Nothing is deleted, only buried.
    &lt;/h3&gt;
  &lt;/div&gt;
  &lt;div class="ltag-github-body"&gt;
    
&lt;div id="readme" class="md"&gt;&lt;div class="markdown-heading"&gt;
&lt;h1 class="heading-element"&gt;App Graveyard 👻&lt;/h1&gt;
&lt;/div&gt;
&lt;p&gt;&lt;strong&gt;The apps you uninstalled left ghosts behind.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Every app you ever installed and removed left folders in your application-data directories: caches, preferences, logs, containers. Uninstalling almost never cleans them up. App Graveyard finds those leftovers, works out which installed app each one belongs to, and asks an open-weight model running &lt;strong&gt;on your own machine&lt;/strong&gt; to identify the rest: what the app was, who made it, and whether it is safe to put to rest.&lt;/p&gt;
&lt;p&gt;Nothing is deleted. Ever. "Burying" a ghost moves its folder to a quarantine directory with a manifest, and one click restores it.&lt;/p&gt;
&lt;p&gt;No cloud, no API key, no telemetry. The only network call is to &lt;code&gt;127.0.0.1:11434&lt;/code&gt;, your local &lt;a href="https://ollama.com" rel="nofollow noopener noreferrer"&gt;Ollama&lt;/a&gt;.&lt;/p&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Run it&lt;/h2&gt;
&lt;/div&gt;
&lt;p&gt;&lt;strong&gt;Open the site: &lt;a href="https://raushanichaudhary.github.io/app-graveyard/" rel="nofollow noopener noreferrer"&gt;https://raushanichaudhary.github.io/app-graveyard/&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The page is the app. It walks you through three one-time steps (install Python 3, install Ollama, download and double-click the 1 MB helper), then connects…&lt;/p&gt;&lt;/div&gt;
  &lt;/div&gt;
  &lt;div class="gh-btn-container"&gt;&lt;a class="gh-btn" href="https://github.com/raushanichaudhary/app-graveyard" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;


&lt;p&gt;MIT. Python standard library only. The one thing you need besides Python is Ollama.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;p&gt;There are four stages, and only the last one is AI. Keeping it that way turned out to be the real lesson of the week: the model gives much better answers when the code has already done the boring, certain parts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Scan.&lt;/strong&gt; Look inside the folders where apps keep their data. On a Mac that is mostly &lt;code&gt;~/Library&lt;/code&gt; (Application Support, Caches, Preferences, Logs, Containers and a few more); on Windows it is &lt;code&gt;%APPDATA%&lt;/code&gt;, &lt;code&gt;%LOCALAPPDATA%&lt;/code&gt; and &lt;code&gt;ProgramData&lt;/code&gt;; on Linux &lt;code&gt;~/.config&lt;/code&gt;, &lt;code&gt;~/.cache&lt;/code&gt; and &lt;code&gt;~/.local/share&lt;/code&gt;. For every folder found there, note how big it is, how many files it has, when it was first and last touched, and a few of the file names inside. Nothing is modified at this stage.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Match, with no AI at all.&lt;/strong&gt; Make a list of the apps that are actually installed (on a Mac, the &lt;code&gt;.app&lt;/code&gt; bundles and Homebrew; on Windows, the registry's uninstall list, Program Files and Store apps; on Linux, desktop entries, dpkg, flatpak and whatever is on &lt;code&gt;$PATH&lt;/code&gt;). Then compare names: does this leftover folder look like it belongs to one of those apps? The one rule that mattered more than anything else: a word that three or more installed apps share is almost always a company name, and on its own it proves nothing. Without that rule, the leftover profile of an uninstalled browser can hide behind an unrelated app from the same company, just because both carry the company's name.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Group and protect.&lt;/strong&gt; One app usually leaves folders in several places. A clipboard manager might leave one in Application Support, one in Caches and one in Preferences; those get folded into a single entry with three parts, rather than three separate tombstones. Anything that belongs to the operating system itself is marked protected: it never goes to the model and can never be buried.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Consult the ghost.&lt;/strong&gt; Whatever is still unexplained goes to Gemma 3 4B through Ollama, four apps at a time, with the answer forced into JSON. For each app the model is told the folder names, where they are, how big and how old they are, a few file names inside, and which apps from the same company are still installed. It answers with the product name, the company, what kind of app it was, a verdict (&lt;code&gt;ghost&lt;/code&gt;, &lt;code&gt;keep&lt;/code&gt; or &lt;code&gt;unsure&lt;/code&gt;), how confident it is, a one-line reason and an epitaph. If it says ghost with less than 60% confidence, that becomes unsure, so the model can't bury something on a coin flip. If it skips an app in a batch, that app gets asked about again on its own.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;p&gt;I thought about this more than I expected to while building it. The input to this tool is a list of every application you have ever used, with paths, dates and file names. That is a pretty complete profile of a person. Sending it to a hosted model to ask "which of these are dead?" would be a strange trade: hand over the most detailed inventory of your digital life to free up a few hundred kilobytes.&lt;/p&gt;

&lt;p&gt;With an open-weight model it never leaves the laptop. A quantised 4B Gemma on a machine with 8 GB of RAM can recognise a clipboard manager from nothing but its bundle id, knows which vendor helpers are still needed by the apps that remain, and writes a little tombstone for each dead browser build. It does all of that offline, for free, and you can swap the model with one environment variable. The same tool built on a cloud API would need a key, a bill, and a privacy policy, and I don't think I'd have shipped it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Spirit of It
&lt;/h2&gt;

&lt;p&gt;Día de los Muertos is about remembering, not erasing. App Graveyard doesn't delete anything. It gives each dead app a marigold, a candle and a line of remembrance, and moves it to a quarantine you can reopen whenever you like. The ghost in your machine is just data nobody came back for.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Best Use of Gemma&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
      <category>ai</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Cyborg-Landing -page</title>
      <dc:creator>Raushani Kumari</dc:creator>
      <pubDate>Mon, 19 Oct 2026 11:49:58 +0000</pubDate>
      <link>https://dev.to/raushanichaudhary77/cyborg-landing-page-10bj</link>
      <guid>https://dev.to/raushanichaudhary77/cyborg-landing-page-10bj</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week2-2026-10-12"&gt;Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;I built &lt;strong&gt;NEON-X&lt;/strong&gt;, a futuristic, responsive cyborg-themed landing page that represents a fictional next-generation technology platform where humans and intelligent machines work together.&lt;/p&gt;

&lt;p&gt;The project features a cyberpunk-inspired interface with neon cyan and magenta colors, an animated cybernetic core, interactive technology cards, responsive navigation, and smooth CSS animations.&lt;/p&gt;

&lt;p&gt;NEON-X demonstrates how basic frontend technologies can be used to create an engaging and modern technology-focused user experience.&lt;/p&gt;

&lt;p&gt;The project could serve as a starting point for a futuristic technology brand or an interactive product landing page.&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;GitHub Repository:&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://raushanichaudhary77-create.github.io/Cyborg-Landing-Page" rel="noopener noreferrer"&gt;https://raushanichaudhary77-create.github.io/Cyborg-Landing-Page&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;

&lt;p&gt;Explore the complete source code on GitHub:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/raushanichaudhary77-create/Cyborg-Landing-Page" rel="noopener noreferrer"&gt;https://github.com/raushanichaudhary77-create/Cyborg-Landing-Page&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The project uses HTML5, CSS3, and Vanilla JavaScript.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;p&gt;I built NEON-X using three core web technologies:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;HTML5:&lt;/strong&gt; Structured the navigation bar, hero section, technology cards, about section, call-to-action section, and footer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CSS3:&lt;/strong&gt; Created the cyberpunk theme, neon glow effects, responsive layouts, animated rings, background grid, and hover effects.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vanilla JavaScript:&lt;/strong&gt; Added mobile navigation, interactive components, and the connection success message.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The project is organized into separate HTML, CSS, and JavaScript files, making it easy to understand and maintain.&lt;/p&gt;

&lt;p&gt;Currently, NEON-X does not integrate an open-weight AI model or local AI inference. Integrating an open-source AI capability is a potential future improvement.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;p&gt;Open innovation makes it easier for developers to share ideas, learn from existing work, experiment with new technologies, and collaborate with the community.&lt;/p&gt;

&lt;p&gt;By publishing NEON-X on GitHub, I make my source code accessible to other developers who can explore the implementation, learn from it, and build upon the project.&lt;/p&gt;

&lt;p&gt;In the future, I would like to explore integrating a locally running open-weight AI model to introduce intelligent features while giving users greater control over their data and model choices.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;p&gt;Not specified.&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>Touch-grass-ai</title>
      <dc:creator>Raushani Kumari</dc:creator>
      <pubDate>Sat, 10 Oct 2026 18:27:32 +0000</pubDate>
      <link>https://dev.to/raushanichaudhary77/touch-grass-ai-3kf9</link>
      <guid>https://dev.to/raushanichaudhary77/touch-grass-ai-3kf9</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week1-2026-10-05"&gt;Hacktoberfest Open-Source AI Challenge Week 1: Touch Grass&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Touch Grass AI&lt;/strong&gt; is an outdoor mission planner that gets people off their screens and into the world.&lt;/p&gt;

&lt;p&gt;Most of us know we should go outside more, but "go for a walk" is easy to ignore. Touch Grass AI turns that vague intention into a small, concrete &lt;strong&gt;mission&lt;/strong&gt;: you tell it how much time you have, what your surroundings are like and how you feel, and a local AI model plans a short outdoor mission you can start right now.&lt;/p&gt;

&lt;p&gt;It is for anyone who spends too much of the day at a screen: students, developers, remote workers, and anyone who keeps saying "I'll go out later".&lt;/p&gt;

&lt;p&gt;Key ideas:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Missions, not generic advice&lt;/strong&gt;: short, specific outdoor tasks instead of a vague nudge.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Private by design&lt;/strong&gt;: the AI runs on the same machine as the app. Nothing you type is sent to a closed AI service.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Simple and fast&lt;/strong&gt;: a clean interface that takes seconds to use, so the app does not become one more reason to stay on the screen.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;


&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/raushanichaudhary" rel="noopener noreferrer"&gt;
        raushanichaudhary
      &lt;/a&gt; / &lt;a href="https://github.com/raushanichaudhary/Challenge" rel="noopener noreferrer"&gt;
        Challenge
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      
    &lt;/h3&gt;
  &lt;/div&gt;
  &lt;div class="ltag-github-body"&gt;
    
&lt;div id="readme" class="md"&gt;&lt;div class="markdown-heading"&gt;
&lt;h1 class="heading-element"&gt;Touch Grass AI&lt;/h1&gt;
&lt;/div&gt;
&lt;p&gt;A calm, local-first outdoor activity planner. Pick the time, place, energy level, weather, and kind of activity that fits today to get three small, practical ideas. No account, subscription, API key, or external AI service is required.&lt;/p&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Requirements&lt;/h2&gt;
&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;Node.js 18 or newer&lt;/li&gt;
&lt;li&gt;Optional: &lt;a href="https://ollama.com/" rel="nofollow noopener noreferrer"&gt;Ollama&lt;/a&gt; with a model downloaded locally&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The app has no npm dependencies. Its built-in planner works without Ollama or an internet connection once the page has been opened and its static files cached.&lt;/p&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Start the app&lt;/h2&gt;
&lt;/div&gt;
&lt;p&gt;From this folder, run:&lt;/p&gt;
&lt;div class="highlight highlight-source-powershell notranslate position-relative overflow-auto js-code-highlight"&gt;
&lt;pre&gt;npm start&lt;/pre&gt;

&lt;/div&gt;
&lt;p&gt;Open &lt;a href="http://127.0.0.1:3000" rel="nofollow noopener noreferrer"&gt;http://127.0.0.1:3000&lt;/a&gt;. The server binds to loopback by default and serves the site only on your computer. Use &lt;code&gt;Ctrl+C&lt;/code&gt; in the terminal to stop it.&lt;/p&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Optional: enable local AI&lt;/h2&gt;

&lt;/div&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Install Ollama and download a model, for example:&lt;/p&gt;
&lt;div class="highlight highlight-source-powershell notranslate position-relative overflow-auto js-code-highlight"&gt;
&lt;pre&gt;ollama pull llama3.&lt;span class="pl-c1"&gt;2&lt;/span&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Start Ollama. Its default local API is &lt;code&gt;http://127.0.0.1:11434&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Copy &lt;code&gt;.env.example&lt;/code&gt; to &lt;code&gt;.env&lt;/code&gt; if you want to change the model…&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;&lt;/div&gt;
  &lt;/div&gt;
  &lt;div class="gh-btn-container"&gt;&lt;a class="gh-btn" href="https://github.com/raushanichaudhary/Challenge" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;


&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;


&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/raushanichaudhary" rel="noopener noreferrer"&gt;
        raushanichaudhary
      &lt;/a&gt; / &lt;a href="https://github.com/raushanichaudhary/Challenge" rel="noopener noreferrer"&gt;
        Challenge
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      
    &lt;/h3&gt;
  &lt;/div&gt;
  &lt;div class="ltag-github-body"&gt;
    
&lt;div id="readme" class="md"&gt;&lt;div class="markdown-heading"&gt;
&lt;h1 class="heading-element"&gt;Touch Grass AI&lt;/h1&gt;
&lt;/div&gt;
&lt;p&gt;A calm, local-first outdoor activity planner. Pick the time, place, energy level, weather, and kind of activity that fits today to get three small, practical ideas. No account, subscription, API key, or external AI service is required.&lt;/p&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Requirements&lt;/h2&gt;
&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;Node.js 18 or newer&lt;/li&gt;
&lt;li&gt;Optional: &lt;a href="https://ollama.com/" rel="nofollow noopener noreferrer"&gt;Ollama&lt;/a&gt; with a model downloaded locally&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The app has no npm dependencies. Its built-in planner works without Ollama or an internet connection once the page has been opened and its static files cached.&lt;/p&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Start the app&lt;/h2&gt;
&lt;/div&gt;
&lt;p&gt;From this folder, run:&lt;/p&gt;
&lt;div class="highlight highlight-source-powershell notranslate position-relative overflow-auto js-code-highlight"&gt;
&lt;pre&gt;npm start&lt;/pre&gt;

&lt;/div&gt;
&lt;p&gt;Open &lt;a href="http://127.0.0.1:3000" rel="nofollow noopener noreferrer"&gt;http://127.0.0.1:3000&lt;/a&gt;. The server binds to loopback by default and serves the site only on your computer. Use &lt;code&gt;Ctrl+C&lt;/code&gt; in the terminal to stop it.&lt;/p&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Optional: enable local AI&lt;/h2&gt;

&lt;/div&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Install Ollama and download a model, for example:&lt;/p&gt;
&lt;div class="highlight highlight-source-powershell notranslate position-relative overflow-auto js-code-highlight"&gt;
&lt;pre&gt;ollama pull llama3.&lt;span class="pl-c1"&gt;2&lt;/span&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Start Ollama. Its default local API is &lt;code&gt;http://127.0.0.1:11434&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Copy &lt;code&gt;.env.example&lt;/code&gt; to &lt;code&gt;.env&lt;/code&gt; if you want to change the model…&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;&lt;/div&gt;
  &lt;/div&gt;
  &lt;div class="gh-btn-container"&gt;&lt;a class="gh-btn" href="https://github.com/raushanichaudhary/Challenge" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;


&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;p&gt;The project is a full-stack web app built around a &lt;strong&gt;locally running open-weight model&lt;/strong&gt;, with no closed AI APIs anywhere in it.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Frontend&lt;/strong&gt;: React + Vite + Tailwind CSS, with Lucide icons.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Backend&lt;/strong&gt;: Node.js + Express. The server receives the user's input, builds the prompt and returns the generated mission.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AI engine&lt;/strong&gt;: &lt;strong&gt;node-llama-cpp&lt;/strong&gt; runs an open-weight model (Llama family, GGUF format) directly inside the Node.js server. There is no separate AI service to install or manage.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The path to this setup took a few steps. I started with Ollama as the AI engine, then tried running a model in the browser with WebLLM, and finally moved everything to Node.js so the whole app runs from one server with one &lt;code&gt;npm&lt;/code&gt; workflow. That keeps setup simple for contributors, and open-source AI stays at the core of the project.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;About AI tools:&lt;/strong&gt; the app's runtime AI is open-weight and runs locally. I also used an AI assistant (Claude, which is not open-weight) to help generate the first version of the project code.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;p&gt;A mission planner only works if people actually use it, and people are more willing to share how they feel and where they are when the data stays with them.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Privacy&lt;/strong&gt;: because the model is open-weight and runs locally through node-llama-cpp, your mood, schedule and surroundings never leave your machine. A closed API would require sending them to someone else's servers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No keys, no bills, no rate limits&lt;/strong&gt;: anyone can clone the repo and run it for free, including students without a credit card.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Works offline&lt;/strong&gt;: once the model is downloaded, the app does not need an internet connection to plan a walk.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Swap the model&lt;/strong&gt;: because the engine reads standard GGUF files, contributors can try a smaller or larger open model, or one fine-tuned for a different region or language, with a small config change.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hackable by anyone&lt;/strong&gt;: the prompts, the server and the UI are all open, so the community can make missions friendlier, funnier or more local.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>kitchen-allergy-planner</title>
      <dc:creator>Raushani Kumari</dc:creator>
      <pubDate>Sun, 04 Oct 2026 19:34:17 +0000</pubDate>
      <link>https://dev.to/raushanichaudhary77/kitchen-allergy-planner-mjn</link>
      <guid>https://dev.to/raushanichaudhary77/kitchen-allergy-planner-mjn</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-weekend-2026-10-01"&gt;Hacktoberfest Weekend Challenge: Build for a Friend&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Kitchen Allergy Planner&lt;/strong&gt; is a dark, futuristic food-tech web app that helps people plan meals around their food allergies.&lt;/p&gt;

&lt;p&gt;I built it for a close friend who has to avoid certain foods because of allergies. Every week they repeat the same routine: reading ingredient lists, double-checking recipes, and worrying that one planned meal might hide an ingredient they must avoid. Most recipe sites and meal planners treat allergies as an afterthought, so I wanted a planner that starts with the allergy profile instead.&lt;/p&gt;

&lt;p&gt;What it does:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Allergy profile&lt;/strong&gt;: pick from 16 allergens across 6 categories (Dairy, Eggs, Nuts, Gluten, Seafood, Other).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Recipe discovery&lt;/strong&gt;: search by name, ingredient or cuisine, filter (Safe, Contains Allergens, Vegetarian, High Protein, Quick Meals) and sort.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"Why?" explanations&lt;/strong&gt;: an unsafe recipe doesn't just say "unsafe". It shows exactly which ingredients matched your profile, for example &lt;em&gt;"Contains 2 ingredients from your allergy profile: cream (Milk), parmesan cheese (Cheese)."&lt;/em&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Weekly meal planner&lt;/strong&gt;: 7 days x 4 meals, with a live &lt;strong&gt;Weekly Safety Check&lt;/strong&gt; showing how many meals are compatible and which ones need attention.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ingredient Safety Scanner&lt;/strong&gt;: type &lt;code&gt;milk, rice, tomato, peanuts&lt;/code&gt; and see which ingredients match your profile.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Saved recipes&lt;/strong&gt;, toast notifications, and a responsive layout with a sidebar on desktop and bottom navigation on mobile.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Local-first&lt;/strong&gt;: everything is saved in the browser with &lt;code&gt;localStorage&lt;/code&gt;, so there is no account and no data leaves the device.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The app avoids medical claims and shows this disclaimer: &lt;em&gt;"Always verify ingredient labels and cross-contamination information. This application is for meal organization and educational purposes only and does not replace professional medical advice."&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Live demo:&lt;/strong&gt; &lt;a href="https://raushanichaudhary77-create.github.io/kitchen_allergy_planner/" rel="noopener noreferrer"&gt;https://raushanichaudhary77-create.github.io/kitchen_allergy_planner/&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;


&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/raushanichaudhary" rel="noopener noreferrer"&gt;
        raushanichaudhary
      &lt;/a&gt; / &lt;a href="https://github.com/raushanichaudhary/kitchen_allergy_planner" rel="noopener noreferrer"&gt;
        kitchen_allergy_planner
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      🥗 A modern allergy-aware meal planning web app to manage allergies, discover compatible recipes, plan weekly meals, and generate smart shopping lists — built with a futuristic Food-Tech UI
    &lt;/h3&gt;
  &lt;/div&gt;
  &lt;div class="ltag-github-body"&gt;
    
&lt;div id="readme" class="md"&gt;&lt;div class="markdown-heading"&gt;
&lt;h1 class="heading-element"&gt;🥗 Kitchen Allergy Planner&lt;/h1&gt;
&lt;/div&gt;
&lt;p&gt;A dark, futuristic food-tech web app that helps you plan meals around your food allergies
Built with plain HTML, CSS and JavaScript (Tailwind via CDN). No backend, no build step.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Always verify ingredient labels and cross-contamination information. This application is for meal organization and educational purposes only and does not replace professional medical advice.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Features&lt;/h2&gt;
&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;Allergy profile with 16 allergens in 6 categories&lt;/li&gt;
&lt;li&gt;Recipe search, filters (Safe, Vegetarian, High Protein, Quick Meals) and sorting&lt;/li&gt;
&lt;li&gt;"Why?" panel that shows exactly which ingredients match your allergies&lt;/li&gt;
&lt;li&gt;Weekly meal planner (7 days x 4 meals) with a Weekly Safety Check&lt;/li&gt;
&lt;li&gt;Ingredient Safety Scanner&lt;/li&gt;
&lt;li&gt;Saved recipes, toast notifications, responsive layout&lt;/li&gt;
&lt;li&gt;Everything saved in your browser with localStorage&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Project structure&lt;/h2&gt;

&lt;/div&gt;
&lt;div class="snippet-clipboard-content notranslate position-relative overflow-auto"&gt;&lt;pre class="notranslate"&gt;&lt;code&gt;kitchen-allergy-planner/
├── index.html   # page layout
├── style.css    # custom styles (glass, glow, animations)
├── script.js    # data, state, views and events
└── README.md
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;How to run&lt;/h2&gt;

&lt;/div&gt;
&lt;ol&gt;
&lt;li&gt;Download or clone this…&lt;/li&gt;
&lt;/ol&gt;&lt;/div&gt;
  &lt;/div&gt;
  &lt;div class="gh-btn-container"&gt;&lt;a class="gh-btn" href="https://github.com/raushanichaudhary/kitchen_allergy_planner" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;


&lt;p&gt;Project structure:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;kitchen_allergy_planner/
├── index.html   # page layout
├── style.css    # glass, glow and animation styles
├── script.js    # data, state, views and events
└── README.md
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;p&gt;The app is plain &lt;strong&gt;HTML, CSS and JavaScript&lt;/strong&gt; with &lt;strong&gt;Tailwind CSS (via CDN)&lt;/strong&gt;. There is no backend and no build step, so a beginner can open &lt;code&gt;index.html&lt;/code&gt; and start contributing right away.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Data&lt;/strong&gt;: allergens and recipes live in two simple arrays in &lt;code&gt;script.js&lt;/code&gt;. Each allergen has a list of keywords (for example, Wheat matches &lt;code&gt;pasta&lt;/code&gt;, &lt;code&gt;bread&lt;/code&gt;, &lt;code&gt;flour&lt;/code&gt;, &lt;code&gt;tortilla&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Matching&lt;/strong&gt;: each recipe ingredient is compared against the keywords of every allergen the user selected. The matches power the "Why?" panel, the planner warnings and the dashboard stats.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;State&lt;/strong&gt;: one small state object (allergies, favorites, meal plan) is saved to &lt;code&gt;localStorage&lt;/code&gt;, and the UI re-renders from it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Real stats&lt;/strong&gt;: dashboard numbers such as Safe Recipes and Meals Planned are computed from the current state, not hard-coded.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;About AI:&lt;/strong&gt; the allergen matching is simple keyword logic that runs in the browser. The app uses no AI model at runtime. I used an AI assistant (Claude, which is not open-weight) to help generate the first version of the code, and I then set up the project and repository myself.&lt;/p&gt;

&lt;p&gt;Because matching is keyword-based, it can miss unusual ingredient names. That is why the app always tells users to verify labels.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;p&gt;Food allergies are personal, and the data about them is sensitive. Building this as an open-source, local-first project means:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Privacy by default&lt;/strong&gt;: the allergy profile never leaves the user's browser. There is no API, no account and no tracking.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Anyone can improve it&lt;/strong&gt;: a recipe, an allergen keyword or a translation is a one-line change in a plain file. People in different countries can add the foods and ingredient names that matter in their own kitchens.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Transparent logic&lt;/strong&gt;: anyone can read exactly how a recipe is flagged, instead of trusting a black box with something that affects their health.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Free to fork&lt;/strong&gt;: a friend, a family or a community can adapt it to their own needs without asking anyone's permission.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devchallenge</category>
      <category>weekendchallenge</category>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>NEW TO COMMUNITY😊😊.....</title>
      <dc:creator>Raushani Kumari</dc:creator>
      <pubDate>Fri, 02 Oct 2026 17:14:19 +0000</pubDate>
      <link>https://dev.to/raushanichaudhary77/new-to-community-2c8b</link>
      <guid>https://dev.to/raushanichaudhary77/new-to-community-2c8b</guid>
      <description></description>
    </item>
  </channel>
</rss>
