PUBLIC GITHUB ACTIVITY, MADE VISUAL

Coder Cards turns public GitHub activity into a colorful, explainable snapshot of how you build.

The card

Your GitHub, as a collectible.

Twelve tiles, one persona — built from your real commits. This is an actual card from the app, not a mockup.

A Coder Card for @octocat showing the persona The Clean Coder, a character stats radar, weekly rhythm chart, tech stack donut, and peak hour chart.

Persona + tagline

The headline of your card.

Your local hours

Peak hour and weekly rhythm in your timezone.

Real tech stack

Measured from lines you changed.

Character stats

Five axes, scored 0–100.

Inside the card

One card. A surprising amount of signal.

Every tile turns a small, explainable pattern in public GitHub activity into something you can explore and share.

Card tile

Code signals

Style findings, identifier patterns, source-file structure, testing activity, guard clauses, exception handling, and whitespace patterns.

How it’s calculated

Signals are sampled from changed public source lines and summarized as explainable observations.

THE TILES

Every number shows its math.

Tap any tile on your card to see exactly how it was calculated and what data went into it. No mystery scores.

Character Stats

Weekly Rhythm

Peak Hour

Work-Life Balance

Commit Energy

Predicted Role

Style Score

Tech Stack

Tests

Commits

Repos

Naming

Character Stats

Your coding shape across five axes, each scored 0–100.

HOW IT’S CALCULATED

Testing compares test files to source files. Code clarity blends style score with naming. Structure looks at function length and whitespace. Defensive coding counts early guards and error handling. Consistency measures how uniformly you name things.

WHAT IT READS

Source files, identifiers, guard clauses, exception handling, and test files from your sampled commits.

Polished Character Stats card tile for @octocat.

The real detail view in the app.

THE TILES

Every number shows its math.

Tap any tile on your card to see exactly how it was calculated and what data went into it. No mystery scores.

Character Stats

Your coding shape across five axes, each scored 0–100.

HOW IT’S CALCULATED

Testing compares test files to source files. Code clarity blends style score with naming. Structure looks at function length and whitespace. Defensive coding counts early guards and error handling. Consistency measures how uniformly you name things.

WHAT IT READS

Source files, identifiers, guard clauses, exception handling, and test files from your sampled commits.

Polished Character Stats card tile for @octocat.

The real detail view in the app.

How it Works.

01

Connect public GitHub

Connect your public GitHub account to start building a card from activity you choose to share.

02

We collect a sample

We collect a sample of public activity and commit changes to surface explainable signals.

03

Your Coder Card is ready

Explore the patterns, keep the snapshot, or share your card with others.

A Coder Card for @octocat showing the persona The Clean Coder, a character stats radar, weekly rhythm chart, tech stack donut, and peak hour chart.

04

Share your card

Copy the image, copy your link, download a PNG, or post straight to X or Reddit.

Scores are heuristics over a collected sample, not a code review.

SHARE

SHARE

Make it yours. Made to Share.

Make it yours. Made to Share.

Share a visual snapshot of public coding activity—save it, send it, or post it with a public card link.

Share a visual snapshot of public coding activity—save it, send it, or post it with a public card link.

Try the frames — same card, four looks.

Mac

Terminal

Windows

Linux

A link that’s yours

Every card has a public page anyone can open — no sign-in required.

Copy, download, or post

Copy the image to your clipboard, download a high-resolution PNG, or post straight to X or Reddit.

Refresh any time

Re-run the analysis whenever your habits change.

A Coder Card for @octocat in the macOS window frame, showing the persona The Clean Coder, character stats, tech stack, and peak hour.

Try the frames — same card, four looks.

Mac

Terminal

Windows

Linux

A link that’s yours

Every card has a public page anyone can open — no sign-in required.

Copy, download, or post

Copy the image to your clipboard, download a high-resolution PNG, or post straight to X or Reddit.

Refresh any time

Re-run the analysis whenever your habits change.

A Coder Card for @octocat in the macOS window frame, showing the persona The Clean Coder, character stats, tech stack, and peak hour.

Try the frames — same card, four looks.

Mac

Terminal

Windows

Linux

A link that’s yours

Every card has a public page anyone can open — no sign-in required.

Copy, download, or post

Copy the image to your clipboard, download a high-resolution PNG, or post straight to X or Reddit.

Refresh any time

Re-run the analysis whenever your habits change.

A Coder Card for @octocat in the macOS window frame, showing the persona The Clean Coder, character stats, tech stack, and peak hour.

Octocat @octocat

Apparently I’m The Clean Coder. 98% style score, 25% testing… we don’t talk about testing.

A Coder Card for @octocat showing the persona The Clean Coder, a character stats radar, weekly rhythm chart, tech stack donut, and peak hour chart.
WHAT’S COMING

What’s coming

Coder Cards is the visual preview of a broader developer-style system.

Bring the developer-style profile behind your card into your coding workflow.

• Style-aware generation shaped by preferred naming, formatting, structure, and documentation patterns.

• A style profile that considers visual, architectural, cognitive, and behavioral code patterns.

• A controllable style-adapter layer—not a claim to replace an IDE, code review, or Copilot.

Join early access →

Deeper personal coding profiles and more useful ways to carry them between workflows.

Team-level style context and shared conventions.

A visual, explainable way to discuss different coding patterns and styles.

What a card is—and isn’t.

Public activity only

Coder Cards uses public GitHub information and collected public repository activity.

Explainable signals

Each card metric can be traced to specific inputs and a plain-language explanation.

A snapshot, not a judgment

The card is a playful, heuristic view of a collected sample—not a code review or professional assessment.

FAQ

Questions, answered.

Still curious? Open a live card and tap any tile to see the math behind it.

What is Coder Cards?

An absolutely free app that turns your public GitHub activity into a colorful, shareable card — your persona, rhythm, tech stack, style score, and more. This page is the intro; the card is made in the app.

Do I need an account?

No separate account. You sign in with GitHub inside the app.

What data does it use?

Your public GitHub activity: commit timestamps, commit messages, repository metadata, and the patches from a random sample of your commits. Private repositories are never accessed.

How long does it take?

Most cards are ready quickly. Big profiles can take a couple of minutes — the analysis keeps running and your card appears when it’s done.

Why does the app ask for my timezone?

GitHub stores commit times in UTC. Your timezone lets your Peak Hour and Weekly Rhythm reflect the hours you actually keep.

How accurate are the scores?

They’re heuristics over a sample of your commits, not a code review. Style, naming, and structure metrics are tuned for Python and JavaScript.

Can I share or download my card?

Yes. From the Share panel under your card you can copy the image, copy your link, download a PNG, or post to X or Reddit.

Can I update my card?

Yes. Hit Refresh on your card to re-run the analysis with your latest activity.

What’s your coding persona?

Open the app, sign in with GitHub, and get your card in minutes.

Public activity only. We never access private repositories.

A Coder Card for @octocat shown on a phone screen.
A Coder Card for @octocat showing the persona The Clean Coder, a character stats radar, weekly rhythm chart, tech stack donut, and peak hour chart.