Extending & Customizing The Architech
Make It Yours
The Architech is designed to be extended and customized. Whether you want to add custom CLI functionality or create an entire marketplace for your ecosystem, we've got you covered.
Two Paths to Customization
Path 1: Extend the CLI (For Power Users)
Customize the CLI engine itself with advanced capabilities.
What you can do:
- π§ Create custom modifiers - Build your own AST-based transformations
- π§ Add custom commands - Extend the CLI with new commands
- π§ Configure genome sources - Add company/team genome libraries
- π§ Customize resolution - Define your own genome resolution strategies
Who this is for:
- Companies with specific code generation needs
- Teams with custom patterns to enforce
- Power users who want CLI-level control
- Those building on top of The Architech
Get Started:
- Custom Modifiers β - Build AST transformations
- Advanced Configuration β - Power user config
Path 2: Create Your Marketplace (For Communities & Companies)
Build a complete marketplace with your technology choices and architectural patterns.
What you can do:
- π― Define your "Golden Core" - Your opinionated standards
- π― Create custom modules - Adapters, connectors, features
- π― Enforce conventions - Your team's best practices
- π― Build for your ecosystem - Vue, Angular, Svelte, or any stack
Who this is for:
- Framework communities (Vue, Angular, Svelte)
- Companies enforcing internal standards
- Open source maintainers sharing best practices
- Domain experts (blockchain, AI/ML, e-commerce)
Get Started:
- Creating Your Marketplace β - Complete guide
Extend vs Contribute
When to Extend (Private/Internal)
Extend the CLI when you:
- Need custom functionality for your organization
- Want to keep modifications private
- Have specific requirements not suited for public marketplace
Create your marketplace when you:
- Have different technology preferences (Vue vs React)
- Want to enforce company standards
- Need domain-specific modules
- Serve a specific community
When to Contribute (Public/Community)
Contribute to core CLI when you:
- Fix bugs in the execution engine
- Improve performance or safety
- Add generally useful CLI features
- Enhance developer experience
Contribute modules to official marketplace when you:
- Build modules that fit our React + Golden Core philosophy
- Want to share with the community
- Create reusable, general-purpose modules
See: Contributing Guide β for contribution process
Quick Decision Guide
I want to...
"Add a new UI library (MUI, Chakra) to the React marketplace" β Contribute to marketplace (public contribution)
"Create a Vue marketplace with Pinia and Vite" β Create your marketplace (new marketplace)
"Build custom AST transformations for my company's code patterns" β Custom modifiers (CLI extension)
"Set up team-shared genome library for our org" β Advanced configuration (CLI config)
"Fix a bug in the VFS or dependency resolver" β Contributing guide (core contribution)
"Create adapters for my company's internal tools" β Create your marketplace (company marketplace)
Architecture Overview
The CLI (Extensible Engine)
The CLI is designed to be extended:
- β Modifier system - Pluggable AST transformations
- β Resolution strategies - Pluggable genome resolution
- β Configuration system - Extensive customization options
- β Service architecture - Modular, composable services
Marketplaces (Composable Ecosystems)
Marketplaces are just TypeScript packages:
- β Standard NPM packages - Use existing infrastructure
- β Auto-generated types - Scripts handle complexity
- β Validation system - Quality assurance built-in
- β Distribution flexibility - npm, git, private registries
Support & Resources
Documentation
- CLI Internals β - Deep dive into CLI architecture
- Architecture β - Understand the module system
- Contributing β - Contribution guidelines
Community
- Discord: #extending channel (opens in a new tab)
- Discussions: GitHub Discussions (opens in a new tab)
- Examples: Study the official marketplace source code
Code References
- Official Marketplace: Complete reference implementation
- CLI Source: See how services are built
- Tests: Unit tests show usage patterns
What You'll Learn
CLI Extension Track
- Modifier API and lifecycle
- AST manipulation with ts-morph
- Testing custom modifiers
- Registering modifiers
- Custom genome sources (git, private npm, local)
- Genome aliases for team standards
- Cache configuration
- Resolution strategy customization
Marketplace Creation Track
- Marketplace structure and organization
- Defining your "Golden Core" standards
- Module development workflow
- Type generation and validation
- Publishing and distribution
Ready to make The Architech truly yours? Choose your path above.