One page that maps every Claude Code skill and MCP connector to each of my repositories — the stack, the branch, the skills that apply, the connectors that ship the work, and the gotchas to remember.
Press / in Claude Code and pick a skill — /market-audit, /ecj-social, /seo-geo-aeo. It runs in the current session, in the current repo.
Most skills auto-trigger on intent — "run the reviews agent for eatcookjoy" fires /ecj-reviews on its own. No need to memorise names.
MCP connectors (GitHub, Gmail, Gamma, Higgsfield…) are the hands. Ask "open a PR", "draft the email", "render this reel" and Claude routes to the right one.
| Connector | What it does | Reach for it when… |
|---|---|---|
| 🐙 GitHub | Branches, commits, PRs, issues, CI/Actions. | Any repo — ship code, open PRs, file issues, check CI. |
| 🎞️ Higgsfield | AI image / video / audio / 3D; upscale, reframe, voiceover. | Reels, hero videos, thumbnails, Arabic/English voiceover. |
| 📊 Gamma | AI decks, one-pagers, docs, social posts. | Pitch decks, KPI one-pagers, lecture slides. |
| ✉️ Gmail | Draft / search / label / send email. | Outreach, GM reports, review recovery, client mail. |
| 📅 Google Calendar | Events, scheduling, free-slot finding. | Posting schedules, bookings, content calendars. |
| 📁 Google Drive | Search / read / create / copy files. | Store reels, briefs, brand assets; share with the team. |
| 🗂️ Notion | Pages, databases, comments, views. | Content calendar, KPI DB, SOP library, approvals. |
| 🎯 Apollo.io | B2B contact / company search & sequences. | Build lead lists (corporate catering, SMB clients). |
| 🧪 Clay | Find & enrich companies and contacts. | Enrich those leads before outreach. |
| 💷 QuickBooks | Invoices, payment links, P&L, cash flow. | Invoice bookings; pull revenue for reports. |
| 🟪 Wix | Build / manage Wix sites & APIs. | Campaign microsites outside GitHub Pages. |
| 🟧 Replit | Build & host small apps from a prompt. | Booking widgets, calculators, internal tools. |
| 🛰️ claude-code-remote | List / add repos, schedule check-ins. | Pull another repo into a session; self follow-ups. |
claude/<feature>
The hub: azizsaif.com — playbooks, blog, case studies and the EatCookJoy/AI microsites. Every page is hand-built HTML using the house theme. This is where the EatCookJoy SOP and most skills live.
Co-Authored-By trailer unless .claude/settings.json sets attribution.commit. Always apply /eatcookjoy-theme — never invent new colours/fonts.The customer-facing EatCookJoy UAE site (home + per-city / per-service pages). This is the repo the AI General Manager runs against daily.
<video> at preload="none" — reels are hosted off-site; don't make phones download them before render.The EatCookJoy product — a Next.js application. This is real engineering, not a static site, so the discipline skills matter more than the marketing ones.
npm run build && npm test, GitHub opens the PR.node_modules/next/dist/docs/ before writing any code — APIs and file structure differ from training data. Heed deprecation notices.The UAE Next.js build of the EatCookJoy app. Same engineering discipline as the main app.
eatcookjoy app — use /github-multi-repo when a change spans both.A single-page restaurant site — all markup, CSS and JS inline in index.html. Media-heavy (hero / reel videos).
preload="none" so mobile doesn't download before render. Everything is one file; edit surgically.A personal profile / portfolio site (home, inspiration, and a /website-complete playbook page). Has a dedicated run/screenshot skill.
A static launch-plan site (index.html, seo-plan.html, target-markets.html) for the Stackbirds SMB go-to-market.
github.io project path. Keep the three pages consistent.Invoke any with /name. The full live index — with one-line descriptions for all 60+ — lives on the AI Skills page.
Every repo above runs on the same loop: a skill does the work, the GitHub connector ships it on the feature branch.
See a full worked example — the EatCookJoy SOP