archspecrb.dev valid

ArchSpec

Documentation for ArchSpec, the static-analysis architecture linter for Ruby and Rails applications.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:48:24.785Z. Cached copy · Source on archspecrb.dev

# ArchSpec

> Documentation for ArchSpec, the static-analysis architecture linter for Ruby and Rails applications.

Start with getting started and configuration, then use the rule, architecture, CLI, CI, and AI-written-code guides. Source is on [GitHub](https://github.com/crmne/archspec), and the generated [API reference](https://archspecrb.dev/api/) documents the Ruby API.

## Full Documentation

- [Complete documentation](https://archspecrb.dev/llms-full.txt): All canonical pages in one Markdown document.

## Overview

- [Architecture linter for Ruby and Rails](https://archspecrb.dev/): Static architecture linter for Ruby and Rails and a Packwerk alternative. Declare components and boundaries in one file, then check every change in CI.

## Guides

- [Getting Started](https://archspecrb.dev/getting-started/): Install ArchSpec, generate an Archspec.rb file, run your first architecture check, and learn how to interpret a reported violation.
- [Rails Applications](https://archspecrb.dev/rails/): Configure ArchSpec for a conventional Rails application and enforce practical boundaries between controllers, models, services, and helpers.
- [Checking AI-Written Code](https://archspecrb.dev/checking-ai-written-code/): Use ArchSpec as a deterministic architecture guardrail for AI-written Ruby and Rails code, with actionable evidence for every violation.
- [Vanilla Rails Guide](https://archspecrb.dev/vanilla-rails/): Turn 37signals-style vanilla Rails conventions into executable ArchSpec checks for models, controllers, concerns, and directory structure.
- [How It Works](https://archspecrb.dev/how-it-works/): Learn how ArchSpec analyzes Ruby and ERB files with Rubydex, Prism, and Herb, builds its model, evaluates rules, and reports architecture diagnostics.
- [Framework integrations](https://archspecrb.dev/framework-integrations/): Teach ArchSpec what a framework or macro library does at runtime with a small facts producer that archspec reflect runs and checks read as data.
- [Rails reflection](https://archspecrb.dev/association-reflection/): Capture what Rails resolved at runtime (association targets, custom validators, and conditional concern effects) as facts that static ArchSpec checks enforce.

## Rules

- [Architecture rules overview](https://archspecrb.dev/rules/): Browse every ArchSpec rule for dependencies, cycles, constants, method calls, protocols, object usage, concerns, naming, and component structure.
- [Dependencies](https://archspecrb.dev/rules/dependencies/): Use ArchSpec dependency rules to define component allowlists, deny specific dependencies, restrict consumers, and expose public APIs.
- [Method boundary rules](https://archspecrb.dev/rules/methods/): Use ArchSpec method rules to forbid calls to selected APIs or prevent components from defining methods that violate architecture boundaries.
- [Protocols](https://archspecrb.dev/rules/protocols/): Use ArchSpec protocol rules to require classes in a component to implement one method or at l
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=archspecrb.dev · GET /v1/domain/archspecrb.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for archspecrb.dev:
1. POST https://agentwebmap.com/v1/sites/archspecrb.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://archspecrb.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/archspecrb.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/archspecrb.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.