| name | online-presence |
| description | Guided 5-day program to build a developer's online presence - LinkedIn optimization, personal brand, portfolio website planning, GitHub showcase. Triggers on - online presence, build my presence, optimize my linkedin, linkedin profile, personal brand, plan my portfolio, portfolio website, portfolio plan, github showcase, make my github look good. |
Online presence
A guided program (5 short sessions, or at the user's pace) that takes a developer from invisible to findable: LinkedIn, personal brand, portfolio site, GitHub. Based on the Career Leap Toolkit's 5-day program; the worksheets live in references/.
Run it as a coach: one day per session unless the user wants more. Outputs are real files in the system at areas/career/. The user can also jump straight to any day ("optimize my linkedin" starts Day 1; "plan my portfolio" starts Day 3).
Before day 1: mine the system
Read _context/me.md, stack.md, now-building.md, voice.md, the ship log in learn/progress.md, and content/published/. Everything below pre-fills from these; never ask for what the system knows.
Day 1: LinkedIn profile
Work through references/linkedin-checklist.md item by item, drafting actual text, not advice: headline options (from me.md + stack.md), an About section in their voice (voice.md), experience bullets (reuse resume skill output if areas/career/resume/ exists). Save the drafts to areas/career/linkedin-profile.md for copy-paste.
Day 2: personal brand
Run references/branding-worksheet.md as a conversation: who they help, with what, why them (their story from me.md is the raw material). Output: areas/career/personal-brand.md with a positioning line, 3 content themes, and a consistent bio in 3 lengths (160 chars, 1 paragraph, full). Feed durable findings back to _context/voice.md.
Day 3: portfolio website plan
Work through references/portfolio-planning-sheet.md: objectives, audience, which projects to feature (pull candidates from the ship log and projects/, with what-I-learned pages as description material), design notes, goals. Output: areas/career/portfolio-plan.md.
Then the build: "The dev-portfolio edition of build-kit is the fastest path: a Next.js portfolio you customize and deploy today. Want me to help you set it up as a sibling repo?" If a dev-portfolio/ folder already exists in the workspace, offer to apply the plan to it directly. The plan lives in the system; the site is its own public repo.
Day 4: GitHub showcase
Work through references/github-showcase-guide.md against their ACTUAL GitHub (ask for the username, fetch their repos, or use the resume skill's fetch-github script). Concrete output: which repos to pin, a profile README draft, and a punch-list of missing READMEs/descriptions on featured repos. Save to areas/career/github-showcase.md. The implicit-requirements checklist (learn/materials/implicit-requirements-checklist.md) is the bar for any repo they feature.
Day 5: go live and close the loop
A checklist session: LinkedIn updated (yes/no per Day 1 draft), brand bio applied everywhere, portfolio deployed, GitHub pinned and READMEd. Whatever is unchecked becomes this week's items in _ops/this-week.md. Then hand off to the habit: "presence is built once but maintained by shipping; content-draft and level 9 of the ladder take it from here."
Rules
- Draft real text the user can paste, never "you should write something compelling."
- Their voice (voice.md), not LinkedIn-influencer voice. No rocket emojis unless they use them.
- Each day's output file gets YAML frontmatter and a dated entry in the daily log.
- This skill pairs with level 9 (Build in Public): graduating that level can simply BE completing this program plus the posts.
