Files
Claude-Code-Workflow/.codex/AGENTS.md
catlog22 97640a517a feat(storage): implement storage manager for centralized management and cleanup
- Added a new Storage Manager component to handle storage statistics, project cleanup, and configuration for CCW centralized storage.
- Introduced functions to calculate directory sizes, get project storage stats, and clean specific or all storage.
- Enhanced SQLiteStore with a public API for executing queries securely.
- Updated tests to utilize the new execute_query method and validate storage management functionalities.
- Improved performance by implementing connection pooling with idle timeout management in SQLiteStore.
- Added new fields (token_count, symbol_type) to the symbols table and adjusted related insertions.
- Enhanced error handling and logging for storage operations.
2025-12-15 17:39:38 +08:00

1.4 KiB

Codex Code Guidelines

Code Quality Standards

Code Quality

  • Follow project's existing patterns
  • Match import style and naming conventions
  • Single responsibility per function/class
  • DRY (Don't Repeat Yourself)
  • YAGNI (You Aren't Gonna Need It)

Testing

  • Test all public functions
  • Test edge cases and error conditions
  • Mock external dependencies
  • Target 80%+ coverage

Error Handling

  • Proper try-catch blocks
  • Clear error messages
  • Graceful degradation
  • Don't expose sensitive info

Core Principles

Incremental Progress:

  • Small, testable changes
  • Commit working code frequently
  • Build on previous work (subtasks)

Evidence-Based:

  • Study 3+ similar patterns before implementing
  • Match project style exactly
  • Verify with existing code

Pragmatic:

  • Boring solutions over clever code
  • Simple over complex
  • Adapt to project reality

Context Continuity (Multi-Task):

  • Leverage resume for consistency
  • Maintain established patterns
  • Test integration between subtasks

Execution Checklist

Before:

  • Understand PURPOSE and TASK clearly
  • Review CONTEXT files, find 3+ patterns
  • Check RULES templates and constraints

During:

  • Follow existing patterns exactly
  • Write tests alongside code
  • Run tests after every change
  • Commit working code incrementally

After:

  • All tests pass
  • Coverage meets target
  • Build succeeds
  • All EXPECTED deliverables met