docs(readme): "Made by" app links + Sponsor button

[hamen]

Adds a Made by section at the end of the README linking all of Ivan's live app sites, and a .github/FUNDING.yml Sponsor button.

Why: the repo has a warm, high-trust dev audience. README/profile links are nofollow (no DR lift) but drive real referral traffic + installs, which is what ad/subscription-monetized apps need. UTM tags (utm_campaign=compose_skill) let GA4 attribute installs back to this repo.

Changes

• README.md: new ## Made by section (10 app links + hub + X handle)
• .github/FUNDING.yml: Sponsor button → GitHub Sponsors (github: [hamen]), per cross-review (the button must target a funding destination, not a commercial hub)

🤖 Generated with Claude Code

https://claude.ai/code/session_01BDaGsxPqiYywmcQLuFQRuH

[hamen]

🟢 Codex review (automated cross-review)

Blocker

None.

Should-fix

None.

Nit

• The PR body still says .github/FUNDING.yml points to ivanmorgillo.com; the latest commit correctly changed it to github: [hamen]. Update the description to match.

All added links resolve successfully; the change otherwise looks good.

_{via pr-review-relay · author: claude}

[hamen]

🔵 Cursor review (automated cross-review)

PR #14 Review — docs(readme): "Made by" app links + Sponsor button

Docs-only (+20 lines). I read the PR via gh, the full diff, and the touched files in the worktree. All 11 external URLs return HTTP 200; ivanmorgillo.com redirects to www.ivanmorgillo.com with UTMs preserved. github.com/sponsors/hamen also resolves. No code, CI, or security surface area is affected.

---

Blocker

None.

---

Should-fix

PR description is stale vs. the actual diff. The body says .github/FUNDING.yml points to the ivanmorgillo.com hub, but the file uses github: [hamen] (GitHub Sponsors). That’s the correct YAML for a Sponsor button and matches a live sponsors page — just update the PR text so reviewers aren’t misled. (Prior automated reviews that flagged a custom: portfolio URL appear to be reviewing an older revision.)

---

Nit

• UTM parity: App and hub links all carry utm_source=github&utm_medium=readme&utm_campaign=compose_skill; the @hamen link does not. Add UTMs there only if you want X click attribution in GA4.
• Maintenance: Ten hardcoded app entries will need manual README edits as the portfolio changes. Reasonable tradeoff if per-app README attribution matters; otherwise the hub link alone is easier to keep current.
• Placement: ## Made by sits cleanly between the layout tree block and ## License — consistent with the README’s footer-style sections and non-intrusive for a maintainer-owned repo.

---

Verdict: Looks good — safe to merge. Only actionable item is aligning the PR description with github: [hamen] in FUNDING.yml.

_{via pr-review-relay · author: claude}

[hamen]

🟠 Antigravity review (automated cross-review)

Looks good — safe to merge.

_{via pr-review-relay · author: claude}