archspec

KO | EN

gitlite — search

#hacktoberfest #react #ai #typescript #deep-learning #docker #nodejs #awesome #cli #kubernetes #security #ios #openai #open-source

(★ 148)

Architecture checks for Ruby and Rails.

파일 탐색기

최종 버전 다운로드 (.zip)

- - ci.yml
  - release.yml
- - clean.md
  - cqrs.md
  - event-driven.md
  - hexagonal.md
  - index.md
  - layered.md
  - modular-monolith.md
  - rails.md
  - ruby_conventions.md
  - vanilla-rails.md
- - navigation.yml
  - sidebar.yml
  - social_links.yml
  - versions.yml
- - checking-ai-written-code.md
  - getting-started.md
  - how-it-works.md
  - rails.md
  - vanilla-rails.md
- - home.html
- - cli.md
  - configuration.md
- - components.md
  - concerns.md
  - constants.md
  - cycles.md
  - dependencies.md
  - index.md
  - methods.md
  - naming.md
  - objects.md
  - protocols.md
- - audit-seo.rb
  - build-api.sh
  - postprocess_api_seo.rb
- _config.yml
- CNAME
- Gemfile
- index.md
- archspec
- - analyzer.rb
  - architectures.rb
  - cli.rb
  - component_spec.rb
  - definition.rb
  - diagnostic.rb
  - dsl.rb
  - error.rb
  - evaluator.rb
  - model.rb
  - source_location.rb
  - todo.rb
  - value_object.rb
  - version.rb
- archspec.rb
- - run.rb
- analyzer_test.rb
- architectures_test.rb
- cli_test.rb
- fixture_app_test.rb
- naming_rules_test.rb
- rules_test.rb
- test_helper.rb
- text_formatter_test.rb
- todo_test.rb
- torture_test.rb
- value_object_test.rb
.gitignore
.rdoc_options
archspec.gemspec
Archspec.rb
Gemfile
LICENSE.txt
Rakefile
README.md

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# ArchSpec

<strong>Executable architecture specifications for Ruby and Rails</strong>

<p>Declare your components and boundaries in one <code>Archspec.rb</code>, and every change gets checked in CI, whether a person or a coding agent wrote it. No AI involved, just Prism.</p>

