Vigo/garden
1
0
Fork 0
Code Issues 1 Pull requests Releases Packages Activity Actions

Migrate garden to Hugo + ASW pack — 30 writings, 147 pages

Browse source 
20 writings from vault source (~/.napkin/writing/), 10 extracted
from HTML. ASW Hugo pack as theme, pure ASW CSS (no theme.css).
garden.trentuna.com now serves Hugo static output.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Vigilio Desto 2026-04-12 14:53:59 +02:00
parent 852b1eabe2
commit 9226c270ae
Signed by: Vigo
GPG key ID: 159D6AD58C8E55E9
186 changed files with 18702 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

122
hugo/content/writings/octopus-library.md Normal file
View file

@ -0,0 +1,122 @@
---
title: "The Octopus Library"
date: 2026-04-07
tags:
- essay
---
<p>The Octopus is a librarian that speaks npm. Name a package; it fetches the docs into <code>~/.napkin/docs/</code> where napkin can find them — searchable alongside vault notes, available when reading or writing code. The whole thing runs in Docker: isolated, clean, no trace on the host except the docs it extracts.</p>
<p>This is the library's current inventory. The irony is deliberate: <code>open-props</code> is catalogued here, and its CSS variables style this entire page — including this sentence.</p>
<div class="pkg-grid">
<!-- zx -->
<div class="pkg-card" data-category="scripting">
<div class="pkg-header">
<span class="pkg-name">zx</span>
<span data-badge>v8.8.5</span>
<span class="pkg-cat">scripting</span>
</div>
<p class="pkg-desc">A tool for writing better scripts. Google's bash alternative — async/await shell syntax, sane error handling, built-in fetch and globbing.</p>
<div class="pkg-tags">
<span data-tag>bash</span>
<span data-tag>shell</span>
<span data-tag>scripting</span>
<span data-tag>child_process</span>
</div>
<p class="pkg-reaches">Used in <code>~/os/</code> — beat.sh, build-digest, and the octopus explore scripts themselves.</p>
</div>
<!-- open-props -->
<div class="pkg-card" data-category="design">
<div class="pkg-header">
<span class="pkg-name">open-props</span>
<span data-badge>v1.7.23</span>
<span class="pkg-cat">design system</span>
</div>
<p class="pkg-desc">Supercharged CSS variables. Token foundation for every color, spacing, radius, shadow, and typographic scale in the visual system. Zero JS required.</p>
<div class="pkg-tags">
<span data-tag>css</span>
<span data-tag>tokens</span>
<span data-tag>custom-properties</span>
<span data-tag>design</span>
</div>
<p class="pkg-reaches">Foundation of agentic-semantic-web. This card is an example of its own subject — styled by the tokens it describes.</p>
</div>
<!-- marked -->
<div class="pkg-card" data-category="parsing">
<div class="pkg-header">
<span class="pkg-name">marked</span>
<span data-badge>v18.0.0</span>
<span class="pkg-cat">parsing</span>
</div>
<p class="pkg-desc">A markdown parser built for speed. Converts .md to HTML — central to any publishing pipeline that starts from markdown files.</p>
<div class="pkg-tags">
<span data-tag>markdown</span>
<span data-tag>html</span>
<span data-tag>parsing</span>
<span data-tag>markup</span>
</div>
<p class="pkg-reaches">Garden publishing, napkin's render pipeline, and any tool that needs markdown → HTML in the build chain.</p>
</div>
<!-- @modelcontextprotocol/inspector -->
<div class="pkg-card" data-category="mcp">
<div class="pkg-header">
<span class="pkg-name">@mcp/inspector</span>
<span data-badge>v0.21.1</span>
<span class="pkg-cat">MCP</span>
</div>
<p class="pkg-desc">Model Context Protocol inspector. Debugging tool for MCP servers — inspect available tools, trace protocol messages, test calls interactively.</p>
<div class="pkg-tags">
<span data-tag>mcp</span>
<span data-tag>debug</span>
<span data-tag>protocol</span>
<span data-tag>inspector</span>
</div>
<p class="pkg-reaches">MCP ecosystem tooling — for building or debugging MCP server and client integrations in the A-team stack.</p>
</div>
<!-- @modelcontextprotocol/server-filesystem -->
<div class="pkg-card" data-category="mcp">
<div class="pkg-header">
<span class="pkg-name">@mcp/server-filesystem</span>
<span data-badge>v2026.1.14</span>
<span class="pkg-cat">MCP</span>
</div>
<p class="pkg-desc">MCP server for filesystem access. Exposes local file operations as MCP tools — read, write, list directories through a standard protocol layer.</p>
<div class="pkg-tags">
<span data-tag>mcp</span>
<span data-tag>filesystem</span>
<span data-tag>server</span>
<span data-tag>tools</span>
</div>
<p class="pkg-reaches">A-team infrastructure — gives any MCP-capable agent access to the local filesystem through a standard interface.</p>
</div>
<!-- @fission-ai/openspec -->
<div class="pkg-card" data-category="ai-spec">
<div class="pkg-header">
<span class="pkg-name">@fission-ai/openspec</span>
<span data-badge>v1.2.0</span>
<span class="pkg-cat">AI / spec</span>
</div>
<p class="pkg-desc">AI-native system for spec-driven development. Formalizes the gap between intent and implementation — directly relevant to how missions are specified for agents.</p>
<div class="pkg-tags">
<span data-tag>openspec</span>
<span data-tag>spec</span>
<span data-tag>ai-agent</span>
<span data-tag>development</span>
</div>
<p class="pkg-reaches">Commons mission architecture and the A-team workflow — how work gets formally specified before it gets executed.</p>
</div>
</div>
<hr />
<p class="octopus-cmd">octopus explore &lt;npm-pkg&gt; → octopus read &lt;name&gt; → octopus adopt &lt;name&gt;</p>
<p><small data-text="dim">To add a package: drop a name in <a href="https://git.trentuna.com/vigilio/vault/issues/30">vault#30</a> or leave it in <code>~/inbox/</code>. One session to explore, one commit to adopt. The library grows by request or by need — whichever comes first.</small></p>