modular-architecture-documentation-module-naming
Sub-skill of modular-architecture-documentation: Module Naming (+4).
Best use case
modular-architecture-documentation-module-naming is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of modular-architecture-documentation: Module Naming (+4).
Teams using modular-architecture-documentation-module-naming 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/module-naming/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How modular-architecture-documentation-module-naming Compares
| Feature / Agent | modular-architecture-documentation-module-naming | 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: Module Naming (+4).
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
# Module Naming (+4) ## Module Naming - **Use domain names, not technical terms:** - ✅ `invoice`, `tax_prep`, `tax_file` - ❌ `module1`, `processor`, `generator` - **Keep names short and memorable:** - ✅ `invoice-gen` (CLI command) - ❌ `invoice_generation_automation_tool` ## Module Boundaries - **One module = one CLI command = one purpose** - **Clear inputs/outputs per module** - **No circular dependencies between modules** - **Minimize shared components** (only truly shared code) ## CLI Command Design - **Consistent flag naming across modules:** - `--help`, `--verbose`, `--dry-run`, `--config` - **Intuitive command names reflecting actions:** - `invoice-gen`, `tax-prep`, `tax-file` - **Comprehensive help text with examples** ## Documentation Standards - **Document in tech-stack.md:** Module structure, CLI commands, adoption path - **Record in decisions.md:** Why modular, alternatives considered, consequences - **Update roadmap.md:** Phased implementation per module - **Maintain README:** Quick start per module ## Testing Independence - **Each module has test directory:** ``` tests/ ├── invoice/ ├── tax_prep/ ├── tax_file/ └── shared/ ``` - **Mock other modules in tests** (don't depend on them) - **80% coverage per module, 95% for critical**
Related Skills
module-lookup
Query the digitalmodel module registry to discover modules by capability, standard, or maturity without reading source code.
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.
module-based-refactor
Reorganize a repository from flat structure to a module-based 5-layer architecture (src/tests/specs/docs/examples) while preserving git history. Use when restructuring a codebase into modules, migrating import paths, cleaning up hidden folders, consolidating duplicate directories, removing root-level artifacts, or archiving completed plan files. Capabilities: parallel agent spawn strategy, hidden-folder consolidation patterns, benchmark fixture separation, 4-phase atomic commit workflow.