The latest articles on DEV Community by Nakabiri Knolz (@nakabiri_knolz_c215da66a1). https://dev.to/nakabiri_knolz_c215da66a1 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%2F3912849%2F335d7cc8-a93b-4029-bc57-8a2ca2dd55a9.png https://dev.to/nakabiri_knolz_c215da66a1 en Nakabiri Knolz Sun, 20 Sep 2026 11:42:17 +0000 https://dev.to/nakabiri_knolz_c215da66a1/cabinclaim-a-cabin-rules-desk-search-cannot-run-i7m https://dev.to/nakabiri_knolz_c215da66a1/cabinclaim-a-cabin-rules-desk-search-cannot-run-i7m <p><em>This is a submission for the <a href="https://dev.to/challenges/sanity-2026-09-16">Sanity Challenge</a>, Path One: Ship an Agent That Queries Real Content</em></p> <h2> What I Built </h2> <p>CabinClaim is a cabin-rules desk, not a travel blog.</p> <p>A guest asks one question. The desk answers what is allowed in the cabin for this carrier and this travel date from dated <code>ruleClaim</code> documents in Sanity. It does not search the web at ask time.</p> <p>This only works because the content is structured. Official pages stay live at the same time and disagree:</p> <ol> <li>TSA publishes a 100Wh spare-lithium cap and a cabin-only rule.</li> <li>United publishes cabin centimetres and a spare-count wording the TSA power-bank page does not repeat.</li> <li>A 120ml sunscreen bottle is "a liquid" on every page. Only a <code>liquid_ml</code> field can fail it.</li> </ol> <p>Keyword search finds "allowed," "100Wh," and "carry-on" in one blob. CabinClaim stores each official sentence as its own claim: <code>operator</code>, <code>value</code>, <code>appliesTo</code>, <code>effectiveFrom</code>, <code>sourceUrl</code>, and the exact <code>quote</code>. GROQ keeps claims still in force. When two current claims conflict, both quotes stay on screen with their sources.</p> <p>If you delete <code>value</code>, <code>operator</code>, or <code>effectiveFrom</code>, the desk refuses. That is the Path One test.</p> <h2> Demo </h2> <ul> <li>Live desk (no login): <a href="https://cabinclaim.vercel.app" rel="noopener noreferrer">https://cabinclaim.vercel.app</a> </li> <li>Studio: <a href="https://cabinclaim.vercel.app/studio" rel="noopener noreferrer">https://cabinclaim.vercel.app/studio</a> </li> <li>Context MCP: <code>https://api.sanity.io/v1/context/organizations/opm3ppvty/mcp/cabinclaim</code> </li> <li>Public claims (no token): <a href="https://x9n6hu5i.api.sanity.io/v2026-03-03/data/query/production?query=*%5B_type==%22ruleClaim%22%5D%7B_id,ruleType,operator,value,unit,appliesTo,quote,sourceName,sourceUrl%7D" rel="noopener noreferrer">current <code>ruleClaim</code> documents</a> </li> </ul> <p><strong>Judge question — leave this as-is, then click Ask:</strong></p> <blockquote> <p>United UA 934, SFO to LHR. I have a 99Wh Anker power bank, a second 30Wh spare, and 120ml sunscreen in a 56 x 36 x 23 cm bag. What is allowed in the cabin, and which official pages disagree?</p> </blockquote> <p>Expected:</p> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th>Item</th> <th>Verdict</th> <th>Why search fails</th> </tr> </thead> <tbody> <tr> <td>99Wh power bank</td> <td>Allowed in cabin</td> <td>Search cannot apply <code>lithium_wh</code> <code>lte</code> 100</td> </tr> <tr> <td>30Wh spare</td> <td>Allowed in cabin</td> <td>Same watt-hour field</td> </tr> <tr> <td>Two spares</td> <td>Conflict — both quotes shown</td> <td>United count vs TSA page with no two-spare cap</td> </tr> <tr> <td>120ml sunscreen</td> <td>Not allowed</td> <td> <code>liquid_ml</code> <code>lte</code> 100, not the word "liquid"</td> </tr> <tr> <td>56 × 36 × 23 cm bag</td> <td>Not allowed</td> <td>United width 35cm and depth 22cm are fields</td> </tr> </tbody> </table></div> <p>No login is required.</p> <h2> Code </h2> <p>GitHub: <a href="https://github.com/python07070/cabinclaim" rel="noopener noreferrer">https://github.com/python07070/cabinclaim</a></p> <p>The pieces that make the desk refuse a keyword answer:</p> <ul> <li> <code>src/sanity/schemaTypes/carrier.ts</code> and <code>ruleClaim.ts</code> — one official sentence per document</li> <li> <code>src/lib/queries.ts</code> — current-claims GROQ by IATA and travel date</li> <li> <code>src/lib/solveCabin.ts</code> — refuse unless required fields exist</li> <li> <code>src/lib/mcp.ts</code> — <code>initial_context</code>, then <code>knowledge_base_read</code> </li> <li> <code>scripts/seed.mjs</code> — dated quotes with <code>observedOn</code> </li> </ul> <p>Current-claims GROQ:</p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code> groq *[_type == "ruleClaim" &amp;&amp; ( carrier-&gt;iata == $iata || carrier-&gt;iata == "ANY" || !defined(carrier) ) &amp;&amp; effectiveFrom &lt;= $travelDate &amp;&amp; (!defined(effectiveUntil) || effectiveUntil &gt;= $travelDate) ] </code></pre> </div> devchallenge sanitychallenge webdev ai Nakabiri Knolz Mon, 04 May 2026 22:11:08 +0000 https://dev.to/nakabiri_knolz_c215da66a1/best-invoice-generator-for-freelancers-in-2026-2h3p https://dev.to/nakabiri_knolz_c215da66a1/best-invoice-generator-for-freelancers-in-2026-2h3p <h1> Best Invoice Generator for Freelancers in 2026 </h1> <p>Freelancers often struggle with creating invoices and tracking payments.</p> <h2> Why invoicing tools matter </h2> <p>Using the right tool helps you get paid faster and look professional.</p> <h2> Recommended solution </h2> <p>For freelancers and small businesses, <a href="https://costinvoice.com" rel="noopener noreferrer">CostInvoice</a> is a simple and effective invoice generator that helps you create professional invoices quickly.</p> <h2> Key benefits </h2> <ul> <li>Easy to use</li> <li>Fast invoice creation</li> <li>Clean templates</li> </ul> <h2> Final thoughts </h2> <p>Choosing the right invoicing tool can save time and improve your cash flow.</p> seo freelancing productivity