Agent skill

Ad Architecture

by CorridorTech in CorridorTech/PoseCap

Generate ARCHITECTURE.md at the repo root by scanning the code first, pre-filling layers/patterns/observability/deployment from observed signals, then asking only the genuine gaps.

Apache-2.0Auto-check: notesDevOps & Cloud

Install Ad Architecture

skills CLI
$ npx skills add CorridorTech/PoseCap --skill ad-architecture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install CorridorTech/PoseCap ad-architecture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/CorridorTech/PoseCap.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ad-architecture .claude/skills/ad-architecture && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ad-architecture
GitHub stars
224
Token cost
~1.5k tokens
SKILL.md length
576 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Generate ARCHITECTURE.md at the repo root by scanning the code first, pre-filling layers/patterns/observability/deployment from observed signals, then asking only the genuine gaps.

  • Works in 5 steps: Detect mode → Scan the code → Pre-fill → …
  • The user wants to bootstrap
  • SKILL.md covers Step 0 — Detect mode, Step 1 — Scan the code, Step 2 — Pre-fill and Step 3 — Show only the gaps, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ad Architecture is an agent skill from CorridorTech/PoseCap. Generate ARCHITECTURE.md at the repo root by scanning the code first, pre-filling layers/patterns/observability/deployment from observed signals, then asking only the genuine gaps. Use when the user wants to bootstrap, scaffold, generate, document, or audit ARCHITECTURE.md (system-level patterns and boundaries, paired with ADRs in doc/adr/). Covers brownfield (code exists) and audit (drift report against existing ARCHITECTURE.md).

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Architecture decision records. The licence is Apache-2.0.

When your agent uses it

  • The user wants to bootstrap
  • Audit ARCHITECTURE.md (system-level patterns and boundaries
  • Paired with ADRs in doc/adr/)

Example prompts

  • “/ad-architecture”

Requirements

  • Docker
  • Pre-approved tools (allowed-tools): Read, Write, Glob, Grep, Bash

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Detect mode
  2. Scan the code
  3. Pre-fill
  4. Show only the gaps
  5. Write the file

What it can do on your machine

Read from SKILL.md and the folder at commit 626701b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Glob
    • Grep
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ad Architecture loads about 1.5k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 576 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~113
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Glob, Grep, Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from CorridorTech/PoseCap at commit 626701b, republished under its Apache-2.0 licence (© CorridorTech). 576 words, ~1,463 tokens.

