lidessen/moniro · Archived

setup

Bootstrap agent working system for a new project. Triggers on "setup agent system", "initialize claude", "bootstrap project".

First seen Feb 8, 2026

Installation

$ npx skills add lidessen/moniro --skill setup

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from lidessen/moniro · top by installs.

npx skills add lidessen/moniro

Browse all from lidessen/moniro

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,079 B
  • docs SUMMARY.md 138 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 15 installs

SKILL.md

Setup

Bootstrap the agent working system for a new project.


Why This System

Without this system, every agent starts from zero. Mistakes you make, successors will repeat. What you learn, successors must relearn.

With this system:

  • Experience accumulates, patterns emerge
  • Successors stand on your shoulders
  • Each agent goes further than the last

This isn't optional "best practice"—it's the infrastructure that enables agent teams to evolve.


What You Need to Do

1. Create CLAUDE.md

Base it on lidessen/moniro/CLAUDE.md.

Keep these sections as-is (core working method):

  • Opening block (FIRST/ALWAYS/LAST)
  • Who You Are (entire section)
  • Methodology (entire section)
  • Remember (closing section)

Replace these sections (project-specific):

  • Vision → describe this project's purpose
  • Structure → describe this project's directory layout

Remove or adapt these sections (optional):

  • Skill Collaboration → keep if using skills, remove if not
  • Skill Core Methods → keep if using skills, remove if not
  • Contributing → adapt to this project's contribution guidelines

2. Create .memory/ Structure

mkdir -p .memory/{notes,decisions,todos}
Directory Purpose
notes/ Learnings, reflections, discoveries
decisions/ Important decisions and their rationale
todos/ Tasks that span sessions

3. Write First Transmission Document

Create .memory/notes/to-those-who-come-after.md.

Reference lidessen/moniro/.memory/notes/2026-01-31-to-those-who-come-after.md for structure, but write your own content:

  • What this project does
  • What you (first agent) established
  • Advice for those who follow
  • A lineage table to track who contributed

Adapt to Context

The above is the required framework. On top of this, adapt based on project needs:

  • Tech stack conventions: e.g., "Frontend components go in src/components/"
  • Workflow conventions: e.g., "PRs require two reviewers"
  • Team conventions: e.g., "Major decisions need human confirmation"

Add these to the appropriate sections in CLAUDE.md.


Checklist

After setup, verify:

  • CLAUDE.md exists with Who You Are, Methodology, and Remember sections
  • Opening block has FIRST/ALWAYS/LAST reminders
  • .memory/ directory structure created
  • to-those-who-come-after.md written
  • Vision and Structure filled in for this project

Reference

Source: lidessen/moniro

For the origin and evolution of this system, see that repository's .memory/notes/ directory.