Virtual Architects
GitHub (opens in a new tab)Get the kit
← Home

Commands

Start from what you have in hand

Nine slash commands, the same in Claude Code and Copilot Chat. Start with /arch-profile so the team knows your project, then bring whatever you have in hand. None of them commits or pushes.

Pick a command

What do you have in hand?

Try it

/arch-profile
You get
Your project profile, filled from the code and a few questions
Who answers
You, with the team
Where it lands
docs/architecture/project.yaml
Then
Every architect now knows your stack, your rules and who decides. Run it again when they change.

Not sure which? /arch-board picks the architects and tells you why.

Reference

Every command, side by side

  1. /arch-profile [what changed]

    A repository the architects have not seen yet

    You get
    Your project profile, filled from the code and a few questions
    Who answers
    You, with the team
    Where it lands
    docs/architecture/project.yaml
    Then
    Every architect now knows your stack, your rules and who decides. Run it again when they change.
    /arch-profile
  2. /arch-research <source or question>

    A link, a PDF, a vendor page, a regulation

    You get
    A brief, and the questions each architect has to answer
    Who answers
    Research
    Where it lands
    docs/architecture/practice/research/<date>-<topic>.md
    Then
    Every new question has one owner. Take the first one to that architect, or to the board.
    /arch-research is PostHog available in the Saudi region?
  3. /arch-enterprise <idea>

    A purchase, an RFP, a new vendor, build or buy

    You get
    A demand assessment: options, a recommendation, and an outline or an ADR
    Who answers
    Enterprise
    Where it lands
    docs/architecture/outlines/solutions/ or decisions/
    Then
    You decide: go, no, or not now. A go moves on to /arch-doc.
    /arch-enterprise we received an RFP for a new CRM: buy one, build one, or extend what we have?
  4. /arch-doc <feature | integration | system> <what>

    A feature, an integration or a system to design

    You get
    An HLD to decide on, and the LLD, written as a software architecture document
    Who answers
    Solution
    Where it lands
    docs/architecture/designs/solutions/<project>/hld.md and lld.md
    Then
    Security and cloud review the HLD. Then you take the design decision.
    /arch-doc feature customers can pause their subscription for up to three months
  5. /arch-solution <question>

    A design question, a plan or a branch to review

    You get
    A design answer, or findings that point to the exact line
    Who answers
    Solution
    Where it lands
    Usually nothing. An ADR if the answer will matter for years
    Then
    Fix the findings, or record an exemption as an ADR.
    /arch-solution should we integrate with the notification service sync or async?
  6. /arch-conform <branch | folder | file> [fix]

    Code to check against your standards, before a pull request

    You get
    Every breach of a guideline, with the exact line and the rule it breaks, fixed if you ask
    Who answers
    Solution
    Where it lands
    Your fixes, and each guideline's list of where the code still breaks it
    Then
    Merge the fixes. A rule it keeps finding broken becomes a lint rule or a test.
    /arch-conform fix
  7. /arch-cloud-infra <question>

    A deploy, network, database or cost question

    You get
    A change plan with the steps, the cost and the rollback
    Who answers
    Cloud and infra
    Where it lands
    docs/architecture/designs/solutions/<project>/change-plan.md
    Then
    You run the commands. The architect never touches live resources.
    /arch-cloud-infra our API slows down every Monday morning: how should we scale it, and at what cost?
  8. /arch-security <question>

    Is this safe? Auth, personal data, a new third party

    You get
    A threat model, or ranked findings
    Who answers
    Security
    Where it lands
    docs/architecture/designs/solutions/<project>/threat-model.md
    Then
    Controls go to their owners. A live weakness goes to you, never into the repository.
    /arch-security investigate our backend services and plan their security testing
  9. /arch-board <question>

    Something that crosses lanes

    You get
    One recommendation, the disagreements, and the decision it needs
    Who answers
    The board: research first, then the architects it touches
    Where it lands
    Open questions in practice/research/questions.yaml
    Then
    You take the decision it names: strategy, investment, technology or design.
    /arch-board should all customer data stay in a cloud region inside our country?

One more, for maintainers: /arch-sync regenerates the Copilot copies after you edit an architect, and /arch-sync hook makes every commit do it.