rulesync 0.17.0 → 0.19.0

package/dist/index.js

@@ -382,6 +382,11 @@ async function parseRulesFromDirectory(aiRulesDir) {
     throw new Error(`Validation errors found:
 ${errors.join("\n")}`);
   }
+  const rootRules = rules.filter((rule) => rule.frontmatter.root);
+  if (rootRules.length > 1) {
+    const rootRuleFiles = rootRules.map((rule) => rule.filepath).join(", ");
+    throw new Error(`Multiple root rules found: ${rootRuleFiles}. Only one rule can have root: true.`);
+  }
   return rules;
 }
 async function parseRuleFile(filepath) {
@@ -666,15 +671,15 @@ async function initCommand() {
 async function createSampleFiles(aiRulesDir) {
   const sampleFiles = [
     {
-      filename: "coding-rules.md",
+      filename: "overview.md",
       content: `---
 root: true
 targets: ["*"]
-description: "General coding standards and best practices"
+description: "Project overview and general development guidelines"
 globs: ["**/*.ts", "**/*.js", "**/*.tsx", "**/*.jsx"]
 ---
 
-# Coding Rules
+# Project Overview
 
 ## General Guidelines
 
@@ -690,54 +695,94 @@ globs: ["**/*.ts", "**/*.js", "**/*.tsx", "**/*.jsx"]
 - Use semicolons
 - Use double quotes for strings
 - Use trailing commas in multi-line objects and arrays
+
+## Architecture Principles
+
+- Organize code by feature, not by file type
+- Keep related files close together
+- Use dependency injection for better testability
+- Implement proper error handling
+- Follow single responsibility principle
 `
     },
     {
-      filename: "naming-conventions.md",
+      filename: "frontend.md",
       content: `---
 root: false
 targets: ["*"]
-description: "Naming conventions for variables, functions, and files"
-globs: ["**/*.ts", "**/*.js"]
+description: "Frontend development rules and best practices"
+globs: ["src/components/**/*.tsx", "src/pages/**/*.tsx", "**/*.css", "**/*.scss"]
 ---
 
-# Naming Conventions
+# Frontend Development Rules
+
+## React Components
+
+- Use functional components with hooks
+- Follow PascalCase naming for components
+- Use TypeScript interfaces for props
+- Implement proper error boundaries
+
+## Styling
+
+- Use CSS modules or styled-components
+- Follow BEM methodology for CSS classes
+- Prefer flexbox and grid for layouts
+- Use semantic HTML elements
 
-## Variables and Functions
-- Use camelCase for variables and functions
-- Use descriptive names that explain the purpose
-- Avoid abbreviations unless they are well-known
+## State Management
 
-## Files and Directories
-- Use kebab-case for file names
-- Use PascalCase for component files
-- Use lowercase for directory names
+- Use React hooks for local state
+- Consider Redux or Zustand for global state
+- Avoid prop drilling with context API
+- Keep state as close to where it's used as possible
 
-## Constants
-- Use SCREAMING_SNAKE_CASE for constants
-- Group related constants in enums or const objects
+## Performance
+
+- Use React.memo for expensive components
+- Implement lazy loading for routes
+- Optimize images and assets
+- Use proper key props in lists
 `
     },
     {
-      filename: "architecture.md",
+      filename: "backend.md",
       content: `---
 root: false
-targets: ["copilot", "cursor"]
-description: "Architectural patterns and project structure guidelines"
-globs: ["src/**/*.ts"]
+targets: ["*"]
+description: "Backend development rules and API guidelines"
+globs: ["src/api/**/*.ts", "src/services/**/*.ts", "src/models/**/*.ts"]
 ---
 
-# Architecture Guidelines
+# Backend Development Rules
 
-## Project Structure
-- Organize code by feature, not by file type
-- Keep related files close together
-- Use index files for clean imports
+## API Design
 
-## Design Patterns
-- Use dependency injection for better testability
-- Implement proper error handling
-- Follow single responsibility principle
+- Follow RESTful conventions
+- Use consistent HTTP status codes
+- Implement proper error handling with meaningful messages
+- Use API versioning when necessary
+
+## Database
+
+- Use proper indexing for performance
+- Implement database migrations
+- Follow naming conventions for tables and columns
+- Use transactions for data consistency
+
+## Security
+
+- Validate all input data
+- Use proper authentication and authorization
+- Implement rate limiting
+- Sanitize database queries to prevent SQL injection
+
+## Code Organization
+
+- Use service layer pattern
+- Implement proper logging
+- Use environment variables for configuration
+- Write comprehensive tests for business logic
 `
     }
   ];

package/dist/index.mjs

@@ -359,6 +359,11 @@ async function parseRulesFromDirectory(aiRulesDir) {
     throw new Error(`Validation errors found:
 ${errors.join("\n")}`);
   }
+  const rootRules = rules.filter((rule) => rule.frontmatter.root);
+  if (rootRules.length > 1) {
+    const rootRuleFiles = rootRules.map((rule) => rule.filepath).join(", ");
+    throw new Error(`Multiple root rules found: ${rootRuleFiles}. Only one rule can have root: true.`);
+  }
   return rules;
 }
 async function parseRuleFile(filepath) {
@@ -643,15 +648,15 @@ async function initCommand() {
 async function createSampleFiles(aiRulesDir) {
   const sampleFiles = [
     {
-      filename: "coding-rules.md",
+      filename: "overview.md",
       content: `---
 root: true
 targets: ["*"]
-description: "General coding standards and best practices"
+description: "Project overview and general development guidelines"
 globs: ["**/*.ts", "**/*.js", "**/*.tsx", "**/*.jsx"]
 ---
 
-# Coding Rules
+# Project Overview
 
 ## General Guidelines
 
@@ -667,54 +672,94 @@ globs: ["**/*.ts", "**/*.js", "**/*.tsx", "**/*.jsx"]
 - Use semicolons
 - Use double quotes for strings
 - Use trailing commas in multi-line objects and arrays
+
+## Architecture Principles
+
+- Organize code by feature, not by file type
+- Keep related files close together
+- Use dependency injection for better testability
+- Implement proper error handling
+- Follow single responsibility principle
 `
     },
     {
-      filename: "naming-conventions.md",
+      filename: "frontend.md",
       content: `---
 root: false
 targets: ["*"]
-description: "Naming conventions for variables, functions, and files"
-globs: ["**/*.ts", "**/*.js"]
+description: "Frontend development rules and best practices"
+globs: ["src/components/**/*.tsx", "src/pages/**/*.tsx", "**/*.css", "**/*.scss"]
 ---
 
-# Naming Conventions
+# Frontend Development Rules
+
+## React Components
+
+- Use functional components with hooks
+- Follow PascalCase naming for components
+- Use TypeScript interfaces for props
+- Implement proper error boundaries
+
+## Styling
+
+- Use CSS modules or styled-components
+- Follow BEM methodology for CSS classes
+- Prefer flexbox and grid for layouts
+- Use semantic HTML elements
 
-## Variables and Functions
-- Use camelCase for variables and functions
-- Use descriptive names that explain the purpose
-- Avoid abbreviations unless they are well-known
+## State Management
 
-## Files and Directories
-- Use kebab-case for file names
-- Use PascalCase for component files
-- Use lowercase for directory names
+- Use React hooks for local state
+- Consider Redux or Zustand for global state
+- Avoid prop drilling with context API
+- Keep state as close to where it's used as possible
 
-## Constants
-- Use SCREAMING_SNAKE_CASE for constants
-- Group related constants in enums or const objects
+## Performance
+
+- Use React.memo for expensive components
+- Implement lazy loading for routes
+- Optimize images and assets
+- Use proper key props in lists
 `
     },
     {
-      filename: "architecture.md",
+      filename: "backend.md",
       content: `---
 root: false
-targets: ["copilot", "cursor"]
-description: "Architectural patterns and project structure guidelines"
-globs: ["src/**/*.ts"]
+targets: ["*"]
+description: "Backend development rules and API guidelines"
+globs: ["src/api/**/*.ts", "src/services/**/*.ts", "src/models/**/*.ts"]
 ---
 
-# Architecture Guidelines
+# Backend Development Rules
 
-## Project Structure
-- Organize code by feature, not by file type
-- Keep related files close together
-- Use index files for clean imports
+## API Design
 
-## Design Patterns
-- Use dependency injection for better testability
-- Implement proper error handling
-- Follow single responsibility principle
+- Follow RESTful conventions
+- Use consistent HTTP status codes
+- Implement proper error handling with meaningful messages
+- Use API versioning when necessary
+
+## Database
+
+- Use proper indexing for performance
+- Implement database migrations
+- Follow naming conventions for tables and columns
+- Use transactions for data consistency
+
+## Security
+
+- Validate all input data
+- Use proper authentication and authorization
+- Implement rate limiting
+- Sanitize database queries to prevent SQL injection
+
+## Code Organization
+
+- Use service layer pattern
+- Implement proper logging
+- Use environment variables for configuration
+- Write comprehensive tests for business logic
 `
     }
   ];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rulesync",
-  "version": "0.17.0",
+  "version": "0.19.0",
   "description": "Unified AI rules management CLI tool that generates configuration files for various AI development tools",
   "main": "dist/index.js",
   "module": "dist/index.mjs",