Sharing my #VibeCoding
1/ A top-level directive document https://t.co/LYFB1aM3T9 assigns roles to https://t.co/m7OLJWKW9G and https://t.co/4z5pm1emEe
2/ cc is the builder, xcode is the reviewer; they communicate via .task files
3/ Each directory has https://t.co/QsDykAiXZ1; code changes in the directory trigger automatic updates
4/ https://t.co/m7OLJWKW9G references https://t.co/QsDykAiXZ1, keeping https://t.co/m7OLJWKW9G lean
5/ docs directory stores daily requirement docs; running https://t.co/WMY37zrNNY generates today's prompts and launches cc
6/ Manage .task directories (ready/feedback/done/review) storing interaction MD docs at different stages
7/ Beyond .task communication, git commits also convey information between builders and reviewers, though git push permissions reside with me
8/ Reviewers monitor .task/ready directory files in real-time; new additions trigger automatic review, determining whether to mark as feedback or done
Oh, and all this runs on a Linux cloud server.