Dev Like

dev-like profiles a tech company or developer's engineering culture from public sources only (their shipped agent configs, linter configs, CI files, engineering blogs, talks) and distills it into an installable, spec-compliant Agent Skill: develop-like-every, develop-like-theo, develop-like-<your-heroes>.

Every claim in a generated skill links to the public source it came from. No source, no claim.

Install

# Universal — symlinks into every detected harness (Claude Code, Codex, Cursor, Copilot, ...)
npx skills add marcusrbrown/dev-like

# Claude Code plugin (bare /dev-like command)
/plugin marketplace add marcusrbrown/dev-like
/plugin install dev-like

# CLI — install a cached profile's skill directly, no LLM needed
npx dev-like oxide

Use

/dev-like Every        # cached: installs develop-like-every from the registry
/dev-like Theo         # aliases work: theo.gg, t3.gg, t3
/dev-like SomeNewShop  # uncached: live OSINT profile -> skill -> offers to PR it back

What changes? Same prompt, before and after — see the dry-run transcript: a generic senior-engineer review becomes one that runs on the shop's actual operating model, every point traceable to a cited source.

Registry

Want a shop profiled? Request it — or run /dev-like <target> and PR the result back.

How it works

1. Resolve — target is matched against the registry (slugs + aliases).
2. Cached — the distilled profile.md becomes a develop-like-<slug> skill in your project (.agents/skills/ + .claude/skills/).
3. Uncached — the agent runs the collection workflow across a ranked source taxonomy (revealed preference beats stated preference), builds a cited profile, generates the skill, and offers to contribute the profile back.

Ethics, in one paragraph

Public professional sources only, official APIs over scraping, consent tiers on every profile (self-published > stated > observed > social), a stated-tier floor for individuals, opt-out honored within 48h, and provenance links on every claim. We extract principles and workflow shapes — never reproduce prose.

Development

bun install
bun run validate   # frontmatter + registry schema + index sync + plugin/skill version lockstep
bun run test       # generator, CLI install, link-collection suites

bun run validate also checks that .claude-plugin/plugin.json and the dev-like skill's frontmatter metadata.version stay in lockstep with package.json (the canonical version). The marketplace entry intentionally stays unversioned — plugin.json is authoritative for Claude's plugin resolution. If a check fails, node scripts/sync-release-version.mjs fixes it.

Plain node works too (node scripts/validate.mjs, node --test tests/) — the package has zero runtime dependencies. Provenance links are re-checked weekly in CI; trigger evals and the paired workflow eval live in evals/.

See CONTRIBUTING.md for adding registry profiles.

License

MIT