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.

Security Scan

The skill's files, templates, and runtime instructions are coherent with its stated role as a System Architect and do not request extra credentials, installs, or unexpected system access.

Purpose & Capability

Name, description, SKILL.md, and all included templates/references align: scaffolding, linter configs, README/ARCHITECTURE templates, and security checklist are appropriate for an architecture/standards skill. There are no environment variables, binaries, or external services requested that are unrelated to the stated purpose.

Instruction Scope

SKILL.md directs the agent to produce folder structures, tech recommendations, linting configs, and docs. It does not instruct reading local secrets, scanning unrelated files, exfiltrating data, or contacting external endpoints. The rules and references are narrowly scoped to architecture, standards, scaffolding, and security best-practices.

Install Mechanism

No install spec and no code files are present; this is instruction-only so nothing will be downloaded or written by an installer. That minimizes disk-write and supply-chain risk.

Credentials

The skill declares no required environment variables, no credentials, and no config paths. Templates reference .env.example and advise not to commit secrets — appropriate for this purpose and proportionate to functionality.

Persistence & Privilege

always is false and the skill is user-invocable. It does not request persistent/privileged system presence or modify other skills/configs. Autonomous invocation is allowed by platform default but not combined with other red flags.

Assessment

This skill appears to be what it claims: a set of architecture templates and instructions. It's low-risk because it asks for no credentials and has no install. Still: (1) avoid pasting real secrets into prompts or generated .env files; (2) review any generated Dockerfiles, CI configs, or dependency lists before building or deploying; (3) vet any specific package versions the skill recommends before installing; and (4) treat 'git clone ...' placeholders as templates — don't run arbitrary clone commands the skill outputs without verifying the repository URL.

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

• Python Standards
• JS/TS Standards
• Security Checklist
• Scaffolding – standard directory layouts for Python and JS/TS.

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).