Layers And Ownership logo

Layers And Ownership

OrganizationPopular
agent0ai
Layers And Ownership

Understand L0 or L1 or L2 placement, group and user structure, permissions, and layered override order before storing or overriding frontend assets.

Overview

Publisheragent0ai
Repositoryspace-agent
Skill nameLayers And Ownership
Stars
1.4K
Forks
323
Bundled files
Instructions only
LicenseMIT
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by agent0ai on GitHub. Read the source before you install it.

Installation

Install the Layers And Ownership AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/agent0ai/space-agent.git /tmp/space-agent
mkdir -p .claude/skills
cp -r /tmp/space-agent/app/L0/_all/mod/_core/skillset/ext/skills/development/layers-ownership .claude/skills/agent0ai-layers-and-ownership
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Layers And Ownership in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Layers And Ownership on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Layers And Ownership is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Use this skill before deciding where new files belong or how readable and writable content resolves across users and groups.

The Three Layers

  • L0 is firmware. Repo-owned first-party code belongs here.
  • L1 is group customware. It is writable only for group managers and admins.
  • L2 is user customware. It is writable only for that user and admins.

Group And User Structure

  • L1/_all is the shared group layer available to everyone.
  • L1/_admin is the admin group layer.
  • L2/<username>/user.yaml stores user metadata such as full_name.
  • L2/<username>/meta/ holds auth state such as password and login session records.
  • L2/<username>/mod/ is that user's customware module root.
  • L1/<group>/group.yaml is the canonical group membership and management file.
  • When CUSTOMWARE_GIT_HISTORY is enabled, each writable L1/<group>/ and L2/<username>/ root may have a server-managed local Git history repository.
  • L2 history ignores meta/password.json and meta/logins.json; rollback preserves those current auth files and keeps previous heads listable for forward travel when possible, while revert creates a new inverse commit.

Permission Model

  • Nobody writes L0.
  • Users may read their own L2/<username>/.
  • Users may read L0/<group>/ and L1/<group>/ for groups they belong to.
  • Users may write L1/<group>/ only when they manage that group directly or through a managing-group include chain.
  • _admin members may write any L1/ and L2/ path.

Group Config Fields

group.yaml uses these canonical fields:

  • included_users
  • included_groups
  • managing_users
  • managing_groups

Resolution Order

Readable module and extension resolution is rank-based:

  1. L0/_all
  2. readable L0/<group> entries in group order
  3. L1/_all
  4. readable L1/<group> entries in group order
  5. L2/<username>

Higher-ranked exact same module-relative paths override lower-ranked ones. Different filenames under the same extension point compose together.

Placement Rules For Repo Work

  • Put repo-owned first-party development work in app/L0/_all/mod/_core/....
  • Use L1 and L2 only when the user explicitly wants layered customware or user- or group-specific overrides.
  • Do not treat repo-local app/L1 or app/L2 as durable framework source; they are transient runtime state and are gitignored.
  • Do not read, write, or depend on .git paths inside writable layer roots; they are reserved for server-managed history.

Mandatory Doc Follow-Up

  • If layer order, ownership rules, group semantics, or permission rules change, update the mirrored docs and the development skill subtree in the same session.

Frequently asked questions

What does the Layers And Ownership AI skill do?

Understand L0 or L1 or L2 placement, group and user structure, permissions, and layered override order before storing or overriding frontend assets.

Why use Layers And Ownership on TypingMind?

Because you install it once and use it with any model. Layers And Ownership is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Layers And Ownership in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/agent0ai/space-agent/tree/main/app/L0/_all/mod/_core/skillset/ext/skills/development/layers-ownership. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Layers And Ownership?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Layers And Ownership?

As many as you like. As long as a model supports skills, you can use Layers And Ownership with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Layers And Ownership AI skill free?

Yes. It is published on GitHub by agent0ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
mattpocock logo

Ask Matt

mattpocock
CommunityPopular

Ask which skill or flow fits your situation. A router over the skills in this repo.

22.3K
264.4K
2 files
View
mattpocock logo

Code Review

mattpocock
CommunityPopular

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what…

22.3K
264.4K
1 files
View
mattpocock logo

Codebase Design

mattpocock
CommunityPopular

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or…

22.3K
264.4K
3 files
View
mattpocock logo

Diagnosing Bugs

mattpocock
CommunityPopular

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

22.3K
264.4K
2 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