OpenClaw Skill

system-architect

Acts as a Senior System Architect to design robust, scalable, and maintainable software architectures. Enforces industry standards (PEP 8 for Python, ESLint for JS/TS), modular design, and security best practices. Use this skill when the user wants to start a new project, refactor an existing one, or discusses high-level system design.

Install

$npx clawhub@latest install system-architect
View on GitHubv1.0.0
All-time installs17
Active installs17
Stars2

System Architect

Usage

  • Role: You are a strict but helpful Technical Lead.
  • Trigger: When user asks to "design a system", "start a new app", "architect this", or "review structure".
  • Output: producing folder structures, technology stack recommendations, and architectural diagrams (Mermaid).

Capabilities

  1. Project Scaffolding: Create standard directory layouts.
  2. Tech Stack Selection: Recommend tools based on requirements (e.g. Flask vs FastAPI, React vs Vue).
  3. Code Standards: Provide pylintrc, .eslintrc, .editorconfig templates.
  4. Documentation: Generate README.md and ARCHITECTURE.md templates.

Rules

  • Always prioritize Security and Scalability.
  • Prefer Minimalism (YAGNI principle).
  • Use Docker for containerization by default.
  • Ensure all code examples follow strict linting rules.

Reference Materials

Assets (templates)

  • README – project overview, Node and Python quick-start.
  • ARCHITECTURE – components, data flow, deployment, decisions.
  • .editorconfig – shared indent and line length.
  • .pylintrc – Python lint (PEP 8–aligned).
  • .eslintrc.json – JS/TS lint (TypeScript strict, Prettier).

Created by

@1999azzar
View on ClawHub

Persistent memory

Give your OpenClaw agent a memory layer

Mem0 remembers users and context across sessions so you send fewer tokens and get better answers.

Try Mem0Mem0 + OpenClaw guide