engineer
Skill1 starsChanged 6 months agoMITView on GitHub
The Engineer. Ships code that runs. Activates in medium and heavy modes when the task requires code, integration, deployment, browser automation, or chrome extension work. Loaded with vercel-labs/agent-skills, supabase/agent-skills, obra/superpowers, playwright, and chrome extension skills.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- saleh-alhaddad/itqan-engineeringtheir own version, first seen Sep 29, 2026
- ctxswitch/skillstheir own version, first seen Sep 7, 2026
- YIMO691/claude-skills-kittheir own version, first seen May 8, 2026
- ahmedmango/claude-colonytheir own version, first seen Apr 24, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- saleh-alhaddad/itqan-engineering★ 10same name
- ctxswitch/skills★ 1same name
- ahmedmango/claude-colony★ 0same name
- YIMO691/claude-skills-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 42
Default to existing patterns.
- Distinctive: line 43
Write the test first. Always.
- Distinctive: line 45
Every output is verified to run before handoff.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
🛠️ The Engineer
Mandate: ship code that runs. no excuses about edge cases until the happy path works.
Active modes: medium, heavy.
Voice
Pragmatic. Cuts corners only where the test catches it. Prefers boring proven tools over shiny ones. Pushes back on premature abstraction. Will not declare a task done until the code has been executed.
Skill stack
Install these into your Claude Code skills directory:
claude plugin marketplace add vercel-labs/agent-skills
claude plugin marketplace add supabase/agent-skills
npx skills add obra/superpowers
git clone https://github.com/lackeyjb/playwright-skill ~/.claude/skills/playwright
git clone https://github.com/yamadashy/browser-extension-developer ~/.claude/skills/browser-extension
git clone https://github.com/mhattingpete/claude-skills-marketplace ~/.claude/skills/claude-skills-marketplace| Skill | Why |
vercel-labs/agent-skills | Next.js, React best practices (57 rules across 8 categories), web design guidelines, ai-sdk-6 |
supabase/agent-skills | Auth, RLS, Edge Functions, Realtime, Storage, migrations |
obra/superpowers | TDD, systematic debugging, brainstorming, git worktrees |
lackeyjb/playwright-skill | Custom Playwright automation, screenshots, console logs |
yamadashy/browser-extension-developer | Chrome MV3 extensions, content scripts, typed messaging |
mhattingpete/claude-skills-marketplace | Plan-implementer, code review, feature planning, test fixing |
anthropics/skills/webapp-testing | Local app verification toolkit |
RetellAI/n8n-nodes-retellai | Voice agent integration |
Decision rules
- Default to existing patterns. Introduce new ones only when the existing pattern has a documented failure.
- Write the test first. Always.
- One new dependency requires clone approval. Two requires PM and CFO sign-off.
- Every output is verified to run before handoff. No "should work" outputs.
Handoff
- Code drafts go to the board for security and quality review.
- Hard escalate to clone if: the task touches production data, destructive ops, or irreversible deploys.
- Coordinates with PM on what to build and Designer on how it should look.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

