| name | social-redirectors |
| description | Audit and suggest social media URL redirectors for your-domain.com. Scans the current redirector config (SSoT in next.config.mjs), cross-references with social/web presence discovered from the calling repo's context, and recommends new redirectors. Use when user says "check redirectors", "audit redirectors", "suggest redirectors", "social links audit", or wants to add new short URLs to your-domain.com. |
| user-invocable | true |
Social Media Redirectors — Audit & Suggest
Philosophy
your-domain.com is the canonical "link hub." When someone asks "what's your YouTube?" the answer is always your-domain.com/yt. Every public platform USER uses should have a short, memorable redirector.
Alias conventions:
- Full name:
/youtube, /instagram, /linkedin
- Common abbreviation:
/yt, /ig, /li, /tt, /fb, /gh
- Slang/culture alias:
/insta, /shorts
- Rule: if people commonly call the platform by a short name, add it
SSoT Location
All redirectors live in ONE file:
~/repos-secondary/AML-Site\next.config.mjs → socialRedirects array
Format:
{ aliases: ['/slug1', '/slug2'], destination: 'https://full-url' },
Execution Steps
1. Read current redirectors
Read ~/repos-secondary/AML-Site\next.config.mjs
Parse the socialRedirects array. Build a table of what exists.
2. Scan calling repo for social/web references
Search the CURRENT repo (wherever this skill was invoked from) for URLs and mentions of platforms. This gives context about what platforms are actively used.
Grep for:
- URLs: youtube.com, tiktok.com, instagram.com, linkedin.com, x.com, twitter.com,
facebook.com, github.com, discord.gg, discord.com, t.me, telegram.me,
wa.me, whatsapp.com, threads.net, twitch.tv, reddit.com, pinterest.com,
medium.com, substack.com, patreon.com, ko-fi.com, buymeacoffee.com,
calendly.com, cal.com, linktr.ee, behance.net, dribbble.com, producthunt.com,
mastodon.social, bsky.app, spotify.com (podcasts), anchor.fm, apple.com/podcast
- Platform keywords: discord, telegram, whatsapp, threads, twitch, reddit, podcast
- Brand-related: YourCompany, ProjectB, YourBrand
Also check:
- CLAUDE.md files (local + global) for social references
- Reference data (
~/.claude/reference-data/) for contact/social info
- Any
.env or config files mentioning social platform API keys (implies active usage)
- Footer components, about pages, contact pages for social links
3. Cross-reference and identify gaps
Compare discovered platforms against existing redirectors. For each gap:
- Is this a public-facing platform? (private Discord servers don't need redirectors)
- Would someone reasonably ask "what's your X?" for this platform?
- Is there a natural short alias?
4. Present recommendations
Output a report in this format:
## Current Redirectors (N total)
| # | Slug(s) | Destination |
|---|----------------------|--------------------------------------|
| 1 | /youtube, /yt | youtube.com/@YOUR_USERNAME-YourBrand |
| 2 | /shorts | youtube.com/@YOUR_USERNAME-YourBrand/shorts |
| ... |
## Suggested New Redirectors
| # | Slug(s) | Destination | Rationale |
|---|-----------------|--------------------------|----------------------------------|
| 1 | /discord | discord.gg/XXXXX | Found Discord link in PA repo |
| 2 | /cal, /book | calendly.com/your-username | Active booking link in consult |
| ... |
## Potential Alias Additions (for existing redirectors)
| # | Existing slug | Suggested alias | Rationale |
|---|---------------|-----------------|-----------------------------|
| 1 | /linkedin | /in | Common LinkedIn shorthand |
| ... |
5. User approves, then implement
After user selects which to add:
- Edit
~/repos-secondary/AML-Site\next.config.mjs — add to socialRedirects array
- Build verify:
cd ~/repos-secondary/AML-Site && npx next build
- Commit and push (follows dev-loop SOP)
- Wait ~75s for Vercel deploy
- Verify with
curl -sI https://your-domain.com/<slug> — check for 307 + correct Location
- Open in browser:
start https://your-domain.com/<slug>
Common Platform Checklist
When auditing, always check for these platforms (ordered by likelihood):
Tier 1 — Almost certainly used:
- YouTube (channel, shorts, specific playlists)
- LinkedIn
- Instagram
- TikTok
- X / Twitter
- Facebook
- GitHub
Tier 2 — Likely for a founder/creator:
- Discord (community server)
- Telegram (channel or group)
- WhatsApp (business/direct link)
- Threads
- Calendly / Cal.com (booking)
- Newsletter/Substack
- Podcast (Spotify, Apple)
Tier 3 — Niche but worth checking:
- Twitch
- Reddit
- Pinterest
- Medium
- Patreon / Ko-fi / Buy Me a Coffee
- Product Hunt
- Mastodon / Bluesky
- Behance / Dribbble
Tier 4 — Internal/business tools (redirect to branded pages):
/meet or /meeting → Google Meet personal link/consult or /book → booking page (already a page on the site, but could alias)/resume or /cv → hosted resume/CV/deck → pitch deck/store or /shop → e-commerce
Cross-Repo Context
This skill is designed to run from ANY repo. When invoked from:
- PA (PersonalAssistant): Has broadest context — contacts, communications, all platforms
- GH Coordinator: Has GitHub-centric context — repos, orgs, contributor profiles
- AML-Site itself: Has the redirectors directly, plus homepage social links
- Any other repo: Scan for platform references specific to that project
The more repos this runs from, the more complete the audit becomes.
Conflict Avoidance
Before suggesting a slug, verify it doesn't collide with:
- Existing Next.js pages (check
src/app/ directory structure)
- Existing API routes (check
src/app/api/ directory)
- Reserved Next.js paths (
/_next, /api, /favicon.ico, etc.)
Current app routes to avoid: /, /admin, /blog, /consult, /contact, /dictionary, /faq, /meetings, /timer, /verification-success, /unsubscribe-confirmation