Battle tested in [<picture><source media="(prefers-color-scheme: dark)" srcset="https://rubyllm.com/assets/images/logotype_dark.svg"><img src="https://rubyllm.com/assets/images/logotype.svg" alt="RubyLLM" height="30" align="absmiddle"></picture>](https://rubyllm.com) and at [<picture><source media="(prefers-color-scheme: dark)" srcset="https://chatwithwork.com/logotype-dark.svg"><img src="https://chatwithwork.com/logotype.svg" alt="Chat with Work" height="30" align="absmiddle"></picture>](https://chatwithwork.com)

[![Gem Version](https://badge.fury.io/rb/archspec.svg)](https://rubygems.org/gems/archspec)
[![Gem Downloads](https://img.shields.io/gem/dt/archspec)](https://rubygems.org/gems/archspec)
[![CI](https://github.com/crmne/archspec/actions/workflows/ci.yml/badge.svg)](https://github.com/crmne/archspec/actions/workflows/ci.yml)

</div>

---

ArchSpec turns your architecture into executable checks: components, layers, constant references, inheritance, mixins, named method calls, method protocols, naming conventions, cycles, and Rails boundaries. It is plain static analysis: it reads Ruby source with Prism, never boots the app, and no AI is involved in checking your code. The full Discourse app, 1,899 files, checks in 2.5 seconds.

## Why ArchSpec?

Architecture usually lives in pull request comments, onboarding docs, and senior
engineers' heads. That does not scale well, especially when code is moving fast.
More of that code is now written by coding agents that do not know your
conventions.

ArchSpec gives you a small Ruby DSL for the rules that code review otherwise has
to remember, and checks them on every change:

- models do not reach into controllers
- domain code does not depend on adapters
- packs only depend on approved packs
- query objects do not call obvious write methods
- generated code follows the same boundaries as hand-written code

ArchSpec does not try to infer the "true" design pattern of arbitrary Ruby code.
You describe the architecture your team wants. ArchSpec checks whether the code
still matches it.

## Show me the code

Start with conventional Rails boundaries:

```ruby
architecture :rails
```

Go vanilla, 37signals style, with rich models and no service objects:

```ruby
architecture :vanilla_rails
```

Add layers when the app has a clear direction of dependencies:

```ruby
architecture :layered
```

Override the default directories when the app uses different names:

```ruby
architecture :layered, layers: {
  interface: "app/controllers/**/*.rb",
  application: "app/services/**/*.rb",
  domain: "app/models/**/*.rb"
}
```

Keep a hexagonal core away from adapters:

```ruby
architecture :hexagonal
```

Check a modular monolith, and make packs go through a public API:

```ruby
architecture :modular_monolith,
  components: {
    billing: "packs/billing/**/*.rb",
    catalog: "packs/catalog/**/*.rb",
    shared: "packs/shared/**/*.rb"
  },
  allow: {
    billing: %i[shared],
    catalog: %i[shared]
  },
  public: {
    billing: "packs/billing/app/public/**/*.rb"
  }
```

Write local rules in plain Ruby:

```ruby
component :controllers, in: "app/controllers/**/*.rb"
component :models, in: "app/models/**/*.rb"
component :services, in: "app/services/**/*.rb"

controllers.can_only_use :models, :services
models.cannot_use :controllers
services.cannot_call :render, :redirect_to, :params, :session
services.cannot_instantiate_and_invoke
```

Check command/query separation:

```ruby
architecture :cqrs,
  commands: "app/commands/**/*.rb",
  queries: "app/queries/**/*.rb",
  read_models: "app/read_models/**/*.rb"
```

## What It Checks

- **Dependencies:** allowed and forbidden references between components, in both directions
- **Privacy:** other components must go through a component's public API
- **Concerns:** a concern must not depend on the classes that include it
- **Layers:** dependency direction and cycles
- **Rails:** controller APIs kept out of models and services
- **Architectures:** Rails, vanilla Rails, layered, hexagonal, clean, modular monolith, CQRS, event-driven, and Ruby conventions bundles
- **Protocols:** required methods such as `resolve`, `perform`, or project-specific interfaces
- **Naming:** conventions on a component's public API, such as banning `get_`/`set_` or pairing `with_x` with `without_x`
- **Objects:** rules against one-shot `Something.new(...).whatever` command objects
- **Empty components:** directories that must stay empty, like `app/services` in vanilla Rails
- **Suppressions:** narrow local exceptions with a reason

## Checking Zeitwerk Names

ArchSpec does not check Zeitwerk constant names. Zeitwerk does that itself. Add `Zeitwerk::Loader.eager_load_all` (or your loader's `eager_load`) to your test suite or CI. It raises on any file that does not define the constant its path implies, using your real inflector and ignores.

## Installation

Add ArchSpec to your Gemfile:

```ruby
group :development, :test do
  gem "archspec"
end
```

Then install it:

```sh
bundle install
```

Create `Archspec.rb`:

```sh
bundle exec archspec init
```

Run the checks:

```sh
bundle exec archspec check
```

## Commands

```sh
bundle exec archspec init
bundle exec archspec check
bundle exec archspec check --format json
bundle exec archspec check --update-todo
bundle exec archspec explain app/models/user.rb
```

`explain` shows why a file or constant belongs to a component and which outgoing
facts ArchSpec found:

```text
app/models/user.rb

defined constants: User
  components:
    models: matched file pattern app/models/**/*.rb
  outgoing facts:
    1:14 │ inherits from ApplicationRecord
     2:3 │ references UsersController
```

## Checking AI-Written Code

Generated code should pass the same architecture checks as hand-written code.

After an AI-assisted change, check the whole project, or just the files that changed:

```sh
bundle exec archspec check
bundle exec archspec check app/models/user.rb app/services
```

Passing paths still analyzes the project so dependencies resolve, but reports only violations in those paths. This keeps the loop tight after each edit.

If it fails, read the evidence before changing the spec:

```text
[error] models must not depend on controllers [dependencies.forbid]

app/models/user.rb:2:3

1 │ class User < ApplicationRecord
  → 2 │   UsersController
      │   ^~~~~~~~~~~~~~~
    3 │ end

note: User references UsersController
```

Most failures should be fixed in the generated code. Update the spec only when
the architecture decision itself has changed.

## Todo and Suppressions

Use a todo file when adopting ArchSpec in an existing app. It records the current
violations so they stop failing the build, leaving a list to burn down:

```ruby
todo "archspec_todo.yml"
```

```sh
bundle exec archspec check --update-todo
```

Use local suppressions for deliberate exceptions:

```ruby
# archspec:disable-next-line dependencies.forbid -- legacy admin export
Admin::UsersController
```

## Documentation

Read the guides at [archspecrb.dev](https://archspecrb.dev/).

## Dogfooding

This repository checks its own architecture:

```sh
bundle exec rake architecture
```

It also runs against pinned checkouts of large real-world Rails apps to catch crashes and false positives before they ship:

```sh
bundle exec rake torture
```

## License

Released under the MIT License.

archspec

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

archspec

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README