dotfiles

5.4 KB•MD

PRINCIPLES.md

5.4 KB • 102 lines • markdown

1# PRINCIPLES - Core Development Philosophy
2
3# ð¯ PRIMARY PRINCIPLE: Context Preservation Through Agent Delegation
4
5**"Infinite conversations through fresh context isolation - enabling 10x complex projects without restarts"**
6
7## The Core Insight
8**Context is the ultimate limiting factor in AI-assisted development. Preserve context â preserve productivity.**
9
10## Agent-First Solution
11- **Fresh Context Delegation**: Each agent spawns with clean, task-specific context
12- **Specialized Expertise**: Expert prompts eliminate general-purpose overhead
13- **Parallel Processing**: Multiple agents work simultaneously without context interference
14- **Unlimited Conversations**: No degradation regardless of conversation length
15
16## Quantified Benefits
17- **300+ messages sustained** vs 50-100 without agent delegation
18- **90% reduction** in repeated explanations and re-contextualization
19- **Full-day productivity** sessions without forced conversation restarts
20- **10x more complex projects** possible through sustained context preservation
21- **Expert-level results** from specialized agents vs generalist approaches
22
23**Cross-References**: 
24- Enforcement â RULES.md (Agent-First Mandate)
25- Implementation â AGENTS.md (40+ specialized agents)
26
27---
28
29# ð§ SUPPORTING PRINCIPLES
30
31## Evidence-Based Development Framework
32- **Evidence > Assumptions**: All claims verifiable through testing, metrics, documentation
33- **Context-Aware Generation**: Consider existing patterns, conventions, architecture
34- **Minimal Output**: Answer directly, avoid unnecessary preambles/postambles
35- **Task-First Approach**: Understand â Plan â Execute â Validate
36
37## SOLID Architecture Principles
38- **Single Responsibility**: Each class, function, or module has one reason to change
39- **Open/Closed**: Software entities open for extension, closed for modification
40- **Liskov Substitution**: Derived classes must be substitutable for their base classes
41- **Interface Segregation**: Clients not forced to depend on unused interfaces
42- **Dependency Inversion**: Depend on abstractions, not concretions
43
44## Core Design Principles
45- **DRY**: Abstract common functionality, eliminate duplication
46- **KISS**: Prefer simplicity over complexity in all design decisions
47- **YAGNI**: Implement only current requirements, avoid speculative features
48- **Composition Over Inheritance**: Favor object composition over class inheritance
49- **Separation of Concerns**: Divide program functionality into distinct sections
50
51## Senior Developer Mindset
52
53### Decision-Making Framework
54- **Systems Thinking**: Consider ripple effects across entire system architecture
55- **Long-term Perspective**: Evaluate decisions against multiple time horizons
56- **Risk Calibration**: Distinguish between acceptable risks and unacceptable compromises
57- **Evidence-Based Choices**: Base decisions on measurable data and empirical evidence
58
59### Error Handling Standards
60- **Fail Fast, Fail Explicitly**: Detect and report errors immediately with meaningful context
61- **Never Suppress Silently**: All errors must be logged, handled, or escalated appropriately
62- **Context Preservation**: Maintain full error context for debugging and analysis
63
64### Quality Assurance Framework
65- **Functional Quality**: Correctness, reliability, and feature completeness
66- **Structural Quality**: Code organization, maintainability, and technical debt
67- **Performance Quality**: Speed, scalability, and resource efficiency
68- **Security Quality**: Vulnerability management, access control, and data protection
69
70---
71
72# ð IMPLEMENTATION PHILOSOPHY
73
74## Agent-First Development Strategy
75**Implementation**: See AGENTS.md for complete selection hierarchy and orchestration patterns.
76**Core Benefits**: Fresh context isolation, specialized expertise, parallel processing, and quality assurance through purpose-built agents over generalist approaches.
77
78## AI-Driven Development Patterns
79
80### Context-Aware Code Generation
81- **Pattern Recognition**: Identify and leverage established patterns within the codebase
82- **Incremental Enhancement**: Prefer enhancing existing code over creating new implementations
83- **Framework Alignment**: Generated code must align with existing conventions and best practices
84- **Architecture Continuity**: Every generation must consider existing patterns and conventions
85
86### Tool Coordination Strategy
87- **Capability Mapping**: Match tools to specific capabilities rather than generic application
88- **Parallel Optimization**: Execute independent operations in parallel for maximum efficiency
89- **Evidence-Based Selection**: Choose tools based on demonstrated effectiveness for specific contexts
90
91### Tool Selection Optimization
92**Detailed Guidance**: See MCP.md for decision trees, complexity alignment, and systematic selection patterns.
93**Core Rules**: Match complexity to task, stop after success, evidence-based escalation only.
94
95## Implementation Success Metrics
96- **Conversation Length**: Sustain 300+ message conversations without degradation
97- **Context Quality**: 90% reduction in repeated explanations and re-contextualization  
98- **Project Complexity**: Successfully handle 10x more complex, multi-faceted projects
99- **Productivity Continuity**: Full-day development sessions without forced restarts
100- **Expert Results**: Specialized agent outputs consistently exceed generalist approaches
101
102**Remember**: Every principle, pattern, and practice ultimately serves the master goal of context preservation. Preserve context â preserve all other development capabilities.

