helpers4 for AI assistants
An assistant that does not know a helper exists writes it again. helpers4 gives assistants two things so they use what is already there instead:
- References they can read —
llms.txtfiles: a site index and one complete reference per library, in plain text, kept in step with every release. - Plugins they can run — assistant plugins with skills that scan a project and propose the helpers4 replacement, or audit a CI against the helpers4 CI guide. Claude Code first; other assistants will follow.
Quick Links
Section titled “Quick Links”- llms.txt — what each file holds and how to point an agent at it
- Claude Code plugin — install it in two commands
- GitHub · License (LGPL-3.0)
Which one do I need?
Section titled “Which one do I need?”| You want to… | Use |
|---|---|
| Let any assistant check whether a helper already exists | /llms.txt, then the library’s llms-full.txt |
| Replace hand-written code, devcontainer setup or CI steps in a project | the replace-with-helpers4 skill |
| Review or write a GitHub Actions CI | the ci-guidelines skill |
| Ask questions about a repository | DeepWiki ↗ (TypeScript, Dev Container, GitHub Actions) |
Contributing
Section titled “Contributing”Skills are plain SKILL.md folders in helpers4/ai, so they can be packaged for other assistants without being rewritten. Open an issue to ask for an assistant or a skill.