aiox-architect

Convert system requirements into full-stack architecture with API design and deployment strategy.

Updated May 25, 2026
One-click install
npx skills add https://github.com/FelipeMaines/ProjetoWeb --skill aiox-architect-felipemaines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiox-architect
Source: https://github.com/FelipeMaines/ProjetoWeb/tree/main/.claude/skills/AIOX/agents/architect
Command: npx skills add https://github.com/FelipeMaines/ProjetoWeb --skill aiox-architect-felipemaines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you create sound, end-to-end system architecture by translating requirements into coherent decisions across frontend, backend, APIs, infrastructure, and security.

Core Features & Use Cases

  • Full-stack and layer-focused architecture generation: Produce complete system designs or targeted frontend/backend architecture with clear boundaries and integration points.
  • Technology stack selection and API design: Evaluate and select technologies while designing consistent APIs (REST/GraphQL/tRPC/WebSocket) and communication patterns.
  • Architecture documentation and validation workflow: Generate project documentation, run architecture checklists, assess complexity, and produce an implementation plan.

Quick Start

Activate the architect agent to design a complete full-stack architecture for your new feature and technology stack.

Frequently Asked Questions about aiox-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design full-stack architecture for a new software project?

Full-stack architecture design translates system requirements into coherent decisions across frontend, backend, APIs, infrastructure, and security. This approach ensures holistic component integration and production-oriented structuring supported by planning and checklist workflows.

What is the best way to select a technology stack for my application?

Technology stack selection involves evaluating and selecting technologies while designing consistent APIs like REST, GraphQL, tRPC, or WebSocket. This ensures your communication patterns align with your specific frontend and backend architectural boundaries.

How do I plan API design for a full-stack system?

API design for a full-stack system involves creating consistent REST, GraphQL, tRPC, or WebSocket interfaces. It ensures clear boundaries and integration points between your frontend and backend components while addressing cross-cutting concerns.

Does this approach support security architecture at every layer?

Security architecture is applied at every layer of the system design, covering frontend, backend, APIs, and infrastructure. This satisfies the need for holistic component integration and production-oriented architectural structuring.

When do I need to generate architecture documentation and validation checklists?

Architecture documentation and validation checklists are needed when translating requirements into a production-oriented system structure. They help assess complexity, validate architectural decisions, and produce a concrete implementation plan for your feature.

What are the limitations of using a planning workflow for system architecture design?

System architecture planning workflows focus on structuring decisions and generating documentation, but do not execute code or deploy infrastructure. They produce architectural plans, technology evaluations, and checklists that require manual implementation downstream.