How I use what I publish
This is not a catalog. These are tools I wrote to solve my own problems, and what I do with them.
I built a bot to query the SII. Then I gave it memory.
I built sii, an open-source library for the Chilean tax authority: purchases and sales, fee receipts and F29 statuses. At first, using it meant typing commands in a terminal. Ordinary for me. For someone running a business, one more thing to learn before the actual problem.
With that library as a tool, I built an accounting bot in Grok Bot. The conversation is the input: I ask for a review and the bot uses the available functions to look the information up.
I gave it an organized memory of the business, following Andrej Karpathy's LLM Wiki pattern, with clients, suppliers and decisions linked to each other. So I can ask something more useful than "show me the receipts":
"What was still open with this supplier, and what had we decided to do?"
I also set up routines to follow receipts, F29 filings and observations that need attention. I go from remembering to ask to getting a notice when there is something to review.
Excerpt from the article "I built a bot to query the SII. Then I gave it memory." (draft, not published yet).
The others, and where they come from
context-first-development
This is how I work with AI agents: a persistent, hierarchical context the agent reads before writing code. The repository is the template I use to start each project with that structure.
nemo-cli
I wrote it as a client for Vector Capital, so I can check my own holdings from the terminal instead of opening the portal.
cta
Reads the balance, movements and cards of my Chilean bank accounts. Read only.
bloc_one_shot
happy_review
It came out of "The Art of Asking": request the review inside the app at a happy moment, when the user finishes something, not the nth time they open it.