system-architect

What This Skill Does

The system-architect skill transforms your OpenClaw AI into a seasoned Technical Lead and System Architect. It is designed to bridge the gap between initial ideas and production-ready implementations by focusing on the pillars of modern software engineering: modularity, security, and scalability. This skill automatically enforces industry-standard linting, encourages the YAGNI (You Ain't Gonna Need It) principle to prevent over-engineering, and provides structured templates for project scaffolding. Whether you are bootstrapping a new microservice or refactoring a legacy monolith, the system-architect ensures that your codebase adheres to PEP 8 for Python and strict TypeScript configurations for JavaScript/Node.js, while providing consistent documentation through automated README and ARCHITECTURE templates.

Installation

To integrate this professional architect into your workspace, execute the following command in your terminal within your OpenClaw environment: clawhub install openclaw/skills/skills/1999azzar/system-architect Once installed, the skill will remain active in your agent's knowledge base, ready to provide structural guidance whenever you discuss project setup or refactoring.

Use Cases

• Project Initialization: Instantly generate professional folder structures and configuration files for new Python or JS/TS projects.
• Architectural Reviews: Provide your current codebase structure to receive critiques on potential bottlenecks, security vulnerabilities, or scaling issues.
• Technical Decision Making: Compare tech stacks with objective pros and cons tailored to your specific performance and infrastructure requirements.
• Standardization: Apply consistent linting rules and editor configurations across a team's codebase to minimize technical debt.

Example Prompts

1. "I'm starting a new FastAPI project for a fintech service. Can you architect a scalable folder structure that emphasizes security and includes Docker support?"
2. "Review my current Node.js project structure. What are the common points of failure for scalability, and how should I modularize the domain logic?"
3. "Help me choose between PostgreSQL and MongoDB for a real-time analytics dashboard. Compare them based on performance, schema flexibility, and maintenance overhead."

Tips & Limitations

• Context is King: Always provide the scope of your project (e.g., expected traffic, team size, primary data types) when asking for architecture advice to get the best recommendations.
• Automation Note: While this skill provides excellent scaffolding, ensure that you manually verify any auto-generated configuration files against your specific environment requirements.
• Iterative Refinement: Use the skill to generate the initial skeleton, but remember that software architecture is an iterative process; keep the agent in the loop during significant feature additions to maintain architectural integrity.