experiments: Cursor rule for Cursor

Rempts CLI Development Patterns

Dler framework uses Rempts to build CLI tools.

Follow these patterns when developing CLI functionality in the Rempts framework.

Command Structure

Commands follow a consistent pattern using the core framework:

// In any command file (e.g., packages/cli/src/commands/build.ts)
import { defineCommand, option } from '@reliverse/rempts'
import { z } from 'zod'

export const buildCommand = defineCommand({
  name: 'build',
  description: 'Build the project',
  options: {
    // Define options with Zod validation
    output: option(
      z.string().default('dist'),
      { description: 'Output directory', short: 'o' }
    ),
    compress: option(
      z.boolean().default(false),
      { description: 'Compress output' }
    )
  },
  handler: async ({ flags, positional, shell, env, cwd, prompt, spinner, colors, context }) => {
    // Access type-safe flags
    const spin = spinner(`Building to ${flags.output}...`)
    spin.start()
    
    // Access plugin context if available
    if (context?.env.isAIAgent) {
      console.log(`AI Agent detected: ${context.store.aiAgents.join(', ')}`)
    }
    
    // Implementation
    await shell`bun build src/index.ts --outdir ${flags.output}`
    spin.succeed('Build complete!')
  }
})

Configuration

• Use dler.config.ts files for project configuration
• Configuration is defined using packages/core/src/types.ts
• See examples in examples/ for different config patterns

File Naming

• Use kebab-case for all files: my-command.ts not MyCommand.ts
• Commands go in commands/ directory
• Use .js extensions for all local imports (ESM requirement)
• Keep files focused on single responsibilities

Error Handling

• Use utilities from the handler context: relico.error(), relico.warn(), relico.info()
• Throw meaningful errors with helpful messages
• Zod schemas provide automatic validation for command options
• Use validation from packages/utils/src/validation.ts