<?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: member_b03d2604</title>
    <description>The latest articles on DEV Community by member_b03d2604 (@member_b03d2604).</description>
    <link>https://dev.to/member_b03d2604</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%2F3846496%2Fa0d45b3e-d9d1-45cd-bb9e-82a80eb54fc6.png</url>
      <title>DEV Community: member_b03d2604</title>
      <link>https://dev.to/member_b03d2604</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/member_b03d2604"/>
    <language>en</language>
    <item>
      <title>5 AI Prompts I Actually Use in Production (And Where to Get More)</title>
      <dc:creator>member_b03d2604</dc:creator>
      <pubDate>Sun, 29 Mar 2026 03:41:06 +0000</pubDate>
      <link>https://dev.to/member_b03d2604/5-ai-prompts-i-actually-use-in-production-and-where-to-get-more-2cib</link>
      <guid>https://dev.to/member_b03d2604/5-ai-prompts-i-actually-use-in-production-and-where-to-get-more-2cib</guid>
      <description>&lt;p&gt;I've been collecting and refining AI prompts for the past year. Not the generic act-as-an-expert&lt;br&gt;
stuff â€” I mean prompts that I use daily in real production work. Here are 5 of them, plus info on the full pack.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Most Prompts Are Garbage
&lt;/h2&gt;

&lt;p&gt;The problem with most prompt lists is they're designed to impress in a screenshot, not to work reliably. A good prompt is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Specific about format&lt;/strong&gt; â€” tells the AI exactly how to structure output&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Scoped&lt;/strong&gt; â€” one job, not five&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Handles edge cases&lt;/strong&gt; â€” what should the AI do when it's unsure?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Here are 5 from my personal vault:&lt;/p&gt;




&lt;h3&gt;
  
  
  1. Code Review (Actually Useful)
&lt;/h3&gt;

&lt;p&gt;Review this code for: (1) bugs, (2) security issues, (3) performance bottlenecks, (4) anything that would fail code review at a senior level. For each issue: quote the line, explain why it's a problem, give the fix. Skip compliments.&lt;/p&gt;

&lt;p&gt;The 'skip compliments' line alone saves 40% of the output.&lt;/p&gt;




&lt;h3&gt;
  
  
  2. Debugging Unknown Errors
&lt;/h3&gt;

&lt;p&gt;I have this error: [error message]. Context: [language/framework, what you were doing]. I already tried: [what you tried]. Give me 3 ranked hypotheses for the root cause. For each: confidence %, why you think it, exact steps to verify. Start with most likely.&lt;/p&gt;

&lt;p&gt;Ranked hypotheses &amp;gt; here are some possibilities.&lt;/p&gt;




&lt;h3&gt;
  
  
  3. Architecture Decision
&lt;/h3&gt;

&lt;p&gt;I need to [describe the system requirement]. Constraints: [list real constraints â€” budget, team size, existing stack]. Give me 3 architecture options. For each: overview, pros, cons, what type of team/project it's best for, estimated complexity (1-10). End with a recommendation and why.&lt;/p&gt;




&lt;h3&gt;
  
  
  4. Rewrite for Clarity
&lt;/h3&gt;

&lt;p&gt;Rewrite this for a technical audience who are smart but unfamiliar with this specific domain. Keep all technical accuracy. Remove jargon where plain language works. Target: someone could read this once and explain it to a colleague.&lt;/p&gt;




&lt;h3&gt;
  
  
  5. Daily Standup Generator
&lt;/h3&gt;

&lt;p&gt;Turn these rough notes into a standup update. Format: Yesterday / Today / Blockers. Keep it under 5 sentences total. Tone: direct, no fluff. Notes: [your rough notes]&lt;/p&gt;




&lt;h2&gt;
  
  
  The Full Pack
&lt;/h2&gt;

