Docs / Item Types

Item Types

Everything you store is one of five built-in types — or a custom type you define. The type decides how an item is formatted, how it downloads, and how your AI uses it.

Quick map:

Type	In one line	How the AI uses it
📝 Prompt	a fill-in-the-blank message	type `/`, fill the blanks, send
🧠 Skill	how to do a task	just ask — it reads & follows it
📏 Rule	an always-on standing order	sits in your project, always applied
📄 Doc	reference material	read on demand, when you ask
⚙️ Config	a setup / settings file	download & drop where it's needed

📝 Prompts

A prompt is a message you'd send to an AI, saved once as a reusable template. Mark the parts you change each time with [brackets]:

Draft a cold outreach email from [sender] at [company] to [recipient] about [topic].

Those brackets become fill-in-the-blank fields. You reuse the prompt and fill the blanks, instead of rewriting it.

How you use a prompt:

In the app — open it, fill the fields, and copy the result, or Send to AI to open Claude/ChatGPT/Perplexity with it prefilled.
In your editor (over MCP) — it shows up as a /aistoragedepot:… slash command that takes your input as arguments and fills the fields, asking for anything you leave out.

🧠 Skills

A skill teaches your AI how to do a task — your code-review process, your way of writing release notes, a methodology. You don't fill it in; you point the AI at it.

How you use a skill:

Over MCP (recommended) — just ask in plain language: "do a code-review pass." The agent finds your skill and reads it. It works live, always your latest version, and you don't have to remember a command.
As a typed command — run pull to install it as a /aistoragedepot:… slash command you can type. This is the offline / "I'd rather type it" option.

A skill only ever appears in your slash menu if you pull it — over MCP it's something the agent reads, not a command you type.

📏 Rules

Rules are standing orders your AI should always follow — "always use British spelling," "follow our TypeScript style," "never do X." Unlike a prompt or skill, you don't invoke a rule; it applies to everything.

A rule sitting in your library does nothing on its own. There are two ways to make it take effect, and both are explicit:

Download it into your project or user file — e.g. AGENTS.md or .cursor/rules/*.mdc in a repo, or a global config. From then on your tool loads it every session and the agent follows it automatically. "Project" scope applies to that repo; "user" scope applies across all your projects.
Ask for it over MCP — "follow my team's TypeScript rules." The agent fetches and applies it for that request. Per-task, not always-on.

📄 Docs

Docs are reference material — API notes, a style guide, background — that you want the AI to be able to read when relevant. You don't send a doc like a prompt; the agent reads it on demand, when you point it there ("check my API notes, then answer") or when it searches your library and finds it relevant.

A doc has no "always-on" mode. It's used only when the AI goes looking for it — which happens because you asked.

⚙️ Configs

Configs are setup and settings files — like an mcp.json. They're plumbing, not content the AI reads. You download a config and drop it where a tool expects it.

Custom types

If the five built-ins don't fit, define your own type: give it a name, a format, and a file extension, and it behaves like the closest built-in. A custom type you create follows you into any team or company you administer.