vibe-coding-architecture

Imported from yaochen1125/vibe-coding-architecture (AGENTS.md). Install upstream with npx skills add yaochen1125/vibe-coding-architecture. Copyright stays with the author.

Project Working Standard

This repository follows a domain-driven AI engineering standard.

The primary goals are:

• reduce token waste
• reduce cross-domain coupling
• keep edits local to one domain whenever possible
• prevent unrelated agent or feature contexts from mixing

Default Rule

When editing this repository:

1. work in one domain at a time
2. read the local SPEC.md or domain README.md first
3. avoid scanning unrelated folders by default
4. use public interfaces instead of reaching into internal files
5. prefer small, reversible patches

Domain Map

Current intended domains:

• src/music/ Responsibility:

  • Suno generation
  • polling
  • track and cover downloads

• src/telegram_openclaw/ Responsibility:

  • Telegram topic handling
  • topic -> workspace mapping
  • OpenClaw communication

• src/shared/ Responsibility:

  • stable helpers only

File Reading Order

Before making non-trivial changes, read only:

1. the active file
2. files in the same domain
3. the domain SPEC.md or README.md
4. directly imported interface files

Do not read the whole repository unless the task genuinely requires cross-domain work.

Telegram + OpenClaw Rule

This repository requires strict topic isolation:

• Telegram topic names may be Chinese
• runtime workspaces must be normalized to stable English keys
• session keys must use:

agent:{agent_id}:{workspace}

Recommended mapping:

总控室 -> control
美术组 -> painter
导演组 -> director
音乐组 -> musician
合成组 -> builder
发布组 -> publisher

Change Discipline

• Do not reintroduce orchestrator-style coupling.
• Do not create broad utils/ dumping grounds.
• If a module grows, add or update its SPEC.md.
• If a module is replaced, remove obsolete code instead of preserving dead paths.