NeVibeCode · 9 items
IDE rules for Writing and docs
Rules for Writing and docs: what each one does, an install command and example prompts.
update-docs-on-code-change
official rule A GitHub Copilot rule that flags when README.md and other docs need updating after code changes. Useful when your docs drift behind the code.
★ 40,418repo stars
pcf-manifest-schema
official rule A rule that feeds Copilot the structure of ControlManifest.Input.xml: which elements and attributes exist and what they do. Useful when editing a PCF component manifest.
★ 40,418repo stars
exclude-prompt-data
official rule This rule keeps prompt instructions and commentary out of edited files. Use it when Copilot generates code or documentation from a request.
★ 40,418repo stars
draw-io
official rule Tells Copilot how to build and edit draw.io diagrams: mxGraph XML structure, a semantic colour palette, grid alignment and a validation script.
★ 40,418repo stars
debian-linux
official rule This rule guides Copilot when it writes Debian administration advice, scripts, or docs. Use it for package workflows, service configuration, and security checks.
★ 40,418repo stars
context7
official rule This rule brings Context7 into tasks that depend on current, version-specific API documentation. It is useful when the workspace does not contain the needed external reference.
★ 40,418repo stars
agent-skills
official rule Provides guidelines for creating portable Agent Skills for GitHub Copilot. It ensures SKILL.md files follow proper frontmatter formats, directory structures, and workflow layouts.
★ 40,418repo stars
kubernetes-mkdocs-documentation-cursorrules-prompt rule A Cursor rule that turns the agent into a technical writer for Kubernetes and cloud native docs built with Markdown and MkDocs.
★ 41,011repo stars
how-to-documentation-cursorrules-prompt-file rule A Cursor rule that turns technical steps, test scripts and screenshots into step-by-step guides for non-technical users. Useful when you write How To docs for a feature.
★ 41,011repo stars
