<?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>Forem: Lasse Stilvang</title>
    <description>The latest articles on Forem by Lasse Stilvang (@lasse).</description>
    <link>https://forem.com/lasse</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F794850%2F5c349c03-c447-4a97-a767-6f996a9ac061.jpg</url>
      <title>Forem: Lasse Stilvang</title>
      <link>https://forem.com/lasse</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/lasse"/>
    <language>en</language>
    <item>
      <title>DustOff: Make Your Legacy Projects LLM-Ready</title>
      <dc:creator>Lasse Stilvang</dc:creator>
      <pubDate>Mon, 16 Feb 2026 03:16:18 +0000</pubDate>
      <link>https://forem.com/lasse/dustoff-make-your-legacy-projects-llm-ready-3g9l</link>
      <guid>https://forem.com/lasse/dustoff-make-your-legacy-projects-llm-ready-3g9l</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/github-2026-01-21"&gt;GitHub Copilot CLI Challenge&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

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

&lt;p&gt;As developers, we all have a graveyard of side projects we once loved - now buried in old frameworks, outdated configs, and half-forgotten architecture.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;DustOff&lt;/strong&gt; revives them.&lt;/p&gt;

&lt;p&gt;It migrates legacy projects into a modern &lt;strong&gt;Next.js + TypeScript&lt;/strong&gt; stack, standardizing structure and preparing them for today’s tooling - especially AI-assisted development.&lt;/p&gt;

&lt;p&gt;Instead of wrestling with old build systems and fragile code, you get a clean, predictable foundation ready for iteration.&lt;/p&gt;

&lt;p&gt;DustOff removes the friction of restarting.&lt;/p&gt;

&lt;p&gt;Unfinished ideas deserve a second chance - &lt;strong&gt;DustOff your side-projects.&lt;/strong&gt;&lt;/p&gt;

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

&lt;p&gt;Live Demo: &lt;strong&gt;&lt;a href="https://dust-off.vercel.app/" rel="noopener noreferrer"&gt;dust-off.vercel.app&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;GitHub Repo: &lt;strong&gt;&lt;a href="https://github.com/lassestilvang/dust-off" rel="noopener noreferrer"&gt;github.com/lassestilvang/dust-off&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Video: 

  &lt;iframe src="https://www.youtube.com/embed/XCbl1XY70DY"&gt;
  &lt;/iframe&gt;


&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8qx425rff83ayx7w5nh2.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8qx425rff83ayx7w5nh2.jpeg" alt="DustOff: Migration"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fsp3ekw738iin47muz1qv.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fsp3ekw738iin47muz1qv.jpeg" alt="DustOff: Report"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  My Experience with GitHub Copilot CLI
&lt;/h2&gt;

&lt;p&gt;Building DustOff felt like the perfect use case for GitHub Copilot CLI.&lt;/p&gt;

&lt;p&gt;Since DustOff is fundamentally about analyzing and transforming codebases, I naturally leaned on Copilot CLI directly in the terminal to accelerate development. Instead of context-switching to a browser or IDE, I could:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Generate migration scripts directly from file structures&lt;/li&gt;
&lt;li&gt;Refactor shell scripts and Node tooling inline&lt;/li&gt;
&lt;li&gt;Scaffold Next.js + TypeScript templates&lt;/li&gt;
&lt;li&gt;Quickly iterate on edge-case handling for different project layouts&lt;/li&gt;
&lt;li&gt;Generate commit messages and documentation from diffs&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What stood out most was how &lt;u&gt;Copilot CLI changed my flow state&lt;/u&gt;.&lt;/p&gt;

&lt;p&gt;Because it lives in the terminal, it felt like pair programming without breaking momentum. I could pipe files into it, ask for transformations, validate ideas, and refine scripts in tight feedback loops. It wasn’t just autocomplete - it was collaborative reasoning embedded in my workflow.&lt;/p&gt;

&lt;p&gt;For example, when designing the migration logic, I used Copilot CLI to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Analyze sample legacy project structures&lt;/li&gt;
&lt;li&gt;Suggest normalization strategies&lt;/li&gt;
&lt;li&gt;Refactor repetitive filesystem logic&lt;/li&gt;
&lt;li&gt;Improve TypeScript typings after initial scaffolding&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Instead of writing everything from scratch, I focused on architecture and intent, while Copilot accelerated implementation details.&lt;/p&gt;

&lt;p&gt;The biggest impact? &lt;u&gt;Speed without sacrificing control.&lt;/u&gt;&lt;/p&gt;

&lt;p&gt;Copilot CLI didn’t replace thinking - it amplified it. It allowed me to move from idea → working prototype significantly faster, especially when iterating on transformation logic and developer tooling.&lt;/p&gt;

&lt;p&gt;For a tool like DustOff - which is built for developers who love the terminal - using Copilot CLI felt like building the future with the future.&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>githubchallenge</category>
      <category>cli</category>
      <category>githubcopilot</category>
    </item>
  </channel>
</rss>
