Search results

I'd like to comprehend LLMRule more clear

Status: Open.

#20 In FutureExcited/vibe-rules;

· Phryxia opened on Feb 6, 2026

Add support for @intellectronica/ruler

Status: Open.

#19 In FutureExcited/vibe-rules;

· marianocordoba opened on Sep 16, 2025

Convert functionality does not respect optional metadata from unified format

Status: Open.

#17 In FutureExcited/vibe-rules;

· reteps opened on Jul 25, 2025

Support for Augment Code

Status: Open.

#16 In FutureExcited/vibe-rules;

· KeentGG opened on Jul 2, 2025

Add a list of libraries that use vibe-rules to help people choose packages that are easy to vibe-code with

Status: Open.

#15 In FutureExcited/vibe-rules;

· Floriferous opened on Jul 1, 2025

Add support for npm/pnpm workspaces

Status: Open.

#14 In FutureExcited/vibe-rules;

· Floriferous opened on Jul 1, 2025

Unified format vs ~/.vibe-rules format

Status: Open.

#13 In FutureExcited/vibe-rules;

· reteps opened on Jun 27, 2025

Installation from a project-specific .rules file

Status: Open.

#9 In FutureExcited/vibe-rules;

· reteps opened on Jun 23, 2025

Apparently for claude & codex you can write files into subfolders to create scoped rules

Status: Open.

#8 In FutureExcited/vibe-rules;

· eastlondoner opened on Jun 11, 2025