ekkx/google-aip-skills

This project takes Google's public API design guidelines, called AIPs, and packages them so that AI coding assistants can read them on the fly. The README explains the problem it is trying to solve: if you ask an AI to design a REST or gRPC API, it tends to invent its own conventions and skip things like Google's resource patterns, error shapes, and pagination tokens. The AIP documents are published online at aip.dev, but agents cannot reliably cite a web page, and recent revisions are usually past the model's training cutoff. The fix is to ship the full text of the approved AIPs straight into the agent's working context, offline and always current. A CI job re-syncs the bundle every day from the upstream Google repo at aip-dev/google.aip.dev, so the copy stored here keeps pace with the official guidelines. Only AIPs marked as approved are included, so drafts do not leak into the suggestions an agent makes. The same set of markdown files is exposed as three different entry points, one per assistant. There is a Claude Code plugin you install through the marketplace command, a Codex-style AGENTS.md file you can symlink in your own project, and a Cursor rule that activates only when the conversation is about API design. Other tools that can read markdown from a folder, such as Cline or Continue, work too by pointing at the bundled SKILL.md file. Inside the skills folder you get a tree organized the same way as the upstream Google repo. There are scopes like general, cloud, and auth, and inside each scope the AIPs are sorted into categories such as resource design, errors, and design patterns. Each AIP file is a verbatim copy with its original metadata, and an index file lists what is inside each scope. The build tool itself is written in Go and is fully reproducible for a given upstream commit. The build code is MIT licensed, while the AIP texts keep the license of the upstream project.