|
|
|
|
|
|
by dipeshsukhani
166 days ago
|
|
|
For non‑coding work we still treat a repo as the source of truth, but it’s mostly Markdown, checklists and assets rather than code. Think of it as a structured project brain that AI can read, update and score. For example, for social media management our repo's outline structure that are getting to be is as follows (still WIP): social-media/
README.md # How this repo works, scoring rules
/config
platforms.yaml # Accounts
content_guidelines.md # Brand voice, do/don’t list
/planning
2025-12-calendar.md # Calendar
2025-12-campaign-x402.md # Campaign brief, goals, KPIs
/drafts
2025-12-05-x-new-feature.md
2025-12-16-x-new-feature.md
/assets
images/
video/
copy-snippets.md
/published
2025-12-05-x-new-feature.md # Final copy + URLs + timestamp
2025-12-16-x-new-feature.md
/reports
2025-01-05-metrics.md # CTR, saves, comments, etc. Daily tasks are then deterministic checklists inside the repo, e.g. “Create 3 drafts for next Tuesday with images in /assets/images and entries added to 2025-12-calendar.md under campaign X”. |
|
|