chore: polish repo with community files, README header, and GitHub settings

Add Continue banner, centered header, and Contributing/License sections to
README. Add SECURITY.md, issue templates, PR template, and release.yml.
Configure GitHub repo description, topics, and branch protection ruleset
requiring 1 review on main.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: sestinj

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,43 @@
+name: Bug Report
+description: Report a bug in the rules CLI
+labels: ["bug"]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the bug
+      description: A clear and concise description of what the bug is.
+    validations:
+      required: true
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to reproduce
+      description: Steps to reproduce the behavior.
+      placeholder: |
+        1. Run `rules init`
+        2. Run `rules add ...`
+        3. See error
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+      description: What you expected to happen.
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: CLI version
+      description: Output of `rules --version`
+    validations:
+      required: false
+  - type: input
+    id: os
+    attributes:
+      label: Operating system
+      description: e.g. macOS 15.2, Ubuntu 24.04, Windows 11
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,25 @@
+name: Feature Request
+description: Suggest an enhancement or new feature
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: What problem does this feature solve?
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed solution
+      description: Describe the solution you'd like.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Any alternative solutions or features you've considered.
+    validations:
+      required: false

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,11 @@
+## Summary
+
+<!-- Brief description of what this PR does and why -->
+
+## Changes
+
+<!-- List the key changes -->
+
+## Test plan
+
+<!-- How was this tested? -->

.github/assets/continue-banner.png

@@ -0,0 +1,11 @@
+changelog:
+  categories:
+    - title: New Features
+      labels:
+        - enhancement
+    - title: Bug Fixes
+      labels:
+        - bug
+    - title: Other Changes
+      labels:
+        - "*"

.github/release.yml

@@ -1,4 +1,16 @@
-# rules
+<p align="center">
+  <a href="https://continue.dev">
+    <img src=".github/assets/continue-banner.png" width="800" alt="Continue" />
+  </a>
+</p>
+
+<h1 align="center">rules</h1>
+
+<p align="center">A CLI for managing rules across any AI developer tool.</p>
+
+<p align="center"><em>An autonomous codebase built by the <a href="https://continue.dev/blueprint">Continue Software Factory</a></em></p>
+
+---
 
 > **tl;dr:** `npm i -g rules-cli` then `rules add starter/nextjs-rules`
 
@@ -58,3 +70,12 @@ If you are building a developer tool and want to optimize how AI IDEs work with
 1. Make your account on the [registry](https://hub.continue.dev/signup) and create an organization
 2. [Publish your rules](index.md#publish-rules)
 3. Mention the corresponding `rules add <name-of-rules>` command in your documentation
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development guidelines and how to get involved.
+
+## License
+
+Apache-2.0 -- see [LICENSE](LICENSE) for details.
+Copyright (c) 2025 Continue Dev, Inc.

README.md

@@ -0,0 +1,13 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability, please report it responsibly by emailing **security@continue.dev**.
+
+Please do **not** open a public GitHub issue for security vulnerabilities.
+
+We will acknowledge your report within 48 hours and aim to provide a fix or mitigation plan within 7 days.
+
+## Scope
+
+This policy applies to the `rules` CLI tool and its published releases.