Engineering Blog — Sailing Naturali
sailingnaturali/engineering
Blog de engenharia code-heavy sobre AI ops em embarcações autossuficientes
Ver no GitHubBlog técnico focado em documentar a construção do stack de AI ops para um catamarã elétrico autossuficiente, cobrindo Home Assistant, SignalK, MCP servers e LLMs locais. Serve como referência prática para comunidades de self-hosted e makers interessados em automação marinha e sistemas inteligentes.
Instalação
npx convez-ai sailingnaturali/engineering1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Documentar soluções práticas de automação marinha e IA local
- Compartilhar troubleshooting de integração de Home Assistant com dados NMEA
- Registrar aprendizados e decisões arquiteturais para comunidade maker
- Servir como SEO-friendly reference para problemas específicos de DevOps em ambientes embarcados
Veredito

Projeto legítimo de documentação técnica orientado a código, com disciplina clara de estilo (broken → tried → fixed) e governance por agent + human review. Serve nichos reais (self-hosted, HA, embedded AI) sem marketing vazio. Recomendado para quem busca referência honest sobre DevOps em sistemas autônomos.
README
A tradução para o português deste README ainda está na fila.
Sailing Naturali — Engineering Blog
Developer-facing engineering blog for Sailing Naturali. Built with Jekyll, served by GitHub Pages at engineering.sailingnaturali.com.
It's the developer-facing sibling of the exec-facing Substack: code-heavy posts
about building the boat-agent / marine-AI-ops stack (Home Assistant, SignalK,
MCP servers, local LLM, NMEA marine data), aimed at the self-hosted / HA / maker
crowd. Design rationale lives in the planning repo:
docs/superpowers/specs/2026-06-01-engineering-blog-and-scribe-agent-design.md.
How it's built & served
- Static-site generator: Jekyll (
minimatheme). - Build: native GitHub Pages build — pushing to
mainrebuilds and publishes. No GitHub Actions workflow. Plugins are limited to the Pages whitelist; we usejekyll-seo-tag,jekyll-feed, andjekyll-sitemap. - Domain: the
CNAMEfile pinsengineering.sailingnaturali.com. DNS is aCNAME engineering → sailingnaturali.github.iorecord.
Writing a post
Posts are Markdown files in _posts/, named YYYY-MM-DD-slug.md. Front matter:
---
layout: post
title: "A specific, searchable title — include the error string people google"
description: "1–2 sentence SEO description. Name the real symptoms and versions."
date: 2026-06-01
tags: [homeassistant, selfhosted, ai]
---
URLs are /:title/ (the slug from the filename), so make the slug searchable.
jekyll-seo-tag derives the canonical URL automatically — don't set one unless
the post is syndicated and canonical lives elsewhere.
House style
- Code first. Every config, command, error, and change is a copy-pasteable block, never described in prose.
- broke → tried → fixed. The "what we tried (and why it failed)" beat is mandatory — it's the highest-trust, highest-SEO part of the post.
- Direct, technical, no marketing fluff. Close with a short, non-salesy line connecting back to the project.
The Scribe workflow
Drafts are produced on-demand by the Scribe agent (lives in the planning
repo at .claude/agents/scribe.md) from finished engineering work and
docs/agent-lessons.md. The Scribe opens a PR against this repo; a human reviews
voice/accuracy and merges. Never reproduces anything from the private
infrastructure repo.
Local preview
bundle install
bundle exec jekyll serve # http://localhost:4000