engineering-skills

A tool-agnostic library of engineering skills and guidelines for AI coding agents — Claude Code, Codex, Cursor, Copilot, Gemini CLI, Lovable and anything else that reads the Agent Skills format.

Install whole packs, not the whole library. Take infra and cloud-yandex and keep your own Go conventions; take go alone; take everything. Skills are layered generic → cloud vendor → your project, so adding AWS later means adding one vendor pack, not rewriting anything.

Packs

Machine-readable index: manifest.json.

The life cycle around the packs

The packs say how to do each engineering thing. sliceworks is the development life cycle they run inside: milestones with ten phases (spark, discover, decide, design, plan, build, accept, release, operate, learn), one ledger of checkable rows, a decisions ledger with veto windows, worktree-isolated slice implementers behind frozen contracts, verification tiers, independent review, budget and money guards, a project survey and dispatcher, and an intake pipeline for requests typed in chat. It is listed in this marketplace and installed from its own repository:

/plugin marketplace add sudo-sane/engineering-skills
/plugin install sliceworks@engineering-skills
/sliceworks:start

Its survey detects which packs a project has installed and recommends the rest for the project’s stack; its phase skills call review-plan, documentation-standards, incident-response, bootstrap-project and the infra pack where they are present.

---

Install

Option 1 — ask your agent (recommended)

Say this to Claude Code, Codex, Cursor, or any agent with file access:

Use github.com/sudo-sane/engineering-skills and install the infra and cloud-yandex packs into this project.

Other phrasings that work: “take the go package from …”, “set this project up with the core and process packs”, “install everything except frontend”.

Option 2 — Claude Code plugin marketplace

/plugin marketplace add sudo-sane/engineering-skills

Then install packs individually — /plugin install infra@engineering-skills, /plugin install cloud-yandex@engineering-skills. Each pack plugin carries its own skills and agents. /plugin install sliceworks@engineering-skills installs the life cycle (see above).

Option 3 — script

git clone https://github.com/sudo-sane/engineering-skills && cd engineering-skills
./scripts/install.sh ~/path/to/project --packs infra,cloud-yandex --tools claude,codex

Omit --packs for an interactive picker. --user installs to ~/.claude/skills etc. instead of into a project. --dry-run shows what would happen.

Option 4 — copy the directories

Packs are plain directories. cp -r skills/infra/* /path/to/project/.agents/skills/.

Lovable

Lovable reads the root AGENTS.md of a connected repo automatically — that is the main integration. For skills, zip a pack directory and upload it in workspace Settings → Skills.

---

Update installed skills

Installed copies carry metadata.source and metadata.version, so an agent can tell which of them are behind the library. Say this to your agent:

Update the skills installed from github.com/sudo-sane/engineering-skills in this project to the library’s current versions.

Other phrasings that work: “bring the installed packs up to date”, “check whether our skills from engineering-skills are stale”, “pull the latest go and database skills”.

With a shell and a clone, the same update is two commands: scripts/check-drift.sh to see what is behind, then scripts/install.sh --packs --tools --force to reinstall those packs — only when nothing is MODIFIED, because --force overwrites every skill in the named packs.

---

First use in a blank project

After installing core, tell your agent: “bootstrap this project”. The bootstrap-project skill asks about your stack, instantiates the templates (AGENTS.md with a filled Project context block, CLAUDE.md pointer, docs/ tree with ADR and runbook templates, Makefile, .secrets.example, .gitignore), and tells you what is left to fill in.

How the layers fit

generic skill        infra/secrets-management   "values never enter git; the
                                                 SECRET_MANAGER capability holds them"
        ↓ Vendor delta
vendor skill         cloud/yandex-cloud         "SECRET_MANAGER = Lockbox + External
                                                 Secrets Operator; [!] the ExternalSecret
                                                 name must match the Helm template"
        ↓ Project delta
your project         AGENTS.md                  "Cloud: yandex-cloud, namespace: acme-prod"

Generic skills never name a vendor. Vendor skills never name your project.

Contributing

See CONTRIBUTING.md and AGENTS.md (the rules agents follow when working on this repo). Improvements go upstream first — never hand-edit an installed copy.

Licence

Apache-2.0.