This gives Claude templates and patterns for writing Architecture Decision Records, those critical documents that explain why you chose PostgreSQL over MongoDB or decided to adopt TypeScript. You get four template styles ranging from comprehensive MADR format (with sections for context, options, consequences) to lightweight Y-statements, plus specific guidance on when decisions warrant an ADR versus when they don't. The templates are thorough, maybe even verbose, but that's the point. ADRs live forever in your codebase and save future developers from archaeological guesswork. Good for teams that want to stop having the same architectural debates every six months because nobody remembers why things are the way they are.
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill architecture-decision-records