Docs / Getting Started

Getting Started

AIStorageDepot is a searchable, versioned home for everything you feed your AI — your prompts, skills, rules, docs, configs, and templates — that plugs straight into the tools you already use. This guide takes you from a brand-new account to using your first prompt inside your editor, in about five minutes. (New accounts don't start bare, either: you get two starters — a prompt already set up as a slash command and a skill your AI finds just by asking — plus the prebuilt AIStorageDepot Library one tab over, ready to copy from.)

By the end you'll have:

A free account with your first prompt saved.
Your library connected to your AI tool over MCP.
That prompt working as a live / command.

Before you start

You need two things:

A free AIStorageDepot account — no credit card. Sign up with email and password, or with Google or Microsoft.
An AI tool that speaks MCP — Claude Desktop, Cursor, VS Code, Claude Code, Cline, Windsurf, or Codex.

Step 1 — Save your first prompt

Sign in, click + New ▾, and choose New prompt.
Give it a title — say, Cold outreach email.
In the body, write the prompt and wrap the parts you'll change each time in [brackets]:

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

Those [brackets] become fill-in-the-blank fields. That's the whole point of a prompt here: you reuse it and fill the blanks, instead of rewriting it every time.

Step 2 — Connect your library to your AI

This is the step that makes your library live — your AI reaches into it on demand and always sees your latest version.

Go to Settings → API tokens → New token, and copy the token. (You'll see it once.)
Open the Connect page and pick your tool. You'll get an exact, copy-paste config for your operating system.
Paste it into your tool's config file, drop in your token where it says so, and fully restart the tool.

On Windows? The generated config wraps the command in cmd /c on purpose — Windows can't launch it otherwise. Use the config exactly as Connect gives it to you; don't "simplify" it to a bare npx, or it won't connect.

Shortcut: using a coding agent (Cursor, Claude Code, VS Code, Cline, Windsurf, Codex)? Skip the manual paste — give it the config and ask it to set up the MCP server, at the user level (every project) or project level (just this repo).

You only do this once per tool.

Step 3 — Use it

Back in the app, click the / button on the items you want as commands — that's your slash menu, and it's yours alone. In your editor, type / and you'll see them, grouped under aisd:. Pick a prompt and it walks you through the [fields] — type values right after the command; the AI asks you for any required field you leave out and works around the rest.

Prefer plain language? You don't even need the slash command — just ask your agent to "use my cold-outreach prompt," and it fetches it live over MCP.

That's the loop: save once → connect once → use anywhere, always current.

Where to go next

Core Concepts — the mental model: the seven item types, and the two ways your library reaches your AI (live over MCP vs. a downloaded copy).
Connecting to your AI tools — the full per-tool setup, slash commands, and the optional pull command.
Working with your library — organizing, version history, import, and sharing.
Bringing in a team? Teams & Companies — one shared library everyone pulls from.