HorneroConfig
Comprehensive dotfiles framework for any WM/OS — reproducible, layered, and documented like a nest built stick by stick.
Explore dotfilesI'm Ulises Jeremias — Solutions Architect at NaNLABS, Core Team Member at V, and AUR Maintainer. I build developer tooling, AI-powered workflows, CLI apps, and infrastructure automation — mostly in TypeScript, Go, Shell, and Python.
I help teams ship reliable tooling: from workstation foundations (HorneroConfig) and AI workspaces to scientific libraries for the V language and community-driven CLIs.
Warm, precise, and reproducible — I help teams ship tooling that survives reinstalls and handoffs.
Solutions Architect @ NaNLABS
La Plata, Buenos Aires, Argentina
Solutions Architect at NaNLABS, Core Team Member at V, and AUR Maintainer. I build developer tooling, AI-powered workflows, CLI apps, and infrastructure automation — mostly in TypeScript, Go, Shell, and Python.
I help teams ship reliable tooling: from workstation foundations (HorneroConfig) and AI workspaces to scientific libraries for the V language and community-driven CLIs.
Active, not aspirational — each tile is a repo you can read, run, and critique today.
Comprehensive dotfiles framework for any WM/OS — reproducible, layered, and documented like a nest built stick by stick.
Explore dotfilesPersonal AI developer workstation — agents, skills & CLI helpers that make any assistant useful on day one.
Explore workstationPortable workspace orchestrator — persistent memory, personas, skills for Claude Code, Cursor, opencode, and Gemini CLI.
Explore harnessScientific computing for V — numerical methods, linear algebra, and statistics with precise, tested implementations.
Explore VSLTensor and autograd for V — building ML primitives with clarity over magic.
Explore VTLEach world is a documentation-ready section — dotfiles, workstation, toolkit, V, templates, and community — connected, not scattered.
Your nest, reproducible. Layered dotfiles with Chezmoi, Hyprland, and Quickshell — copy what you need, understand why it exists.
personal DXFour layers: machine → tools → intelligence → workspace. Health checks, doctor, and skills that survive a reinstall.
toolkitComposable AI toolkit — 52 skills, loops, packs, and MCP templates for every assistant. One source of truth, many targets.
V ecosystemCore Team perspective: language, tooling, and ecosystem — from setup-v to the libraries that make V useful for science.
templatesScaffold without decisions fatigue. Templates + addons that compose cleanly across Node, Python, and V.
communityEvidence over vanity. Contribution timelines, proof links, and pathways for beginners and maintainers.
No skill bars. Each strength is a system: principles, tools, and proof you can verify.
Systems that can be rebuilt from zero and audited line by line. Chezmoi, shell, and containers over hidden state.
Small CLIs that compose well. Typed, tested, and documented — so they survive beyond the author.
Agents are tools, not theatre. Skills, loops, and memory designed for solo → swarm handoffs and cost control.
Numerical code with tests, diagrams, and references — not copy-pasted formulas. Clarity over cleverness.
No vanity metrics. Every claim links to a repo, commit, or org you can inspect — not a star count.
Shipping language tooling and scientific libraries used by the V community. Contributions are public, reviewed, and linked.
Verified via github.com/vlang — member badge and authored commits
Lead the initiative for reference repositories and boilerplates. Every public repo catalogued transparently.
20+ public repos — not vanity stars, but reusable starting points
Packaging and maintenance where it counts — reproducible installs for the tools people actually run.
Evidence links instead of download counts
Linux tooling, CLI apps, AI agents, and science computing — if you build in those worlds, I’d love to compare notes.
The fastest way is email or Discord. For code, open an issue on any repo — I review every one.
Have an idea that needs a workstation, a CLI, or a scientific library? I help teams ship the first reliable version and the docs that keep it alive.
Response time: usually within 24h — or open a GH issue for async.