<?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>PromptZone - AI Prompts, Guides and Tools for Builders: Jennifer Jasmine</title>
    <description>The latest articles on PromptZone - AI Prompts, Guides and Tools for Builders by Jennifer Jasmine (@caninecalc).</description>
    <link>https://www.promptzone.com/caninecalc</link>
    <image>
      <url>https://promptzone-community.s3.amazonaws.com/uploads/user/profile_image/40247/5d26bf72-a4e4-4a3b-b9e6-9daf3e92889f.png</url>
      <title>PromptZone - AI Prompts, Guides and Tools for Builders: Jennifer Jasmine</title>
      <link>https://www.promptzone.com/caninecalc</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.promptzone.com/feed/caninecalc"/>
    <language>en</language>
    <item>
      <title>How I Use AI Prompts to Ship Free Pet-Care Calculators</title>
      <dc:creator>Jennifer Jasmine</dc:creator>
      <pubDate>Tue, 20 Oct 2026 00:09:14 +0000</pubDate>
      <link>https://www.promptzone.com/caninecalc/how-i-use-ai-prompts-to-ship-free-pet-care-calculators-37gb</link>
      <guid>https://www.promptzone.com/caninecalc/how-i-use-ai-prompts-to-ship-free-pet-care-calculators-37gb</guid>
      <description>&lt;p&gt;I run a small project called CanineCalc that publishes free dog calculators and research-backed care guides — puppy weight and size estimators, calorie and feeding calculators, a crate size finder, and more.&lt;/p&gt;

&lt;p&gt;Most of the tooling gets prototyped with a repeatable prompt workflow before I write production code. Here is the version I keep coming back to:&lt;/p&gt;

&lt;h2 id="1-spec-first-code-second"&gt;
  
  
  1. Spec first, code second
&lt;/h2&gt;

&lt;p&gt;My opening prompt never asks for code. It asks the model to write a plain-English spec: inputs, outputs, edge cases, and the formulas the calculator needs. Reviewing that spec first catches most of the mistakes that would otherwise hide inside generated code.&lt;/p&gt;

&lt;h2 id="2-make-the-model-state-its-assumptions"&gt;
  
  
  2. Make the model state its assumptions
&lt;/h2&gt;

&lt;p&gt;Pet care is full of rules of thumb that change by breed, age, and activity level. I prompt the model to list every assumption it bakes into a formula and to flag anything it is uncertain about. The flagged items become the parts I research and pin down myself, which keeps the final tool honest.&lt;/p&gt;

&lt;h2 id="3-generate-the-unhappy-path"&gt;
  
  
  3. Generate the unhappy path
&lt;/h2&gt;

&lt;p&gt;The most useful prompt in the sequence asks for edge cases: empty inputs, extreme values, mixed units. I keep that list next to the calculator and turn it into validation rules and test cases.&lt;/p&gt;

&lt;h2 id="4-iterate-in-the-open"&gt;
  
  
  4. Iterate in the open
&lt;/h2&gt;

&lt;p&gt;Once the calculator ships, real users find the inputs I never imagined. Each round of feedback becomes a new prompt: describe the confusing case, ask for the cleanest way to handle it, and update the tool. The loop is slow but it compounds.&lt;/p&gt;

&lt;p&gt;One example of the result is a &lt;a href="https://caninecalc.com/dog-calorie-calculator/" rel="nofollow ugc noopener noreferrer"&gt;free dog calorie calculator&lt;/a&gt; — it estimates daily calories from a dog's weight and activity level, and every assumption it uses is spelled out on the page.&lt;/p&gt;

&lt;p&gt;The takeaway: prompts are cheap and published tools are forever. Write the spec with the model, verify the assumptions yourself, and ship the calculator.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