Download SKILL.mdSave it as .claude/skills/ad-architecture/SKILL.md (or your agent's skills folder).
name
ad-architecture
description
Generate ARCHITECTURE.md at the repo root by scanning the code first, pre-filling layers/patterns/observability/deployment from observed signals, then asking only the genuine gaps. Use when the user wants to bootstrap, scaffold, generate, document, or audit ARCHITECTURE.md (system-level patterns and boundaries, paired with ADRs in doc/adr/). Covers brownfield (code exists) and audit (drift report against existing ARCHITECTURE.md).
allowed-tools
Read, Write, Glob, Grep, Bash
summary
Generate or audit `ARCHITECTURE.md` at the repo root.

/ad-architecture

Produces ARCHITECTURE.md at the repo root. Pairs with ADRs in doc/adr/ — architecture is the binding pattern; ADRs are individual decisions with status. ADRs in doc/adr/ with Status: accepted are binding; read every one before writing.

Step 0 — Detect mode

Inspect the repo:

  • ARCHITECTURE.md exists at the repo root → audit mode. Do not rewrite it. Stop after producing a drift list (see Step 4).
  • ARCHITECTURE.md absent → bootstrap mode. Scan first, pre-fill, ask only the gaps.

Step 1 — Scan the code

Read in this order, taking the first that exists for each category:

  • Top-level directory listing — infer the layered/hexagonal/clean structure.
  • Main entry points — servers (main.go, app/server.ts, manage.py, cmd/), CLI binaries, background jobs.
  • Boundary code — handlers/, controllers/, repositories/, gateways/, middleware/.
  • Config and env loading.
  • Observability hooks — logger setup, metrics export, tracing init.
  • Deploy config — Dockerfile, docker-compose.yml, k8s/, terraform/, .github/workflows/, Procfile, serverless.yml.
  • doc/adr/ — doc/adr/ is the canonical ADR ledger. Read accepted ADRs to inform pattern descriptions; do not duplicate the index inside ARCHITECTURE.md.

Build a model of: layers and boundaries, data access pattern, HTTP middleware chain, async/messaging, error and validation patterns, naming conventions, logging/metrics/tracing, deployment topology.

Step 2 — Pre-fill

For every <placeholder> in the template below, fill from observed signals. No fabrication. If a section has no signal, write <TODO: not yet wired> in one line and move on.

Step 3 — Show only the gaps

Print to the user:

  • (a) placeholders without a code signal;
  • (b) places where the code shows two competing patterns (some handlers go through middleware, some don't; mixed data-access styles, etc.).

One question per gap.

When the host exposes Plan Mode, the agent may render the proposed ARCHITECTURE.md body inside the plan for user approval before write. Plan Mode is opt-in — skip for incremental edits where the user already saw the prior content.

Step 4 — Write the file

On user confirmation, write ARCHITECTURE.md at the repo root. Cut every line that does not lock a binding pattern. At the end of the response, list any decision that should become an ADR — flag, do not write the ADR yet (use the ad-adr skill for that).

Audit-mode override: do not write the file. Produce a drift list. Format each line as:

[file or section]: spec says X, code says Y. Suggested resolution: change spec / change code / discuss.

If something the user says contradicts what the code shows, surface the conflict. Don't silently trust the user; don't silently trust the code.

Show full SKILL.md (193 more words)Show less

Template — ARCHITECTURE.md

markdown
# Architecture

System-level patterns and boundaries. Pair with ADRs in `doc/adr/` for individual decisions.

## Overview

`<one paragraph: what the system does, key external dependencies, deployment shape>`

## Layers & Boundaries

`<the layered/hexagonal/clean structure: what lives in each layer, what crosses boundaries, what doesn't>`

## Patterns

* **Data access:** `<e.g., Repository pattern; raw SQL only inside `internal/db/`>`
* **HTTP handlers:** `<e.g., all go through middleware in `src/middleware/`>`
* **Async/messaging:** `<e.g., Kafka topics owned by their producer service>`
* **Error handling:** `<e.g., domain errors in `errors/`; HTTP mapping at handler edge>`
* **Validation:** `<e.g., Pydantic at boundary, never inside core>`

## Naming Conventions

`<module/file/class naming rules that aren't obvious from language defaults>`

## Observability

* Logs: `<format, level conventions, where they ship>`
* Metrics: `<library, dashboards>`
* Traces: `<provider, sampling strategy>`

## Deployment Topology

`<how services run in prod: containers, orchestration, scaling rules>`

Output contract

A single ARCHITECTURE.md at the repo root. Every line locks a binding pattern. ADR candidates flagged in the response, not written. In audit mode: drift list only, no file written.

ARCHITECTURE.md is a narrative document, so the Documentation Discipline rules in WORKFLOW.md §2 apply at write time:

  • No emoji anywhere in the file.
  • No dates, version stamps, DRAFT markers, or changelog blocks. Architecture is the current binding pattern; the lifecycle of "when did this become true" lives in ADRs and git history.
  • Overview is the business-context-first paragraph — what the system does and what would break without it before layers and patterns.
  • One scope: system-level patterns and boundaries. Per-decision rationale lives in ADRs; per-project operations live in AGENTS.md. Link, do not copy.
  • No speculation. If a layer has no observed signal, write <TODO: not yet wired> once; do not propose patterns that aren't already in the code.

Next

  • /ad-spec when starting a feature whose scope spans the patterns this document records.
  • /ad-adr for any binding decision that surfaced while writing or auditing this file (one decision per ADR).
  • /ad-drift periodically to check pattern drift between this document and the code.

© CorridorTech, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/ad-architecture of CorridorTech/PoseCap.

Open the folder on GitHubat commit 626701b

Compare with similar skills

Ad Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ad Architecture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ad Architecture this skillCorridorTech/PoseCap224—~1.5kAutomated safety check: NotesApache-2.0
Obsidian WriterAtmosphere/atmosphere3.8k—~2.6kAutomated safety check: PassApache-2.0
Go Spec Reviewerinference-gateway/inference-gateway214—~1.2kAutomated safety check: PassApache-2.0
Review A Designinkeep/open-knowledge4.4k—~3.7kAutomated safety check: PassGPL-3.0
Architecturenteract/nteract179—~497Automated safety check: PassBSD-3-Clause
Ad Architecturealexandremendoncaalvaro/CorridorKey-Runtime7551 repos~1.3kAutomated safety check: PassCustom licence

Similar skills

  • Obsidian Writer

    Atmosphere/atmosphere

    Write well-formatted notes to the atmosphere-vault Obsidian knowledge base.

    3.8k GitHub stars~2.6k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Go Spec Reviewer

    inference-gateway/inference-gateway

    Review a Go design spec before implementation begins - dispatch a subagent that checks a design doc for completeness, consistency, and idiomatic Go (simplicity, small consumer-defined interfaces…

    214 GitHub stars~1.2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Review A Design

    inkeep/open-knowledge

    Reviews whether a design is SOUND — solving the right problem, derived from its stated goals and constraints — and emits ranked, evidence-backed findings, not edits.

    4.4k GitHub stars~3.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Architecture

    nteract/nteract

    Architecture and documentation framing for cross-cutting repo decisions, docs taxonomy placement, ADRs, memos, PRDs, implementation plans, audits, measurements, runbooks, and source-grounded…

    179 GitHub stars~497 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Ad Architecture

    alexandremendoncaalvaro/CorridorKey-Runtime

    Generate ARCHITECTURE.md at the repo root by scanning the code first, pre-filling layers/patterns/observability/deployment from observed signals, then asking only the genuine gaps.

    755 GitHub starsUsed in 1 repo~1.3k tokens
    DevOps & CloudAuto-check passed
  • Create Doc

    avibebuilder/claude-prime

    A skill your agent uses when the user wants to save knowledge as a file so others don't have to rediscover it — "turn this into a doc", "write this up", "document how X works", "we figured this out…

    120 GitHub stars~812 tokensUpdated 4 mo ago
    DevOps & CloudAuto-check passed

More from CorridorTech/PoseCap

All 15 skills in this repo
  • Ad Adr

    CorridorTech/PoseCap

    Draft a new ADR (Architecture Decision Record) at doc/adr/NNNN-<short-title.md, using Michael Nygard's Context/Decision/Consequences/Alternatives pattern.

    224 GitHub stars~1k tokensUpdated yesterday
    Auto-check: notes
  • Ad Archive

    CorridorTech/PoseCap

    Hard-delete completed plan files (tasks Status:done, specs Status:shipped, PRDs Status:superseded, ADRs Status:superseded or deprecated) via git rm, leaving git history as the only ledger.

    224 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check: notes
  • Ad Drift

    CorridorTech/PoseCap

    Read-only drift audit — compare AGENTS.md, ARCHITECTURE.md, ADR statuses, feature specs in doc/specs/, and documentation discipline against what the code actually does.

    224 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check: notes
  • Ad Hooks

    CorridorTech/PoseCap

    Scaffold deterministic quality gates per WORKFLOW.md §11 — pre-commit (lint, format, secret-scan), pre-push (build, unit, integration).

    224 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check: notes
  • Ad Next

    CorridorTech/PoseCap

    Survey the project's state across the six-layer artifact stack and recommend prioritized next actions, modeled on flutter doctor.

    224 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check: notes
  • Ad Bootstrap

    CorridorTech/PoseCap

    Generate AGENTS.md at the repo root by scanning the codebase first, pre-filling placeholders from observed signals, and asking only the genuine gaps.

    224 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check: warnings

Questions about Ad Architecture

What does Ad Architecture do?

Generate ARCHITECTURE.md at the repo root by scanning the code first, pre-filling layers/patterns/observability/deployment from observed signals, then asking only the genuine gaps. Ad Architecture is an agent skill from CorridorTech/PoseCap.md at the repo root by scanning the code first, pre-filling layers/patterns/observability/deployment from observed signals, then asking only the genuine gaps.

When should I use Ad Architecture?

Ad Architecture fits situations like: the user wants to bootstrap; audit ARCHITECTURE.md (system-level patterns and boundaries; paired with ADRs in doc/adr/).

How do I install Ad Architecture in Claude Code?

Run `npx skills add CorridorTech/PoseCap --skill ad-architecture -a claude-code`. Or copy the skill folder (.claude/skills/ad-architecture in CorridorTech/PoseCap) into .claude/skills/ad-architecture in your project. Claude Code loads it when a task matches its description.

How do I install Ad Architecture in Codex?

Run `npx skills add CorridorTech/PoseCap --skill ad-architecture -a codex`. Or copy the skill folder (.claude/skills/ad-architecture in CorridorTech/PoseCap) into .agents/skills/ad-architecture in your project. Codex loads it when a task matches its description.

Can I use Ad Architecture in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CorridorTech/PoseCap --skill ad-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ad-architecture, .gemini/skills/ad-architecture, .github/skills/ad-architecture and .opencode/skills/ad-architecture in your project.

What does Ad Architecture need to run?

SKILL.md names no scripts, command-line tools or credentials: Ad Architecture is instructions for the agent only. Our summary lists: Docker. Its frontmatter pre-approves these tools: Read, Write, Glob, Grep, Bash.

Does Ad Architecture access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ad Architecture safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Ad Architecture use?

Ad Architecture is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ad Architecture use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ad Architecture?

Skills that share tags, products or a category with Ad Architecture: Obsidian Writer (Atmosphere/atmosphere, 3.8k stars), Go Spec Reviewer (inference-gateway/inference-gateway, 214 stars), Review A Design (inkeep/open-knowledge, 4.4k stars) and Architecture (nteract/nteract, 179 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ad Architecture?

CorridorTech (a GitHub organization) maintains it in CorridorTech/PoseCap, which has 224 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.

Source: CorridorTech/PoseCap on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.