Developer Segmentation

by samber98ed86da8babMIT2 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 10 days ago

Cuts a developer audience into a few named, sized and ranked segments - the two dimensions worth cutting on, a size range with a confidence tier, the user/champion/approver/buyer split inside each, a weighted score, one primary and one secondary segment, and a written anti-segment. Use whenever someone asks who their developers actually are, which developer audience to serve first, how big a language ecosystem or persona is, whether to target hobbyists or enterprise platform teams, who signs when the developer is not the buyer, or why content reaches everyone and converts nobody - even if they only say "who is this for". Not the journey map - use samber/developer-relations-skills@developer-journey-map.

Only the file list is public. File contents are available once the skill is installed in a workspace.

PathSizeType
evals/evals.json38.4 KBapplication/json
references/decision-unit.md5.8 KBtext/markdown
references/published-findings.md16.8 KBtext/markdown
references/segment-dimensions.md9.3 KBtext/markdown
references/segment-map-example.md7.7 KBtext/markdown
references/sizing-sources.md8.9 KBtext/markdown
SKILL.md25 KBtext/markdown

Source and attribution

Source:samber/developer-relations-skillsinskills/developer-segmentationat commit98ed86d

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal