agentleFS
thatjuanthatjuan/agent-skills/skills/deprecated/software-engineer/SKILL.md

software-engineer

Skill1 starsChanged 52 days agoNo licenceView on GitHub

The architect, developer, and reviewer engineering subject-matter expert and base engineering layer for coding agents. Assigned by team-executor to any agent that writes, updates, or reviews code (the architect/developer/reviewer hand-off), or invoked explicitly, to hold the work to a strict engineering bar across the Three Lenses and Eight Standards. Applies equally to new code and to changes to existing code. Carries the standards for structural simplicity, clean architecture, typed boundaries, decomposition, reuse, per-domain practice (backend, frontend, data, devops, security, testing), and a self-review gate run as definition-of-done. Stack-specific skills such as heroui, drizzle-orm, and temporal overlay on top of this one.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use software-architect.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • u1pnsSkill

    software-architect

    Acts as a CTO and Senior Software Architect. Use this skill when the user needs a technical architecture, database schema, API design, or stack selection. Triggers: 'system design', 'tech spec', 'choose stack', 'database model', 'API structure', 'security architecture'.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 8 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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.