From dev-like
Profile a tech company or developer's engineering culture from public sources and generate a develop-like-<target> skill that makes the agent work the way they do. Use when the user invokes /dev-like <target>, asks to "develop like <company>", "code like <person>", "adopt <shop>'s engineering practices", or wants a dev-culture profile of a company, team, or individual developer.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-like:dev-like <company | person | alias> (e.g. Every, Theo, theo.gg)<company | person | alias> (e.g. Every, Theo, theo.gg)The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn a shop's public engineering exhaust into an installable `develop-like-<slug>` skill,
Turn a shop's public engineering exhaust into an installable develop-like-<slug> skill,
with a source citation for every claim.
Target: $ARGUMENTS (if empty, ask the user who they want to develop like).
Fetch the registry index and resolve the target against slugs and aliases (case-insensitive):
https://raw.githubusercontent.com/marcusrbrown/dev-like/main/registry/index.json
Every → every; theo.gg, t3.gg, Theo Browne → theo. If ambiguous, ask.
registry/<slug>/profile.md and registry/<slug>/entry.json (same raw URL base).develop-like-<slug> skill from the profile — follow
references/distilling.md..agents/skills/develop-like-<slug>/ and mirror into .claude/skills/ if the
project uses Claude Code (symlink preferred, copy fallback). See
references/harnesses.md for other harnesses.<slug>-developer reviewer/pair agent persona.profile.md + entry.json per references/distilling.md.stated-tier sources or better — never build a person's
profile purely from social posts. Orgs may use the full source taxonomy.registry/OPTOUT.md before profiling anyone; a listed target is a hard stop.Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
npx claudepluginhub marcusrbrown/dev-like --plugin dev-like