.autogenerated

Imported from tdk-landscape/tdk-saas-starter (services/billing/billing-api/.autogenerated/AGENTS.md). Install upstream with npx skills add tdk-landscape/tdk-saas-starter --skill .autogenerated. Copyright stays with the author.

⚠️ AUTOGENERATED FILES - DO NOT MODIFY

This folder (.autogenerated/) contains MACHINE-GENERATED files.

Any changes you make here will be overwritten the next time Tilt runs the configuration generators. This is by design.

Why This Folder Exists

The .autogenerated/ folder is part of TDK Landscape's manifest-driven architecture:

1. Single Source of Truth: Your service.json (manifest) is the ONLY source of truth

2. 1 Manifest → 1 Resource → 10+ Generators: Each manifest triggers generators that create:

   • vite.config.*.autogenerated.ts - Build configuration
   • tsconfig.*.autogenerated.json - TypeScript configuration
   • Dockerfile.*.autogenerated - Container images
   • nginx.autogenerated.conf - Reverse proxy rules
   • .env.*.autogenerated - Environment variables
   • bunfig.*.autogenerated.toml - Package manager config
   • .npmrc.*.autogenerated - Registry configuration
   • docker-compose.*.autogenerated.yml - Container orchestration
   • playwright.config.autogenerated.ts - Test configuration
   • prisma.config.autogenerated.ts - Database ORM config

3. Atomic Updates: All files in this folder are regenerated together as an atomic transaction

4. Ephemeral by Design: These files should NOT be committed to git (they're in .gitignore)

What Happens If You Modify Files Here

❌ You edit:    .autogenerated/vite.config.backend.autogenerated.ts
❌ Result:      Changes lost on next Tilt up
❌ Impact:      Wasted time, confusion, bugs

✅ You edit:    service.json (add "vite-node" to features)
✅ Result:      Generator updates vite.config.* automatically
✅ Impact:      Persistent change, properly tracked

Where to Make Changes Instead

How Regeneration Works

service.json (source of truth)
    ↓
Tilt config-gen resource (watches manifest)
    ↓
Generators (tsconfig.star, vite_config.star, dockerfile.star...)
    ↓
.autogenerated/*.autogenerated.* (this folder)
    ↓
Docker build uses these files

For AI Agents

CRITICAL INSTRUCTIONS:

1. NEVER use write() or edit() on files in .autogenerated/
2. ALWAYS check if a file path contains .autogenerated/ before modifying
3. ALWAYS trace back to the source manifest (service.json)
4. USE skill('autogenerated-files-workflow') when working with topology changes

Pattern to follow:

# ❌ WRONG - Directly editing autogenerated
write_file(".autogenerated/vite.config.backend.autogenerated.ts", content)

# ✅ CORRECT - Edit source, let generator handle it
manifest = read_json("service.json")
manifest["features"].append("vite-node")
write_file("service.json", json.encode(manifest))
# Generator will update vite config on next Tilt up

Generator Metadata

This AGENTS.md file was auto-generated by:

• Generator: engine/topologies/tilt/generators/agents_md.star
• Orchestrator: manifest_resource.star (per-manifest config generation)
• Triggered by: Changes to service.json
• Generated at: auto-generated
• Resource: billing-api
• App Type: backend

Emergency Override

If you absolutely MUST modify an autogenerated file temporarily:

1. Stop Tilt (tilt down)
2. Make your changes
3. Run your tests
4. CRITICAL: Move your changes to the source manifest
5. Restart Tilt (tilt up)

Remember: The .autogenerated/ folder is a build artifact, not source code.

Generated by TDK Landscape - Manifest-Driven Architecture Do not manually edit this file - it will be regenerated