Professional Repo Docs

Trigger me when the user wants to set up, polish, or professionalize a GitHub repo's docs — new project bootstrap, "add a README / license / contributing guide", "community health files", "make this repo look professional", "prep for open source", "add issue/PR templates", "AGENTS.md", "wire up Sponsors" — even if they don't list the files.

This skill turns any project folder into a professional, agent-first GitHub repository by adding the full set of standard documentation. It encodes hard-won conventions so you don't re-derive them and never regenerates filter-sensitive canonical text (license + code of conduct are copied verbatim).

Core principles (read before running)