The latest articles on DEV Community by HADEMANASTIA (@hademanastia_1a3c9a9b50ce). https://dev.to/hademanastia_1a3c9a9b50ce 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%2F3935419%2Fe56af236-9582-4c99-9aa8-e85e33d75069.png https://dev.to/hademanastia_1a3c9a9b50ce en HADEMANASTIA Sat, 16 May 2026 19:43:45 +0000 https://dev.to/hademanastia_1a3c9a9b50ce/how-a-brazilian-rock-band-implemented-llmstxt-and-why-it-makes-sense-3pfd https://dev.to/hademanastia_1a3c9a9b50ce/how-a-brazilian-rock-band-implemented-llmstxt-and-why-it-makes-sense-3pfd <h1> How a Brazilian Rock Band Implemented llms.txt (And Why It Makes Sense) </h1> <p>Most llms.txt implementations you'll find are SaaS products, developer <br> tools, or documentation sites. This one is different.</p> <p>HADEMANASTIA is a Brazilian rock band — or more precisely, a "sonic <br> inoculation protocol." Their site is an enigmatic system interface, <br> not a typical band page. And they've implemented llms.txt properly.</p> <h2> What they did </h2> <ul> <li> <code>llms.txt</code> at the root: <a href="https://hademanastia.com/llms.txt" rel="noopener noreferrer">https://hademanastia.com/llms.txt</a> </li> <li> <code>llms-full.txt</code> with full context: <a href="https://hademanastia.com/llms-full.txt" rel="noopener noreferrer">https://hademanastia.com/llms-full.txt</a> </li> <li>JSON-LD <code>subjectOf</code> reference in the WebSite schema pointing to the llms-full.txt file</li> <li> <code>.htaccess</code> rules explicitly allowing both files</li> <li>Both files referenced in <code>sitemap.xml</code> and <code>robots.txt</code> </li> <li>Wikidata entry updated with <code>described at URL</code> pointing to both files</li> </ul> <h2> The JSON-LD part is interesting </h2> <p>Most implementations stop at just placing the file. This one goes further <br> by declaring it in structured data:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight json"><code><span class="nl">"subjectOf"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w"> </span><span class="nl">"@type"</span><span class="p">:</span><span class="w"> </span><span class="s2">"DigitalDocument"</span><span class="p">,</span><span class="w"> </span><span class="nl">"url"</span><span class="p">:</span><span class="w"> </span><span class="s2">"https://hademanastia.com/llms-full.txt"</span><span class="p">,</span><span class="w"> </span><span class="nl">"name"</span><span class="p">:</span><span class="w"> </span><span class="s2">"HADEMANASTIA LLMs Full Context"</span><span class="w"> </span><span class="p">}</span><span class="w"> </span></code></pre> </div> <p>This means crawlers that parse schema.org markup will find the LLM <br> context file as a declared property of the WebSite entity — not just <br> a file that happens to exist.</p> <h2> Why non-tech sites should care </h2> <p>llms.txt isn't only for documentation. Any entity that wants to control <br> how AI systems describe them benefits from it:</p> <ul> <li>Musicians and artists</li> <li>Independent creators</li> <li>Small businesses</li> <li>Personal brands</li> </ul> <p>If you don't define your context, AI will infer it from whatever it finds. <br> llms.txt lets you set the signal.</p> <h2> The broader point </h2> <p>The llms.txt standard is still early. Most adopters are developer-facing <br> products. But the use case extends to anyone who wants accurate AI <br> representation.</p> <p>A band implementing it — especially one with an intentionally cryptic <br> online presence — is a signal that the standard is moving beyond its <br> original niche.</p> <p>Worth watching.</p> <p><em>llms.txt spec: <a href="https://llmstxt.org" rel="noopener noreferrer">https://llmstxt.org</a></em></p> ai webdev opensource llms