agentleFS
muyenmuyen/vibe-to-prod/CLAUDE.md

vibe-to-prod

CLAUDE.md34 starsChanged 11 months agoMITView on GitHub

Philosophy: Critical rules embedded here. Platform-specific rules in .claude/rules/. Platform-specific rules load automatically when working on relevant code: *Last Updated

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Continuous Improvement: - Every mistake → update rules.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 28,029 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Claude AI Memory - Vibe to Production

Philosophy: Critical rules embedded here. Platform-specific rules in .claude/rules/.


Core Principles

  1. Single Source of Truth - Edit source, not derived. OpenAPI → generates code.
  2. Impact Radius = Verification Radius - Change affects N systems → verify N systems.
  3. Make Wrong Hard - Automation, types, hooks prevent mistakes.
  4. Continuous Improvement - Every mistake → update rules. Every task → brief retrospective.

Before ANY Code Change

[ ] What is SOURCE vs DERIVED? (Edit source, regenerate derived)
[ ] What systems are affected? (Verify ALL of them)
[ ] Is there automation? (Check Makefile, scripts/)

Critical Rules (All Platforms)

RuleWhy
Use generated typesClients expect exact JSON from OpenAPI
Never edit generated filesPreToolUse hook blocks this automatically
Verify build before commitBackend: make build, iOS: make build, Android: ./gradlew build
Commit format: type: descriptionConventional commits

Platform Rules (Auto-loaded by path)

Platform-specific rules load automatically when working on relevant code:

PlatformRule FileTrigger Path
Backend (Go).claude/rules/backend.mdbackend/**
iOS (Swift).claude/rules/ios.mdmobile/ios/**
Android (Kotlin).claude/rules/android.mdmobile/android/**
Testing.claude/rules/testing.md**/*test*

Project Structure

.
├── backend/                 # Go API server
│   ├── api/openapi.yaml    # API spec (SOURCE OF TRUTH)
│   ├── cmd/api/main.go     # Entry point
│   └── Makefile
├── mobile/
│   ├── ios/                # Swift/SwiftUI
│   │   ├── project.yml     # XcodeGen (SOURCE OF TRUTH)
│   │   └── App/
│   └── android/            # Kotlin/Compose
│       └── app/
├── infrastructure/pulumi/   # IaC (Pulumi + Go)
├── scripts/
│   ├── setup.sh            # Initial setup
│   └── openapi_workflow.py # API code generation
└── .claude/                # AI workflow config

Common Workflows

OpenAPI Change

# 1. Edit API spec
backend/api/openapi.yaml

# 2. Regenerate everything
python scripts/openapi_workflow.py --full

# 3. Verify ALL platforms build
make verify-all  # or run each: backend, iOS, Android

New Backend Endpoint

# 1. Add to OpenAPI spec
# 2. Regenerate: cd backend && make generate
# 3. Implement handler
# 4. Add tests
# 5. Verify: make build && make test

Adding a Feature

# 1. Plan with /ultra-think if complex
# 2. Implement with platform rules loaded
# 3. Test across affected platforms
# 4. Review with /code-review
# 5. Commit with /commit

Slash Commands

CommandPurpose
/commitCreate well-formatted commit
/code-reviewComprehensive code review
/generate-testsGenerate test suite
/refactor-codeSafe refactoring
/ultra-thinkDeep analysis mode
/security-scanSecurity vulnerability check
/improve-claude-configAudit and improve config

Configuration

FilePurpose
.claude/settings.jsonTeam-shared settings (hooks, permissions)
.claude/settings.local.jsonPersonal overrides (gitignored)
.claude/rules/Path-conditional rules
.claude/skills/Model-invoked skills
.claude/commands/User-invoked slash commands
.claude/hooks/Automation hooks
.claude/CONFIGURATION_IMPROVEMENT_GUIDE.mdConfig best practices

Reference Docs

TopicLocation
Getting starteddocs/GETTING_STARTED.md
Architecture decisionsdocs/ARCHITECTURE.md
API gateway/authdocs/API_GATEWAY.md
CI/CD setupdocs/CICD.md
MCP serversdocs/AI_WORKFLOW.md
Troubleshootingdocs/TROUBLESHOOTING.md

Last Updated: 2026-01-02 Version: 1.0.0 - Initial AI memory setup

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.