eigi-stack

A bundled set of skills for Eigi work: understand the code before changing it, follow the repo's backend/frontend standards, delete more than you add, prove it securely, verify it against the running stack, and write it down plainly.

Layout

eigi-stack/
├── plugin.json                  manifest (name, version, skill list)
├── .eigi-stack-provenance.json  per-skill source and copy date
└── skills/
    ├── how/ why/ architect/ figure-it-out/ in-your-own-words/
    ├── unslop/ technical-writing/
    ├── eigi-backend-standards/ eigi-frontend-standards/ eigi-review/ eigi-scope-discipline/
    ├── ponytail/ ponytail-review/
    ├── eigi-security-review/ eigi-security-fixes/
    ├── grilling/ grill-me/
    └── eigi-test/

18 skills, 74 files, 480 KB. Each is a folder with SKILL.md plus any references/ or scripts/ it ships. Frontmatter across all 18 costs about 1,700 tokens per turn once installed; bodies load only when a skill is invoked.

Understanding before changing

Eigi standards

Less code

Security

Verification

Writing

Gaps

The pstack skills (architect, figure-it-out, why, technical-writing) used to name pstack skills and Cursor settings this stack does not ship. Those references were rewritten to point at what is here; see Modified.

Paths that assume an install location

Every skill here is a folder that can sit anywhere. One still assumes a path:

eigi-security-review Step 0 expects the project's own security rules (AGENTS.md section, security-rules.md, docs/SECURITY-DATA-FLOW.md) and says so when they are absent. LRN keeps a rules file at .codex/skills/security-rules.md; it is not bundled here.

The pattern catalogue under eigi-security-review/references/catalog/ ships seventeen topic guides but only three language or infrastructure guides: Python, JavaScript, Docker. Upstream also promised Go, Rust, Java, Kubernetes, Terraform, CI pipeline, and cloud guides; they were never written. The skill says so in Step 4 and reasons from the closest guide instead of implying coverage.

~/.claude/skills/ also holds grill-with-docs, a second alias that calls grilling plus domain-modeling. It is not bundled because domain-modeling isn't: copy both if you want ADR-and-glossary capture during an interview.

Modified

Sources

Required docs

The three profile-driven skills — eigi-review, eigi-test, eigi-security-review — read the project before they act. This is the tree they expect. Every entry is optional on its own: a missing doc costs that line of the profile and the skill says so, rather than inventing one.

docs/architecture.md and docs/known-gaps.md are deliberately not part of this set. The code is the architecture, and the tree can be read directly; deferral status belongs in each spec's own note and in the tracker, where it stays next to the thing it defers.

Using it

Nothing here loads automatically. To make these active, either copy the folders into a project's .claude/skills/, or open eigi-stack/ as its own project.

Both eigi-test and eigi-review resolve a project profile before acting, and both read it from the same place: AGENTS.md plus the docs tree in Required docs. A project without that tree gets a smaller profile, and the skill says which lines it could not fill.