Use when designing a system, choosing an architecture pattern, making a technology decision, or doing capacity/scalability planning — BEFORE drilling into framework-specific mechanics. A lean MAP over three reference docs: pattern selection (monolith → modular monolith → microservices → event-driven → CQRS → event sourcing → hexagonal → clean → API gateway, with trade-offs), the how-to system-design workflows (system-design-interview approach, capacity planning, API design, DB schema design, scalability assessment, migration planning), and the technology-choice frameworks (database, caching, message queue, auth, frontend framework, cloud provider, API style). Trigger on: 'design the system', 'choose an architecture pattern', 'which pattern fits', 'tech decision', 'SQL or NoSQL', 'REST vs GraphQL vs gRPC', 'capacity/scalability planning', 'plan the migration'. This is general system-design knowledge; for Phoenix bounded-context/Ecto/authz/Oban specifics use the architecture-phx skill.
$npx -y skills add endorphin-ai/hasbrains-agent-kit --skill system-architectureInstalls into the current project.
Run `npx skills use "https://github.com/endorphin-ai/hasbrains-agent-kit" --skill "endorphin-ai/hasbrains-agent-kit/system-architecture"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/endorphin-ai/hasbrains-agent-kit" that are relevant to the current task. Run `npx skills add "https://github.com/endorphin-ai/hasbrains-agent-kit"` and select the relevant skills, then follow their instructions.