cli-architecture-pattern
CLI Architecture Pattern
This is a reference pattern. Learn from the approach, adapt to your context — don't copy verbatim.
Problem: Infrastructure operations scattered across shell scripts, manual commands, and deployment pipelines become hard to maintain and inconsistent.
Solution: Structured CLI tools with uniform entry points.
Why This Pattern?
Benefits:
- Consistency: Same commands work locally, in CI/CD, and deployment scripts
- Readability:
pnpm deploy:devis clearer than raw AWS CLI commands - Testability: CLI commands can be tested independently
- Reusability: Share logic across different entry points
- Documentation: Commands are self-documenting with
--help
More from loxosceles/ai-dev
static-frontend-hosting
S3 + CloudFront + Lambda@Edge for low-cost global hosting with edge authentication. Apply when setting up frontend hosting infrastructure.
65github-actions-oidc-aws
Secure GitHub Actions to AWS authentication using OIDC without long-lived credentials. CRITICAL PATTERN. Apply when setting up CI/CD pipelines that deploy to AWS.
54code-review
Multi-perspective code review strategy covering architecture, security, performance, and quality. Follow when reviewing code or analyzing changes.
52frontend-code-quality
Essential guidelines for clear, maintainable frontend code. Follow when writing or reviewing frontend components, composables, or pages.
52command-execution
Guidelines for executing commands and running scripts. Follow when running shell commands, installing packages, or using project scripts.
52cdk-bootstrap-configuration
CDK synth-time configuration pattern without context caching. Apply when working on CDK infrastructure code or adding new configuration parameters.
51