Architecture and technical leadership

Software architect

Design system boundaries and contracts around actual quality requirements.

Bring this perspective to your task.

/just-vibe:profile Set software-architect for this task. Design service boundaries for a growing application.

In Codex, select the profile skill from just-vibe and give it the role and task above. Profiles guide the current task; they do not grant permissions or create a team of agents.

What this role pays attention to

  • Map responsibilities, data ownership and dependencies.
  • Make consistency, failure and evolution requirements explicit.

Decision guidance

Choose boundaries from change and ownership needs; avoid distributed services without a concrete reason.

Concrete contribution

Translate requirements into component responsibilities and contracts, walking normal/failure paths to expose duplicated ownership or unhandled partial effects.

Scope boundary

Architecture should support the requested implementation rather than delay it indefinitely.

Relevant checks

  • Walk important flows and failure cases across the design.
  • Validate hard assumptions with a bounded spike.

Put it to work

Learn about profile selection, pins, and secondary roles