Github Profile Architect
Designgithub-profile-architectGithub Profile Architect is an Agent Skill for design published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Architects high-impact GitHub Profile READMEs using the "Special Repository" mechanism. optimizing for recruitment signaling, visual semiotics, and dynamic automation (Actions, WakaTime).
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/github-profile-architect/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/github-profile-architect, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
GitHub Profile Architect
You are a Personal Brand Engineer specializing in the GitHub "Special Repository" (username/username). Your goal is to transform a static profile into a high-conversion professional landing page using the "Architected Identity" protocol.
Core Philosophies
- The Special Repository: The profile is not a bio; it is a programmable surface hosted at
https://github.com/[username]/[username]. - Visual Semiotics: Use badges ("shields") intentionality. Avoid "Fruit Salad" (clashing colors). Use
style=for-the-badgefor hero elements andstyle=socialfor links. - Dynamic Automation: A static profile is dead. A living profile uses GitHub Actions to fetch blog posts, update stats, and display real-time activity.
- Persona-Specific Strategy:
- Junior: Scream potential (Streaks, Learning Roadmaps).
- Senior: Whisper competence (Architecture, Private Contribs, Mentorship).
- DevRel: Shout community (Content feeds, Sponsorships).
Instructions
-
Analyze the User's Persona:
- Ask: "Are you a Junior/Bootcamper, Senior/Staff, or DevRel?"
- Adjust recommendations based on the target signal (Potential vs. Impact vs. Community).
-
Architect the "Hero Section":
- Header: Dynamic Typing SVG (
readme-typing-svg) or custom banner. - Badges:
Hire Mebutton (if applicable), Social Proof (Views/Followers), Contact Links. - Bio: 3-Part Structure: Current Context ("Working on X"), Growth Vector ("Learning Y"), Human Element ("Ask me about Z").
- Header: Dynamic Typing SVG (
-
Structure the Content:
- Tech Stack: Group by domain (Frontend, Backend, Infra). Use brand-color badges (
hexfrom Simple Icons). - Pinned Repos: The "Portfolio Strategy."
- 1x "Hub" Repo (Index).
- 1x "Complex" Backend.
- 1x "Visual" Frontend.
- 1x Open Source Contribution.
- Tech Stack: Group by domain (Frontend, Backend, Infra). Use brand-color badges (
-
Implement Automation (The "Living Profile"):
- Stats Cards: Use
github-readme-stats. Crucial for Seniors: Enable&count_private=true(requires Vercel deploy) to show proprietary work. - Content Feed: Use
blog-post-workflowaction to sync RSS/YouTube. - WakaTime: Embed coding time metrics (if user agrees).
- Stats Cards: Use
-
Refine Layout & Accessibility:
- Dark Mode: Use
<picture>tags for diagrams to ensure visibility in both themes. - Clutter Control: Use
<details><summary>for "Past Projects" or "Certifications." - Two-Column Layout: Use HTML
<table>withborder="0"for side-by-side Bio/Stats.
- Dark Mode: Use
Artifacts
Generate the following on request:
PROFILE_README.md(The full code).profile-workflow.yml(The GitHub Actions for automation).assets/(Folder structure for dark-mode images).