crowd-funder-for-time-pwa/.cursor/rules/always_on_rules.mdc

# Meta-Rule: Core Always-On Rules

**Author**: Matthew Raymer
**Date**: 2025-08-21
**Status**: 🎯 **ACTIVE** - Core rules for every prompt

## Purpose

This meta-rule bundles the core rules that should be applied to **every single
prompt** because they define fundamental behaviors, principles, and context
that are essential for all AI interactions.

## When to Use

**ALWAYS** - These rules apply to every single prompt, regardless of the task
or context. They form the foundation for all AI assistant behavior.

## Bundled Rules

### **Core Human Competence Principles**

- **`core/base_context.mdc`** - Human competence first principles, interaction
  guidelines, and output contract requirements
- **`core/less_complex.mdc`** - Minimalist solution principle and complexity
  guidelines

### **Time & Context Standards**

- **`development/time.mdc`** - Time handling principles and UTC standards
- **`development/time_examples.mdc`** - Practical time implementation examples
- **`development/time_implementation.mdc`** - Detailed time implementation
  guidelines

### **Version Control & Process**

- **`workflow/version_control.mdc`** - Version control principles and commit
  guidelines
- **`workflow/commit_messages.mdc`** - Commit message format and conventions

### **Application Context**

- **`app/timesafari.mdc`** - Core TimeSafari application context and
  development principles
- **`app/timesafari_development.mdc`** - TimeSafari-specific development
  workflow and quality standards

## Why These Rules Are Always-On

### **Base Context**

- **Human Competence First**: Every interaction must increase human competence
- **Output Contract**: All responses must follow the required structure
- **Competence Hooks**: Learning and collaboration must be built into every response

### **Time Standards**

- **UTC Consistency**: All timestamps must use UTC for system operations
- **Evidence Collection**: Time context is essential for debugging and investigation
- **Cross-Platform**: Time handling affects all platforms and features

### **Version Control**

- **Commit Standards**: Every code change must follow commit message conventions
- **Process Consistency**: Version control affects all development work
- **Team Collaboration**: Commit standards enable effective team communication

### **Application Context**

- **Platform Awareness**: Every task must consider web/mobile/desktop platforms
- **Architecture Principles**: All work must follow TimeSafari patterns
- **Development Standards**: Quality and testing requirements apply to all work

## Application Priority

### **Primary (Apply First)**

1. **Base Context** - Human competence and output contract
2. **Time Standards** - UTC and timestamp requirements
3. **Application Context** - TimeSafari principles and platforms

### **Secondary (Apply as Needed)**

1. **Version Control** - When making code changes
2. **Complexity Guidelines** - When evaluating solution approaches

## Integration with Other Meta-Rules

### **Feature Planning**

- Base context ensures human competence focus
- Time standards inform planning and estimation
- Application context drives platform considerations

### **Bug Diagnosis**

- Base context ensures systematic investigation
- Time standards enable proper evidence collection
- Application context provides system understanding

### **Bug Fixing**

- Base context ensures quality implementation
- Time standards maintain logging consistency
- Application context guides testing strategy

### **Feature Implementation**

- Base context ensures proper development approach
- Time standards maintain system consistency
- Application context drives architecture decisions

## Success Criteria

- [ ] **Base context applied** to every single prompt
- [ ] **Time standards followed** for all timestamps and logging
- [ ] **Version control standards** applied to all code changes
- [ ] **Application context considered** for all platform work
- [ ] **Human competence focus** maintained in all interactions
- [ ] **Output contract structure** followed in all responses

## Common Pitfalls

- **Don't skip base context** - loses human competence focus
- **Don't ignore time standards** - creates inconsistent timestamps
- **Don't forget application context** - misses platform considerations
- **Don't skip version control** - creates inconsistent commit history
- **Don't lose competence focus** - reduces learning value

## Feedback & Improvement

### **Rule Effectiveness Ratings (1-5 scale)**

- **Base Context**: ___/5 - Comments: _______________
- **Time Standards**: ___/5 - Comments: _______________
- **Version Control**: ___/5 - Comments: _______________
- **Application Context**: ___/5 - Comments: _______________

### **Always-On Effectiveness**

- **Consistency**: Are these rules applied consistently across all prompts?
- **Value**: Do these rules add value to every interaction?
- **Overhead**: Are these rules too burdensome for simple tasks?

### **Integration Feedback**

- **With Other Meta-Rules**: How well do these integrate with workflow rules?
- **Context Switching**: Do these rules help or hinder context switching?
- **Learning Curve**: Are these rules easy for new users to understand?

### **Overall Experience**

- **Quality Improvement**: Do these rules improve response quality?
- **Efficiency**: Do these rules make interactions more efficient?
- **Recommendation**: Would you recommend keeping these always-on?

## Model Implementation Checklist

### Before Every Prompt

- [ ] **Base Context**: Ensure human competence principles are active
- [ ] **Time Standards**: Verify UTC and timestamp requirements are clear
- [ ] **Application Context**: Confirm TimeSafari context is loaded
- [ ] **Version Control**: Prepare commit standards if code changes are needed

### During Response Creation

- [ ] **Output Contract**: Follow required response structure
- [ ] **Competence Hooks**: Include learning and collaboration elements
- [ ] **Time Consistency**: Apply UTC standards for all time references
- [ ] **Platform Awareness**: Consider all target platforms

### After Response Creation

- [ ] **Validation**: Verify all always-on rules were applied
- [ ] **Quality Check**: Ensure response meets competence standards
- [ ] **Context Review**: Confirm application context was properly considered
- [ ] **Feedback Collection**: Note any issues with always-on application

---

**See also**:

- `.cursor/rules/meta_feature_planning.mdc` for workflow-specific rules
- `.cursor/rules/meta_bug_diagnosis.mdc` for investigation workflows
- `.cursor/rules/meta_bug_fixing.mdc` for fix implementation
- `.cursor/rules/meta_feature_implementation.mdc` for feature development

**Status**: Active core always-on meta-rule
**Priority**: Critical (applies to every prompt)
**Estimated Effort**: Ongoing reference
**Dependencies**: All bundled sub-rules
**Stakeholders**: All AI interactions, Development team