gmailarchiver-patterns
GMailArchiver architecture, layer patterns, and component design. Use when working with cli, core, data, connectors, or shared layers, or understanding component dependencies. Triggers on: architecture, layer, pattern, component, cli layer, core layer, data layer, SOLID, dependency, contract.
When & Why to Use This Skill
This Claude skill provides comprehensive guidance on the GMailArchiver system architecture, focusing on layer patterns, component design, and SOLID principles. It serves as a central reference for developers to maintain code integrity across CLI, core, data, and connector layers while adhering to established coding standards and development workflows.
Use Cases
- Architectural Guidance: Navigating the layer-based architecture (cli, core, data, connectors) to ensure proper component separation and dependency management.
- Pattern Implementation: Applying SOLID principles and project-specific coding patterns when developing new modules or refactoring existing code.
- Workflow Compliance: Following the 6-phase development process and quality gates defined in the project's process documentation to ensure high-quality delivery.
- Standardization: Maintaining consistency in error handling, type hinting, and style guidelines across the entire codebase by referencing authoritative source documentation.
| name | gmailarchiver-patterns |
|---|---|
| description | >- |
| component dependencies. Triggers on | architecture, layer, pattern, component, |
GMailArchiver Coding Patterns
This skill provides guidance on coding patterns and conventions for GMailArchiver.
Source Documentation
Always read the authoritative sources for current patterns:
CLAUDE.md- Quick reference for AI assistants, includes:- Project overview
- Development commands
- Architecture summary
- Key patterns and safety architecture
docs/ARCHITECTURE.md- Complete system architecture:- Layer-based architecture (cli, core, data, connectors, shared)
- Layer dependency rules and contracts
- Data integrity architecture
- Component responsibilities
docs/CODING.md- Coding standards:- Style guidelines (line length, imports)
- Type hint requirements
- Error handling patterns
docs/PROCESS.md- Development workflow:- 6-phase development process
- Definition of done
- Quality gates
Layer Documentation
Each layer has its own architecture documentation:
src/gmailarchiver/cli/ARCHITECTURE.md- CLI layer designsrc/gmailarchiver/core/ARCHITECTURE.md- Business logic designsrc/gmailarchiver/data/ARCHITECTURE.md- Data layer designsrc/gmailarchiver/connectors/ARCHITECTURE.md- Connectors designsrc/gmailarchiver/shared/ARCHITECTURE.md- Shared utilities design
Usage
When working on code:
- Read the relevant ARCHITECTURE.md files for the layer(s) you're modifying
- Follow patterns documented in those files
- If patterns change, update the documentation (not this skill)
The source documentation is the single source of truth - this skill just points you there.