Obsidian Writer
Atmosphere/atmosphere
Write well-formatted notes to the atmosphere-vault Obsidian knowledge base.
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.
$ npx skills add CorridorTech/PoseCap --skill ad-architecture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install CorridorTech/PoseCap ad-architecture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "ad-architecture" agent skill from https://github.com/CorridorTech/PoseCap/tree/main/.claude/skills/ad-architecture into .claude/skills/ad-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ad-architecture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/CorridorTech/PoseCap/tree/main/.claude/skills/ad-architectureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add CorridorTech/PoseCap --skill ad-architecture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install CorridorTech/PoseCap ad-architecture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CorridorTech/PoseCap.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/ad-architecture .agents/skills/ad-architecture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ad-architecture" agent skill from https://github.com/CorridorTech/PoseCap/tree/main/.claude/skills/ad-architecture into .agents/skills/ad-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ad-architecture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CorridorTech/PoseCap --skill ad-architecture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install CorridorTech/PoseCap ad-architecture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CorridorTech/PoseCap.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/ad-architecture .cursor/skills/ad-architecture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ad-architecture" agent skill from https://github.com/CorridorTech/PoseCap/tree/main/.claude/skills/ad-architecture into .cursor/skills/ad-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ad-architecture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/CorridorTech/PoseCap.git --path .claude/skills/ad-architecture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add CorridorTech/PoseCap --skill ad-architecture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install CorridorTech/PoseCap ad-architecture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CorridorTech/PoseCap.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/ad-architecture .gemini/skills/ad-architecture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ad-architecture" agent skill from https://github.com/CorridorTech/PoseCap/tree/main/.claude/skills/ad-architecture into .gemini/skills/ad-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ad-architecture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install CorridorTech/PoseCap ad-architectureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add CorridorTech/PoseCap --skill ad-architecture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/CorridorTech/PoseCap.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/ad-architecture .github/skills/ad-architecture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ad-architecture" agent skill from https://github.com/CorridorTech/PoseCap/tree/main/.claude/skills/ad-architecture into .github/skills/ad-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ad-architecture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CorridorTech/PoseCap --skill ad-architecture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install CorridorTech/PoseCap ad-architecture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CorridorTech/PoseCap.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/ad-architecture .opencode/skills/ad-architecture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ad-architecture" agent skill from https://github.com/CorridorTech/PoseCap/tree/main/.claude/skills/ad-architecture into .opencode/skills/ad-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ad-architecture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
ad-architectureGenerate 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. 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.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 626701b. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteGlobGrepBashFrom allowed-tools in the SKILL.md frontmatter.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Write, Glob, Grep, BashAutomated 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.
The full file from CorridorTech/PoseCap at commit 626701b, republished under its Apache-2.0 licence (© CorridorTech). 576 words, ~1,463 tokens.
.claude/skills/ad-architecture/SKILL.md (or your agent's skills folder).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.
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.Read in this order, taking the first that exists for each category:
main.go, app/server.ts, manage.py, cmd/), CLI binaries, background jobs.handlers/, controllers/, repositories/, gateways/, middleware/.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.
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.
Print to the user:
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.
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.
ARCHITECTURE.md# 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>`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:
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.AGENTS.md. Link, do not copy.<TODO: not yet wired> once; do not propose patterns that aren't already in the code./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
Just SKILL.md in .claude/skills/ad-architecture of CorridorTech/PoseCap.
Open the folder on GitHubat commit 626701b
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ad Architecture this skillCorridorTech/PoseCap | 224 | — | ~1.5k | Automated safety check: Notes | Apache-2.0 | |
| Obsidian WriterAtmosphere/atmosphere | 3.8k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Go Spec Reviewerinference-gateway/inference-gateway | 214 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Review A Designinkeep/open-knowledge | 4.4k | — | ~3.7k | Automated safety check: Pass | GPL-3.0 | |
| Architecturenteract/nteract | 179 | — | ~497 | Automated safety check: Pass | BSD-3-Clause | |
| Ad Architecturealexandremendoncaalvaro/CorridorKey-Runtime | 755 | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence |
Atmosphere/atmosphere
Write well-formatted notes to the atmosphere-vault Obsidian knowledge base.
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…
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.
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…
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.
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…
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.
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.
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.
CorridorTech/PoseCap
Scaffold deterministic quality gates per WORKFLOW.md §11 — pre-commit (lint, format, secret-scan), pre-push (build, unit, integration).
CorridorTech/PoseCap
Survey the project's state across the six-layer artifact stack and recommend prioritized next actions, modeled on flutter doctor.
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.
Categories
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.
Ad Architecture fits situations like: the user wants to bootstrap; audit ARCHITECTURE.md (system-level patterns and boundaries; paired with ADRs in doc/adr/).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.