Agent skill

Architecture Ownership

by instructa in instructa/agent-skills

Determine runtime owner, first-fix layer, and canonical long-term module or package owner in layered codebases.

No licenceAuto-check passedDevelopment

Install Architecture Ownership

skills CLI
$ npx skills add instructa/agent-skills --skill architecture-ownership -a claude-code

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

GitHub CLI
$ gh skill install instructa/agent-skills architecture-ownership --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/instructa/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/engineering/architecture-ownership .claude/skills/architecture-ownership && 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
architecture-ownership
GitHub stars
139
Token cost
~1.3k tokens
SKILL.md length
647 words
Files
4 (incl. references)
Skills in repo
17
Repo updated
First seen
Licence
None found

At a glance

Determine runtime owner, first-fix layer, and canonical long-term module or package owner in layered codebases.

  • Works in 5 steps: Identify the runtime concern → Name the layer where the wrong behavior… → Decide whether that layer is only the… → …
  • Placing code across UI vs platform shell vs runtime orchestration vs domain
  • SKILL.md covers Required Discovery, Required Output, Decision Order and Layer Map, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Architecture Ownership is an agent skill from instructa/agent-skills. Determine runtime owner, first-fix layer, and canonical long-term module or package owner in layered codebases. Use when placing code across UI vs platform shell vs runtime orchestration vs domain or application vs shared core vs adapter or integration layers, debugging ownership issues, removing duplicate policy paths, or answering "where should this live?" architecture questions.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `README.md`, `agents/openai.yaml` and `references/ownership-matrix.md`).

It sits in Development. The repository describes itself as: A curated collection of agent-skills.

When your agent uses it

  • Placing code across UI vs platform shell vs runtime orchestration vs domain
  • Application vs shared core vs adapter
  • Integration layers
  • Debugging ownership issues

Example prompts

  • “where should this live?”
  • “/architecture-ownership”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Identify the runtime concern
  2. Name the layer where the wrong behavior currently happens.
  3. Decide whether that layer is only the First fix owner or also the Canonical long-term owner.
  4. If the behavior is reusable product or business policy, move the long-term owner out of the runtime orchestration layer.
  5. Remove duplicate policy, fallback logic, or dual paths once the canonical owner is clear.

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    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

Architecture Ownership loads about 1.3k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 647 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.2k

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 passed

The automated check found no risky patterns in SKILL.md.

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

Without a licence we can't republish the file, so here is its outline and opening line. It has 647 words (~1,287 tokens).

“Use this skill for repo-specific ownership and placement decisions in layered systems.”

— opening of SKILL.md by instructa
name
architecture-ownership

Read the full SKILL.md on GitHub

Files

SKILL.md and 3 other files (references) in skills/engineering/architecture-ownership of instructa/agent-skills.

  • SKILL.md
  • README.md
  • agents/openai.yaml
  • references/ownership-matrix.md

Open the folder on GitHubat commit d49c149

Compare with similar skills

Architecture Ownership 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.

Architecture Ownership compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Architecture Ownership this skillinstructa/agent-skills139—~1.3kAutomated safety check: PassNone
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from instructa/agent-skills

All 17 skills in this repo
  • App Spec Packager

    instructa/agent-skills

    A skill your agent uses when the user wants to turn an application, product, startup idea, SaaS, mobile app, web app, API, AI product, or internal tool into a production-ready Markdown specification…

    139 GitHub stars~1.5k tokensUpdated 11 days ago
    Auto-check passed
  • Codex Reviewer

    instructa/agent-skills

    Have Codex review a feature or change from Claude Code, then let Claude address the findings and request verification.

    139 GitHub stars~1.6k tokensUpdated 11 days ago
    Auto-check passed
  • Search Context

    instructa/agent-skills

    Find, clone, inspect, and summarize high-quality GitHub reference repositories for coding agents.

    139 GitHub stars~2.1k tokensUpdated 11 days ago
    Auto-check passed
  • Secleak Check

    instructa/agent-skills

    Run or install repo security leak checks with BetterLeaks and Trivy.

    139 GitHub stars~557 tokensUpdated 11 days ago
    Auto-check passed
  • Delegate Fable

    instructa/agent-skills

    Delegate a bounded task from a Codex session to a Fable-powered Cursor Agent in the same Herdr workspace, then wait for and collect the result.

    139 GitHub stars~925 tokensUpdated 11 days ago
    Auto-check passed
  • Delegate Grok

    instructa/agent-skills

    Delegate a bounded task from a Codex session to Grok 4.6 with xhigh reasoning in the same Herdr workspace, then wait for and collect the result.

    139 GitHub stars~951 tokensUpdated 11 days ago
    Auto-check passed

Categories

Questions about Architecture Ownership

What does Architecture Ownership do?

Determine runtime owner, first-fix layer, and canonical long-term module or package owner in layered codebases. Architecture Ownership is an agent skill from instructa/agent-skills. Determine runtime owner, first-fix layer, and canonical long-term module or package owner in layered codebases.

When should I use Architecture Ownership?

Architecture Ownership fits situations like: placing code across UI vs platform shell vs runtime orchestration vs domain; application vs shared core vs adapter; integration layers; debugging ownership issues.

How do I install Architecture Ownership in Claude Code?

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

How do I install Architecture Ownership in Codex?

Run `npx skills add instructa/agent-skills --skill architecture-ownership -a codex`. Or copy the skill folder (skills/engineering/architecture-ownership in instructa/agent-skills) into .agents/skills/architecture-ownership in your project. Codex loads it when a task matches its description.

Can I use Architecture Ownership 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 instructa/agent-skills --skill architecture-ownership -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture-ownership, .gemini/skills/architecture-ownership, .github/skills/architecture-ownership and .opencode/skills/architecture-ownership in your project.

What does Architecture Ownership need to run?

SKILL.md names no scripts, command-line tools or credentials: Architecture Ownership is instructions for the agent only.

Does Architecture Ownership 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 Architecture Ownership safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Architecture Ownership use?

No licence was found for Architecture Ownership or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Architecture Ownership use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 903 tokens, read only when the agent opens those files.

What are the alternatives to Architecture Ownership?

Skills that share tags, products or a category with Architecture Ownership: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Architecture Ownership?

instructa (a GitHub organization) maintains it in instructa/agent-skills, which has 139 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on September 28, 2026.

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