&lt;p&gt;These 5 are from a set of 50 prompts I've compiled â€” covering code review, debugging, architecture, writing, product decisions, and more. Every prompt has been tested on real work, not demos.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://the-forge-ide-gamedev.itch.io/mariah" rel="noopener noreferrer"&gt;Get the full 50-prompt pack â€” $19&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If you only buy one productivity tool this year, make it something you'll actually use every day. These prompts are that.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>chatgpt</category>
      <category>promptengineering</category>
    </item>
    <item>
      <title>How I Built a Prison Escape Game in One Week with Unity NavMesh</title>
      <dc:creator>member_b03d2604</dc:creator>
      <pubDate>Sun, 29 Mar 2026 03:41:00 +0000</pubDate>
      <link>https://dev.to/member_b03d2604/how-i-built-a-prison-escape-game-in-one-week-with-unity-navmesh-522a</link>
      <guid>https://dev.to/member_b03d2604/how-i-built-a-prison-escape-game-in-one-week-with-unity-navmesh-522a</guid>
      <description>&lt;p&gt;I never planned on building a prison escape game. It started as a weekend project to mess around with Unity's NavMesh â€” but one week later I had a full stealth-survival alpha with reactive guard AI, a noise system, and an inventory. Here's how it happened.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Idea
&lt;/h2&gt;

&lt;p&gt;CLAWED puts you in the role of a prisoner trying to escape a maximum-security facility. Simple concept. But the moment I asked "what makes guards &lt;em&gt;feel&lt;/em&gt; smart?", everything got complicated.&lt;/p&gt;

&lt;h2&gt;
  
  
  Building the Guard AI
&lt;/h2&gt;

&lt;p&gt;The core of the game is a 4-state finite state machine for each guard:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Patrol&lt;/strong&gt; â€” follows a waypoint path, checks line-of-sight every 0.3s&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Suspicious&lt;/strong&gt; â€” heard a noise or caught movement; turns toward source, plays alert animation&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Chase&lt;/strong&gt; â€” full sprint using NavMeshAgent, broadcasts alert to nearby guards via event&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Attack&lt;/strong&gt; â€” triggers caught sequence if player is in range&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The hardest part wasn't the state transitions â€” it was making the AI &lt;em&gt;feel&lt;/em&gt; believable. Guards would teleport-turn to face you. The fix: lerping rotation toward suspicion source over 0.8 seconds. That single change made them feel alive.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight csharp"&gt;&lt;code&gt;&lt;span class="k"&gt;void&lt;/span&gt; &lt;span class="nf"&gt;UpdateSuspicion&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;Vector3&lt;/span&gt; &lt;span class="n"&gt;target&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;suspicionTarget&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="n"&gt;target&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="n"&gt;Quaternion&lt;/span&gt; &lt;span class="n"&gt;lookRot&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="n"&gt;Quaternion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;LookRotation&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;target&lt;/span&gt; &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="n"&gt;transform&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;position&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="n"&gt;transform&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;rotation&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="n"&gt;Quaternion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;Lerp&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;transform&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;rotation&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;lookRot&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;Time&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;deltaTime&lt;/span&gt; &lt;span class="p"&gt;*&lt;/span&gt; &lt;span class="m"&gt;2f&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Noise + Visibility System
&lt;/h2&gt;

&lt;p&gt;Two detection channels:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Visibility&lt;/strong&gt; â€” raycast from guard eyes, player visibility scaled by distance + light level&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Noise&lt;/strong&gt; â€” physics overlap sphere triggered by player actions (running = radius 8, crouch-walk = radius 1, crawl = 0)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Each guard has a suspicion meter (0-100). Visibility adds ~30/sec at close range, noise adds a flat spike based on radius overlap. Hit 100 = Chase.&lt;/p&gt;

&lt;h2&gt;
  
  
  Inventory System
&lt;/h2&gt;

&lt;p&gt;Kept it lean: 6 slots, item pickup via trigger zone, equip/unequip toggle. No drag-and-drop â€” keyboard slots only. Fast to build, fast to play.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where It's At
&lt;/h2&gt;

&lt;p&gt;CLAWED is in alpha right now â€” playable, rough around the edges, but the core loop works. You sneak, you get spotted, you run, you hide. There's a tension to it that surprised me.&lt;/p&gt;

