Afrexai System Architect

What This Skill Does

Afrexai System Architect is a high-level strategic reasoning engine designed to assist developers, CTOs, and systems engineers in designing, evaluating, and evolving software architectures. Rather than offering superficial advice, this skill utilizes a rigid, structured framework—the Architecture Discovery Brief—to ensure that technical decisions are based on data, constraints, and long-term scalability rather than temporary trends. It helps you navigate the transition from initial prototyping to enterprise-grade, distributed systems while maintaining focus on core constraints like budget, team velocity, and technical debt.

Installation

To integrate this agent into your workflow, execute the following command in your terminal: clawhub install openclaw/skills/skills/1kalin/afrexai-system-architect

Use Cases

• Greenfield Design: Quickly map out a cloud-native architecture for a startup MVP that considers future growth.
• Migration Strategy: Evaluate whether a current monolith needs to be decomposed into microservices or if a modular monolith would be a safer, more maintainable path.
• Scalability Audits: Perform stress-testing analysis on your current infrastructure based on projected user growth and latency requirements.
• Kill Criteria Verification: Use the skill to objectively determine if your current project should remain a simple monolith to save time and resources, or if it is time to introduce complex distributed patterns.

Example Prompts

1. "I am starting a new fintech app with three developers and a 6-month timeline. Help me fill out the Architecture Discovery Brief and decide between a monolith or modular approach."
2. "Our current Rails monolith is struggling with a 100k user load. Analyze if we should move to microservices or implement a caching and database sharding strategy first."
3. "Evaluate my current system design for a real-time messaging platform: 50k concurrent users, low latency required. Does this meet the threshold for Event-Driven architecture?"

Tips & Limitations

• Be Specific: The accuracy of the architect's output is directly proportional to the detail you provide in the discovery phase.
• Don't Over-engineer: Always consult the 'Kill Criteria' section. If you meet the criteria, the tool is designed to advise you to stop architecting and start shipping code.
• Maintainability: The architect prioritizes long-term maintainability over premature optimization. Be prepared to defend your technical choices against industry-standard patterns.