modular-architecture-documentation-overview
Sub-skill of modular-architecture-documentation: Overview (+6).
Best use case
modular-architecture-documentation-overview is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of modular-architecture-documentation: Overview (+6).
Teams using modular-architecture-documentation-overview should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/overview/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How modular-architecture-documentation-overview Compares
| Feature / Agent | modular-architecture-documentation-overview | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of modular-architecture-documentation: Overview (+6).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Overview (+6) ## Overview Following DEC-003 (Modular Architecture Decision, 2025-07-27), the system is organized into three independent modules to support gradual feature adoption and independent development cycles. ## Module Structure **Module 1: Invoice Automation** - **Purpose:** Automated invoice generation and delivery - **Scope:** Template processing, data merging, PDF generation, email delivery - **Entry Point:** `aceengineer_admin.invoice:main` - **CLI Command:** `invoice-gen` - **Dependencies:** python-docx, jinja2, plotly (invoice charts) - **Output:** PDF invoices in /reports/invoices/ - **Adoption Phase:** Phase 1 (Weeks 1-2) - 80% time savings **Module 2: Tax Preparation** *See sub-skills for full details.* ## Module Independence Each module: - Can be used independently (invoice-gen works without tax-prep) - Has its own CLI command - Produces standalone outputs - Has dedicated configuration section - Has independent test suite ## Gradual Adoption Path **Phase 1:** Invoice Automation (Weeks 1-2) - Immediate 80% time savings on monthly billing - No dependency on other modules **Phase 2:** Tax Preparation (Weeks 3-4) - Eliminate manual expense categorization - Can be adopted without invoice automation **Phase 3:** Tax Filing (Weeks 5-8) - Streamlined annual compliance - Works with tax prep module or standalone Users can adopt modules in any order based on business priorities. ## CLI Commands ```bash # Module 1: Invoice Automation invoice-gen --client mkt-a --month 2025-01 --template monthly invoice-gen --all-clients --month 2025-01 --email # Module 2: Tax Preparation tax-prep --year 2024 --type federal tax-prep --year 2024 --expense-report --validate # Module 3: Tax Filing tax-file --year 2024 --form 1120 tax-file --year 2024 --form k1 --shareholder all ``` ## Directory Organization ``` src/aceengineer_admin/ ├── invoice/ # Module 1: Invoice Automation │ ├── __init__.py │ ├── __main__.py # CLI entry point │ ├── generator.py # Invoice generation logic │ ├── templates.py # Template processing │ └── config.py # Invoice config ├── tax_prep/ # Module 2: Tax Preparation │ ├── __init__.py *See sub-skills for full details.* ## Testing Strategy - **Unit Tests:** 80% coverage minimum per module, 95% for critical modules - **Integration Tests:** Cross-module workflows (tax prep → tax filing) - **CLI Tests:** Command-line interface validation - **Independence Tests:** Each module testable in isolation with mocks ``` **decisions.md:** ```markdown
Related Skills
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
label-driven-prompt-generation-architecture
Pattern for building automation scripts that classify GitHub issues into prompt templates using label-based routing and extract contextual data for batch processing
documentation-contract-plan-hardening
Harden a documentation/contract plan before adversarial review by mapping every issue-scope requirement to independent acceptance criteria and tests, especially for routing/indexing contracts.
repo-architecture-analysis
Scan a Python repo's package structure, count classes/functions, classify module maturity (PRODUCTION/DEVELOPMENT/SKELETON/GAP), and generate architecture reports with Mermaid diagrams. Use when asked to analyze codebase structure, find untested packages, or assess module maturity.
orcaflex-monolithic-to-modular
Convert monolithic OrcaFlex models (.dat/.yml) to spec-driven modular format with semantic validation for round-trip fidelity.
doc-extraction-naval-architecture
Layer 3 domain sub-skill for extracting naval architecture data from SNAME PNA, IMO stability codes, IACS structural rules, and classification society guidelines. Provides detection heuristics for stability constants, resistance equations, hull form coefficients, hydrostatic curves, IMO stability criteria, and structural scantling tables. type: reference
sparc-architecture
SPARC Architecture phase specialist for system design, component architecture, interface design, scalability planning, and technology selection
architecture-diagram
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
multi-tool-architecture-assessment
Systematic comparison of competing tools/approaches before committing to a multi-account, multi-tool architecture. Uses parallel subagents for research, system-state audit, and data quality analysis. Produces a decision matrix with explicit trade-offs.
modular-architecture-documentation
Systematically document multi-module system architectures including module boundaries, CLI commands, and architecture decisions.
discipline-refactor-orchestration-architecture
Sub-skill of discipline-refactor: Orchestration Architecture.
web-artifacts-builder-self-contained-architecture
Sub-skill of web-artifacts-builder: Self-Contained Architecture (+1).