&lt;p&gt;If you want to try it (or tear apart my code), grab the alpha here:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://the-forge-ide-gamedev.itch.io/clawed" rel="noopener noreferrer"&gt;Play CLAWED on itch.io â€” $10 alpha access&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Week 2 plan: patrol routes editor, camera system, level 2. Following along if you want to see how it breaks.&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>unity3d</category>
      <category>indiedev</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>I Launched My SaaS Product to 22 Different Audiences at Once Using HTML Templates</title>
      <dc:creator>member_b03d2604</dc:creator>
      <pubDate>Fri, 27 Mar 2026 16:28:09 +0000</pubDate>
      <link>https://dev.to/member_b03d2604/i-launched-my-saas-product-to-22-different-audiences-at-once-using-html-templates-3cl5</link>
      <guid>https://dev.to/member_b03d2604/i-launched-my-saas-product-to-22-different-audiences-at-once-using-html-templates-3cl5</guid>
      <description>&lt;p&gt;Most indie founders write one landing page and hope it resonates. I tried something different: I built 22 versions of the same landing page, each tuned for a completely different audience and platform. Here is what I learned.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Problem with One Landing Page
&lt;/h2&gt;

&lt;p&gt;Your product is the same. Your audience is not.&lt;/p&gt;

&lt;p&gt;A developer on Hacker News wants to know: does this solve a real technical problem, is it open source, what is the stack?&lt;/p&gt;

&lt;p&gt;A founder on Product Hunt wants: beautiful design, social proof, clear pricing, one-click CTA.&lt;/p&gt;

&lt;p&gt;A freelancer on Reddit wants: does this save me time, what is the ROI, can I try it free?&lt;/p&gt;

&lt;p&gt;The same copy that wins on HN will bomb on Product Hunt. So I stopped trying to write one page that works everywhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 22-Audience Strategy
&lt;/h2&gt;

&lt;p&gt;I built a pack of 22 HTML landing page templates, each designed for a specific context:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Hacker News launch post&lt;/strong&gt; — minimal, technical, no hype language&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Product Hunt&lt;/strong&gt; — visual, benefit-led, CTA above the fold&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reddit r/entrepreneur&lt;/strong&gt; — story-driven, honest about limitations&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;LinkedIn&lt;/strong&gt; — professional tone, ROI framing, case study format&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cold email landing&lt;/strong&gt; — short, single action, trust signals only&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AppSumo&lt;/strong&gt; — lifetime deal framing, feature checklist, urgency&lt;/li&gt;
&lt;li&gt;... and 16 more&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each template has the same core sections (headline, problem, solution, social proof, CTA) but different &lt;strong&gt;tone&lt;/strong&gt;, &lt;strong&gt;emphasis&lt;/strong&gt;, and &lt;strong&gt;structure&lt;/strong&gt; for that platform.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to Use This
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Pick your product&lt;/li&gt;
&lt;li&gt;List 5-10 channels where your audience lives&lt;/li&gt;
&lt;li&gt;Match each channel to the appropriate template&lt;/li&gt;
&lt;li&gt;Swap in your copy — each template has clearly labeled placeholder sections&lt;/li&gt;
&lt;li&gt;Deploy to Netlify/Vercel/GitHub Pages in under 10 minutes per page&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You now have a landing page optimized for each traffic source. When you post on HN, link to the HN version. When you run a LinkedIn ad, link to the LinkedIn version.&lt;/p&gt;

&lt;h2&gt;
  
  
  Does It Work?
&lt;/h2&gt;

&lt;p&gt;The conversion lift depends on your product, but the logic is sound: message-to-market fit matters at the page level, not just the ad level. If someone clicks an ad that speaks their language and then lands on a generic page, you have already lost them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Get the Templates
&lt;/h2&gt;

