arch-explain

Explains architecture questions by citing guideline sections and review lenses.

89|10|Updated Sep 15, 2026
One-click install
npx skills add https://github.com/baristaze/swe_guidelines --skill arch-explain-baristaze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arch-explain
Source: https://github.com/baristaze/swe_guidelines/tree/main/skills/arch-explain
Command: npx skills add https://github.com/baristaze/swe_guidelines --skill arch-explain-baristaze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When onboarding to a codebase or planning a cross-layer change, developers need to know which architecture rules apply to a question, file, or proposed change without reading the entire guideline. This Skill answers those questions using the project's architecture guideline and lens catalog as the source of truth, with precise citations. ## Core Features & Use Cases - Question Answering: Answers architecture questions (e.g., "where does rate limiting live?") by locating and quoting the governing guideline sections. - File Rule Mapping: Given a file or folder path, lists each applicable rule and whether the code follows it, in one line each. - Change Guidance: For a described change, identifies which layer each part belongs to, which section shapes it, and which scaffold skill starts it. - Use Case: A new team member asks "can a manager call a service?" and receives a short answer quoting the deciding sentence from the guideline, citing the section title and relevant lens IDs. ## Quick Start Ask the arch-explain skill where rate limiting should live in this project and which rules govern it.

Frequently Asked Questions about arch-explain

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

FAQPage Schema
How do I find which architecture rules apply to a file?▼

Pass the file or folder path as the argument, and the skill opens the code and states, for each applicable rule, whether the code follows it in one line each. It points to the arch-review group skills for a full review rather than running one itself.

How to explain an architecture guideline to new team members?▼

Invoke the skill with empty arguments to get a guided tour: every guideline section in table-of-contents order with two sentences each, plus the eight lens groups in one line each. This gives newcomers a structured overview grounded in the actual document.

Can I check rules before making a cross-layer change?▼

Yes, describe the change as the argument and the skill identifies which layer each part belongs to, which guideline section shapes it, and which scaffold skill starts the implementation. It is designed for use before cross-layer changes.

What happens when the guideline does not cover my question?▼

The skill explicitly says the guideline is silent on the question and names the nearest relevant section. It does not offer opinions beyond the text, keeping answers grounded in the written guideline.

What are the limitations of guideline-based architecture answers?▼

Answers are limited to what the guideline and lens catalog actually state, so topics outside the document receive no opinion. The skill also does not run full reviews; it defers those to the arch-review group skills.