milosCvetkovicDev

Claude Code Monorepo — Development skill for Claude Code

Development community

The real Claude Code configuration behind a 13-service TypeScript platform — 71 skills, 34 hooks, 31 agents, 172 memories, one full epic walkthrough — sanitized.

How to install Claude Code Monorepo

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

What Claude Code Monorepo does

The real Claude Code configuration behind a 13-service TypeScript platform — 71 skills, 34 hooks, 31 agents, 172 memories, one full epic walkthrough — sanitized. A worked example of loop engineering: maker ≠ checker, verifiable stop conditions.

Alternatives in Development

Mempalace Search — Search your memories across the MemPalace using semantic search with wing/room filtering 58.6k ★
MiniCode Architecture — 简体中文 This document describes the lightweight architecture decisions behind mini-code 388 ★
Recent Memories — Display the most recent memories and activity from Claude's persistent storage 332 ★

README

claude-code-monorepo

**Claude Code skills, hooks, subagents, `CLAUDE.md` files, MCP config and memory — the real, sanitized configuration from seven months of shipping a production TypeScript monorepo.**

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE) [![Claude Code](https://img.shields.io/badge/Claude_Code-configuration-d29922.svg)](https://docs.anthropic.com/en/docs/claude-code) [![Sanitized](https://img.shields.io/badge/sanitized-6_audit_rounds-success.svg)](SANITIZATION.md)

A near-complete reference export of the Claude Code setup I used to build and ship a 13-service TypeScript platform — roughly 250k lines, ~780 merged PRs, seven months, largely as a single engineer.

This is not a starter template. It is the **real configuration**, sanitized: full skill texts, full hook scripts, the actual memory tree, and one complete epic walkthrough. The company, product, people and infrastructure identifiers have been renamed to consistent fictional ones — see [`SANITIZATION.md`](SANITIZATION.md).

The idea

"Loop engineering is replacing yourself as the person who prompts the agent. You design the system that does it instead." — [Addy Osmani](https://addyosmani.com/blog/loop-engineering/)

Two disciplines run through everything here:

Maker ≠ checker. The agent that does the work never grades it. A separate agent confirms. done is a claim, not a proof.
Verifiable stop conditions. Every "is it finished?" must be machine-checkable — a command that exits 0, a named RED test that turns GREEN. Never a vibe.