[Story]: Vibe Coding — shared guidelines, tips & best practices (cross-team + per-repo)

[adoLime]

User Story

As a team member, I want shared Vibe Coding guidelines, tips, and best
practices — anchored in each team repo — so the team codes consistently
and quality improves.

Acceptance Criteria

• Cross-team Doc exists at the agreed location, linking
  each team-specific doc.
• Team-specific Doc exists in each team repo (backend,
  frontend, AI at minimum), linked from README / CONTRIBUTING.md.
• Initial guidelines, tips, and best practices are documented
  (≥3 entries each from team contributions).
• Contribution workflow and review cadence are agreed and documented.
• Language: All Vibe Coding documentation — both the
  overarching doc and every team-specific doc — is written in
  English (file names, headings, content, examples).

Sub-Tasks

• All teams — contribute initial guidelines / tips / best practices.
• All teams — Link from each repo's README to the docs.