RIGGS

How it started

I was spending too much time managing myself — tracking tasks, summarizing emails, deciding what to work on next. I wanted a system that would handle the operational layer of my day so I could focus on building.

RIGGS started as a simple Claude Code session with some markdown files. It grew into a full knowledge base: structured folders covering every area of life and work, a session log for continuity between conversations, skill files that define repeatable workflows, and sub-agents that go do research autonomously.

The name comes from the idea of a ship's rigger — someone who sets up the lines so the captain can sail. RIGGS handles the rigging. I handle the direction.

How it works

RIGGS lives in a GitHub-synced markdown knowledge base called RIGGS_BRAIN. Every session, Claude reads the last session log entry to restore context, then picks up where we left off.

• Morning check-in — reviews priorities, surfaces urgent items, checks the scratchpad inbox
• Evening check-in — scores the day, logs decisions, commits and pushes all changes to GitHub
• Research agents — sub-agents that run autonomously and append findings to project files
• Gmail + Calendar MCP — reads and drafts email, checks and creates calendar events
• Telegram integration — send messages to RIGGS from your phone, get responses back
• Skills system — repeatable workflows defined in markdown, triggered by slash commands

Tech stack

Boilerplate

The full folder structure, CLAUDE.md template, skill boilerplates, and setup guide are available as a public repo. If you want to build your own RIGGS-style assistant, that's the starting point.

Repo updated monthly with new skills, agents, and tooling.