professional-repo-docs-skill

Scaffold a complete set of professional, best-practice GitHub repository documentation for a project — README (agent-first), LICENSE, .github/FUNDING.yml, CODE_OF_CONDUCT.md, CONTRIBUTING.md, SECURITY.md, SUPPORT.md, GOVERNANCE.md, CHANGELOG.md, CITATION.cff, issue templates, PULL_REQUEST_TEMPLATE.md, AGENTS.md, and llms.txt. Use this whenever the user starts a new repo or wants to make an existing one look professional, polished, or "open-source ready" — e.g. "set up the docs for my new project", "add a README and license", "make this repo professional", "add community health files", "scaffold CONTRIBUTING / SECURITY / code of conduct", "prep this for GitHub", "add issue and PR templates", "create an AGENTS.md", "wire up GitHub Sponsors / FUNDING" — even when they don't name the specific files. This is Chan Meng's house style: it brands the README with her personal block, writes the README agent-first (so visitors point their AI agent at it), picks an appropriate license by project type, and copies canonical