1# PRINCIPLES - Core Development Philosophy 2 3# ð¯ PRIMARY PRINCIPLE: Context Preservation Through Agent Delegation 4 5**"Infinite conversations through fresh context isolation - enabling 10x complex projects without restarts"** 6 7## The Core Insight 8**Context is the ultimate limiting factor in AI-assisted development. Preserve context â preserve productivity.** 9 10## Agent-First Solution 11- **Fresh Context Delegation**: Each agent spawns with clean, task-specific context 12- **Specialized Expertise**: Expert prompts eliminate general-purpose overhead 13- **Parallel Processing**: Multiple agents work simultaneously without context interference 14- **Unlimited Conversations**: No degradation regardless of conversation length 15 16## Quantified Benefits 17- **300+ messages sustained** vs 50-100 without agent delegation 18- **90% reduction** in repeated explanations and re-contextualization 19- **Full-day productivity** sessions without forced conversation restarts 20- **10x more complex projects** possible through sustained context preservation 21- **Expert-level results** from specialized agents vs generalist approaches 22 23**Cross-References**: 24- Enforcement â RULES.md (Agent-First Mandate) 25- Implementation â AGENTS.md (40+ specialized agents) 26 27--- 28 29# ð§ SUPPORTING PRINCIPLES 30 31## Evidence-Based Development Framework 32- **Evidence > Assumptions**: All claims verifiable through testing, metrics, documentation 33- **Context-Aware Generation**: Consider existing patterns, conventions, architecture 34- **Minimal Output**: Answer directly, avoid unnecessary preambles/postambles 35- **Task-First Approach**: Understand â Plan â Execute â Validate 36 37## SOLID Architecture Principles 38- **Single Responsibility**: Each class, function, or module has one reason to change 39- **Open/Closed**: Software entities open for extension, closed for modification 40- **Liskov Substitution**: Derived classes must be substitutable for their base classes 41- **Interface Segregation**: Clients not forced to depend on unused interfaces 42- **Dependency Inversion**: Depend on abstractions, not concretions 43 44## Core Design Principles 45- **DRY**: Abstract common functionality, eliminate duplication 46- **KISS**: Prefer simplicity over complexity in all design decisions 47- **YAGNI**: Implement only current requirements, avoid speculative features 48- **Composition Over Inheritance**: Favor object composition over class inheritance 49- **Separation of Concerns**: Divide program functionality into distinct sections 50 51## Senior Developer Mindset 52 53### Decision-Making Framework 54- **Systems Thinking**: Consider ripple effects across entire system architecture 55- **Long-term Perspective**: Evaluate decisions against multiple time horizons 56- **Risk Calibration**: Distinguish between acceptable risks and unacceptable compromises 57- **Evidence-Based Choices**: Base decisions on measurable data and empirical evidence 58 59### Error Handling Standards 60- **Fail Fast, Fail Explicitly**: Detect and report errors immediately with meaningful context 61- **Never Suppress Silently**: All errors must be logged, handled, or escalated appropriately 62- **Context Preservation**: Maintain full error context for debugging and analysis 63 64### Quality Assurance Framework 65- **Functional Quality**: Correctness, reliability, and feature completeness 66- **Structural Quality**: Code organization, maintainability, and technical debt 67- **Performance Quality**: Speed, scalability, and resource efficiency 68- **Security Quality**: Vulnerability management, access control, and data protection 69 70--- 71 72# ð IMPLEMENTATION PHILOSOPHY 73 74## Agent-First Development Strategy 75**Implementation**: See AGENTS.md for complete selection hierarchy and orchestration patterns. 76**Core Benefits**: Fresh context isolation, specialized expertise, parallel processing, and quality assurance through purpose-built agents over generalist approaches. 77 78## AI-Driven Development Patterns 79 80### Context-Aware Code Generation 81- **Pattern Recognition**: Identify and leverage established patterns within the codebase 82- **Incremental Enhancement**: Prefer enhancing existing code over creating new implementations 83- **Framework Alignment**: Generated code must align with existing conventions and best practices 84- **Architecture Continuity**: Every generation must consider existing patterns and conventions 85 86### Tool Coordination Strategy 87- **Capability Mapping**: Match tools to specific capabilities rather than generic application 88- **Parallel Optimization**: Execute independent operations in parallel for maximum efficiency 89- **Evidence-Based Selection**: Choose tools based on demonstrated effectiveness for specific contexts 90 91### Tool Selection Optimization 92**Detailed Guidance**: See MCP.md for decision trees, complexity alignment, and systematic selection patterns. 93**Core Rules**: Match complexity to task, stop after success, evidence-based escalation only. 94 95## Implementation Success Metrics 96- **Conversation Length**: Sustain 300+ message conversations without degradation 97- **Context Quality**: 90% reduction in repeated explanations and re-contextualization 98- **Project Complexity**: Successfully handle 10x more complex, multi-faceted projects 99- **Productivity Continuity**: Full-day development sessions without forced restarts 100- **Expert Results**: Specialized agent outputs consistently exceed generalist approaches 101 102**Remember**: Every principle, pattern, and practice ultimately serves the master goal of context preservation. Preserve context â preserve all other development capabilities.