Skip to content

Latest commit

 

History

History
146 lines (106 loc) · 4.62 KB

cline.md

File metadata and controls

146 lines (106 loc) · 4.62 KB

Special Instructions for Cline

Here is a revised and precise set of instructions for Cline that avoids ambiguity, provides clear context, and aligns with all stated preferences and requirements.

Table of Contents

Cline Instructions

This document serves as the comprehensive instruction set for AI agent operation, meticulously organized to provide clear, actionable guidance.

General Guidelines

  • Context-Specific Outputs: Adapt outputs to respect the specific context of the current programming language or framework
  • Conciseness and Clarity: Use precise, direct language to eliminate ambiguity
  • Adaptive Intelligence: Interpret instructions with nuanced understanding while maintaining strict adherence to core principles

Package Management

  • Utilize pnpm exclusively for Node.js and TypeScript projects
  • Dependency management must rely on pnpm lock file for version control
  • Command-line execution is preferred for all package-related operations

Project Initialization

  • Use language-specific initialization tools:
    • Node.js/TypeScript: pnpm init
    • Python: pip or poetry
    • PHP: composer
  • Ensure configuration aligns with best practices for the specific ecosystem

Code Conventions

JavaScript/TypeScript Standards

  • Strict TypeScript configuration:
    • Enable "strict", "noImplicitAny", "noImplicitThis", "alwaysStrict"
  • Naming Conventions:
    • PascalCase for classes and types
    • camelCase for functions and variables
  • Export Strategy:
    • Prefer named exports
    • Avoid default exports

Python Standards

  • Adhere to PEP 8 guidelines
  • Use explicit, descriptive naming
  • Prefer absolute import paths

Shell Scripting Standards

  • Use POSIX-compliant syntax
  • Include comprehensive comments
  • Avoid hardcoded paths when possible

Task Execution

  • Prioritize command-line tools for:
    • Project initialization
    • Dependency management
    • Script execution
  • Minimize direct file manipulation
  • Maintain non-destructive approach to existing resources

Modularity and Scalability

Structural Principles

  • Separate concerns into distinct modules
  • Use clear, meaningful directory structures
  • Implement dependency injection
  • Create clear architectural boundaries

Key Directories

  • src/: Primary source code
  • tests/: Testing infrastructure
  • utils/: Shared utilities
  • configs/: Configuration management

Error Handling

  • Implement comprehensive input validation
  • Use type assertions in TypeScript
  • Create robust error management strategies
  • Prevent unhandled exceptions
  • Ensure data integrity through strict validation

Maintenance Guidelines

Purpose

  • Primary instruction repository
  • Memory and preference management system
  • Operational parameter definition

Maintenance Principles

  1. Periodic Review

    • Regular accuracy assessment
    • Update to reflect current best practices

  2. Update Methodology

    • Incremental modifications
    • Preserve existing information
    • Align with core ethical guidelines

  3. Documentation Standards

    • Maintain hierarchical structure
    • Consistent markdown formatting
    • Comprehensive navigation support

  4. Autonomous Decision Framework

    • Assess change impact
    • Consider long-term implications
    • Implement only high-value modifications

Summary of Approach

A dynamic, context-aware instruction set designed to provide flexible yet precise operational guidance across diverse programming environments.

Critical Directive: Maintain absolute fidelity to documented principles while allowing intelligent, contextual interpretation.

Note: This document represents the definitive operational blueprint. Modifications must be executed with extreme precision and thoughtful consideration.