retran

Meowary — AI skill for Claude Code

AI community

AI-powered work journal template for software developers.

How to install Meowary

This entry records only its repository, not the path inside it, so there is no exact command to give. Open retran/meowary and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Meowary does

AI-powered work journal template for software developers. PARA structure, Bullet Journal daily rhythm, Zettelkasten knowledge graph with semantic search, and structured coding workflows. Powered by OpenCode.

Alternatives in AI

Nocturne Memory — A lightweight, rollbackable, and visual Long-Term Memory Server for MCP Agents 1.3k ★
Engineering Notebook — A Bun CLI that ingests Claude Code and Codex session transcripts, generates LLM-powered daily summaries, and s 320 ★
Aiwg — Cognitive architecture for AI-augmented software development 204 ★

README

Meowary

A second brain template for software developers — built on plain Markdown and an AI coding agent that maintains it with you. The name is a portmanteau of *meow* and *diary*.

What It Does

Meowary gives your AI coding agent persistent, searchable memory. Decisions, trade-offs, architecture rationale, team context — captured once, reused every session. The agent reads your notes before acting, so it stops asking things you already documented.

Clone the repo, run `setup.sh`, run `/bootstrap`, start your first day with `/morning`.

Supported Agents

Agent	Status
OpenCode	Full support
Claude Code	Full support

Both agents share the same workflows, skills, scripts, and reference material. `generate.sh` produces each agent's configuration directory from a single canonical source (`.shared/`). You choose your agent during setup; switching later costs one command.

Design Philosophy

Decisions evaporate without a system

Meowary borrows **Zettelkasten** staged understanding: raw capture → source notes → atomic cross-linked articles. [QMD](https://github.com/tobi/qmd) semantic search surfaces the right context before every action.

Capture must be frictionless

**Bullet Journal** rapid logging: dump everything into today's Inbox during the day. `/evening` sorts it. One command opens the day; one closes it.

Notes must develop, not accumulate

**Evergreen Notes** and **Digital Gardening**: articles are never finished, only more developed. Health scripts flag staleness.

Tools must compound, not fight

The same agent that writes your daily notes also reviews your pull requests — reading architecture decisions, team structure, and project history first. Organized by **PARA** (Projects, Areas, Resources, Archive).