conventions-maintainer

Organize team convention docs under ~/.agents/docs with an AGENTS.md index.

3|Updated Jan 14, 2014
One-click install
npx skills add https://github.com/prateek/dotfiles --skill conventions-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventions-maintainer
Source: https://github.com/prateek/dotfiles/tree/main/.agents/skills/conventions-maintainer
Command: npx skills add https://github.com/prateek/dotfiles --skill conventions-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams keep local convention guidance organized and discoverable by centralizing docs under ~/.agents/docs and pointing at a succinct index at ~/.agents/AGENTS.md.

Core Features & Use Cases

  • Centralized convention documents for topics such as Slack, Git, Go, Linear, and Google Workspace.
  • A pointer index at ~/.agents/AGENTS.md that references the docs, reducing duplication.
  • A clear maintenance workflow that ensures consistency and easy updates.

Quick Start

Create or update a convention document at ~/.agents/docs/<topic>.md and ensure ~/.agents/AGENTS.md points to it.

Frequently Asked Questions about conventions-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize local convention docs for team workflows like Slack and Git?

Organize local convention docs by placing focused playbooks in ~/.agents/docs and maintaining a navigational index pointer at ~/.agents/AGENTS.md. This centralizes team workflow guidance for tools like Slack, Git, Go, and Linear while reducing duplication across documents.

What is the best way to keep an index of agent playbooks synced with individual docs?

Keep agent playbook indexes synced by using ~/.agents/AGENTS.md as a navigational pointer to the individual documents stored under ~/.agents/docs. The maintenance workflow ensures this index stays updated whenever convention documents are created or modified.

Does this convention docs approach work for Google Workspace and Linear workflows?

Yes, this convention docs approach works for Google Workspace and Linear workflows. It applies to any team workflow stored under ~/.agents/docs, allowing you to centralize guidance for Slack, Git, Go, Linear, and Google Workspace under a unified index.

How do I structure a new convention document for team workflows?

Structure a new convention document by following the enforced core outline: Purpose, When to use, Defaults, Workflow, and Validation checklist. Create the file at ~/.agents/docs/<topic>.md and ensure ~/.agents/AGENTS.md points to it.

Why use a centralized index for local convention documentation instead of scattered files?

Use a centralized index for local convention documentation to reduce duplication and keep guidance discoverable. By storing docs in ~/.agents/docs and pointing at ~/.agents/AGENTS.md, teams navigate workflows efficiently without searching through scattered files.