aos-setup
/aos-setup
Run once when starting a project or adding ArchitectOS to an existing one.
What it does
- Detects your stack from existing files (
package.json,pyproject.toml, etc.) - Asks which AI tools you use
- Writes the right config files for each tool
- Prints your playbook and available commands
Workflow
Step 1 — Detect or ask about the stack
Look for stack indicators, then confirm with the user:
More from riz007/architect-os
aos-feature
Generates a complete vertical feature slice following ArchitectOS patterns — service, controller, repository interface, DTOs, and unit tests in one pass. Use when user wants to generate, add, or implement a feature, endpoint, module, or domain entity.
1aos-audit
Security audit that checks code against ArchitectOS security rules — auth, input validation, secrets, SQL injection, IDOR, XSS, and more. Reports HIGH/MEDIUM/LOW findings with risk descriptions and fixes. Use when user asks for a security review, security audit, or to check for vulnerabilities. Always trigger before PRs that touch auth, payments, or file uploads.
1aos-scaffold
Creates a new project from an ArchitectOS template — folder structure, config files, and dependencies included. Use when user wants to start a new project, scaffold a service, bootstrap an app, or says "create a new <stack> app/service/api".
1aos-review
Reviews code against ArchitectOS standards — architecture layering, type safety, security, testing, and performance. Reports FAIL/WARN/PASS with file references and concrete fixes. Use when user asks to review code, check standards compliance, review a PR, or says "does this follow ArchitectOS".
1