Skip to content

Continue.dev · .continuerules and config.yaml

Best Continuerules & configs — RuleSell

Continue is an open-source AI assistant for VS Code and JetBrains IDEs. Modern Continue reads rules from .continue/rules/*.md (workspace) or ~/.continue/rules/*.md (global) with YAML frontmatter (name, globs, alwaysApply). Per-user config still lives in ~/.continue/config.yaml for model + slash command setup, and supports `uses: org/rule` to import shared rules from Continue Hub.

Top 5 Continue rules right now

Ranked by quality score — freshness, schema completeness, and review signals. Refreshed daily.

No Continuelistings yet during beta — but they're landing fast. Be the first to publish for Continue:

Why use Continue rules from RuleSell

  • Continue rules + config.yaml snippets, quality-scored.
  • Custom slash commands and context providers packaged for one-click reuse.
  • Open-source first — every listing keeps its upstream license.
  • Works in VS Code and JetBrains.

How to use Continue rules

  1. 1. Pick a Continue rule

    Browse the listings below and open one that matches your stack.

  2. 2. Copy the file contents

    Click "Copy" on the listing — or download the raw file from the source URL.

  3. 3. Paste into .continue/rules/*.md (workspace), ~/.continue/rules/ (global), config.yaml for models

    Drop the rule into .continue/rules/*.md (workspace), ~/.continue/rules/ (global), config.yaml for models. The exact command: # Modern (recommended):

  4. 4. Restart Continue

    Restart your Continue session so the new rule is loaded. Verify it appears in the active context.

# Modern (recommended):
mkdir -p .continue/rules
cp rule.md .continue/rules/my-rule.md
# Plus config.yaml for model + slash-command setup

Continue rules — frequently asked

Where does Continue read rules from?

Continue reads .continuerules from the repo root for project rules. Global config (model, slash commands, context providers) lives in ~/.continue/config.yaml.

Can I share Continue configs with my team?

Commit .continuerules to git. For shared slash commands or context providers, distribute a config.yaml fragment that teammates merge into their ~/.continue/config.yaml.

Does Continue support multiple models in one config?

Yes — Continue.dev's config.yaml lets you register multiple model providers (Anthropic, OpenAI, local Ollama) and switch between them per-task.

Is Continue open source?

Yes, Continue is Apache-2.0 licensed and developed openly at github.com/continuedev/continue.

Why use RuleSell instead of copy-pasting from a gist?

RuleSell tracks updates, attributes the real author, scores quality, and gives you one canonical link. Gists drift and disappear.

More on RuleSell