&lt;p&gt;All 22 templates are plain HTML/CSS — no frameworks, no build step, just edit and deploy. They work with any hosting platform.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://the-forge-ide-gamedev.itch.io" rel="noopener noreferrer"&gt;Browse all templates and products at the store&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The FORGE Landing Pack is available separately on Gumroad if you want just the templates. Each one is production-ready and has been tested on real launches.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>saas</category>
      <category>marketing</category>
      <category>html</category>
    </item>
    <item>
      <title>50 Claude &amp; ChatGPT Prompts That Actually Work in Production (Free Sample + Full Pack)</title>
      <dc:creator>member_b03d2604</dc:creator>
      <pubDate>Fri, 27 Mar 2026 16:28:07 +0000</pubDate>
      <link>https://dev.to/member_b03d2604/50-claude-chatgpt-prompts-that-actually-work-in-production-free-sample-full-pack-6be</link>
      <guid>https://dev.to/member_b03d2604/50-claude-chatgpt-prompts-that-actually-work-in-production-free-sample-full-pack-6be</guid>
      <description>&lt;p&gt;I've been collecting and refining AI prompts for the past year. Not the generic act-as-an-expert&lt;br&gt;
stuff — I mean prompts that I use daily in real production work. Here are 5 of them, plus info on the full pack.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Most Prompts Are Garbage
&lt;/h2&gt;

&lt;p&gt;The problem with most prompt lists is they're designed to impress in a screenshot, not to work reliably. A good prompt is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Specific about format&lt;/strong&gt; — tells the AI exactly how to structure output&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Scoped&lt;/strong&gt; — one job, not five&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Handles edge cases&lt;/strong&gt; — what should the AI do when it's unsure?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Here are 5 from my personal vault:&lt;/p&gt;




&lt;h3&gt;
  
  
  1. Code Review (Actually Useful)
&lt;/h3&gt;

&lt;p&gt;Review this code for: (1) bugs, (2) security issues, (3) performance bottlenecks, (4) anything that would fail code review at a senior level. For each issue: quote the line, explain why it's a problem, give the fix. Skip compliments.&lt;/p&gt;

&lt;p&gt;The 'skip compliments' line alone saves 40% of the output.&lt;/p&gt;




&lt;h3&gt;
  
  
  2. Debugging Unknown Errors
&lt;/h3&gt;

&lt;p&gt;I have this error: [error message]. Context: [language/framework, what you were doing]. I already tried: [what you tried]. Give me 3 ranked hypotheses for the root cause. For each: confidence %, why you think it, exact steps to verify. Start with most likely.&lt;/p&gt;

&lt;p&gt;Ranked hypotheses &amp;gt; here are some possibilities.&lt;/p&gt;




&lt;h3&gt;
  
  
  3. Architecture Decision
&lt;/h3&gt;

&lt;p&gt;I need to [describe the system requirement]. Constraints: [list real constraints — budget, team size, existing stack]. Give me 3 architecture options. For each: overview, pros, cons, what type of team/project it's best for, estimated complexity (1-10). End with a recommendation and why.&lt;/p&gt;




&lt;h3&gt;
  
  
  4. Rewrite for Clarity
&lt;/h3&gt;

&lt;p&gt;Rewrite this for a technical audience who are smart but unfamiliar with this specific domain. Keep all technical accuracy. Remove jargon where plain language works. Target: someone could read this once and explain it to a colleague.&lt;/p&gt;




&lt;h3&gt;
  
  
  5. Daily Standup Generator
&lt;/h3&gt;

&lt;p&gt;Turn these rough notes into a standup update. Format: Yesterday / Today / Blockers. Keep it under 5 sentences total. Tone: direct, no fluff. Notes: [your rough notes]&lt;/p&gt;




&lt;h2&gt;
  
  
  The Full Pack
&lt;/h2&gt;

&lt;p&gt;These 5 are from a set of 50 prompts I've compiled — covering code review, debugging, architecture, writing, product decisions, and more. Every prompt has been tested on real work, not demos.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://the-forge-ide-gamedev.itch.io/mariah" rel="noopener noreferrer"&gt;Get the full 50-prompt pack — $19&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If you only buy one productivity tool this year, make it something you'll actually use every day. These prompts are that.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>chatgpt</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
