Set up your library

A new library is not empty. It starts with the platform’s starter prompts and skills, and one of them is the setup prompt: the first thing to run from a freshly connected AI app. It reads what you have, asks what you do, and builds the first folders, notes and skills with you.

The one thing to do first

Connect your AI app. See Connect Claude, Connect ChatGPT or Connect Cursor, VS Code and other apps.
Open Connected apps in your FactorIn settings. Under the connection instructions is a sentence ready to copy.
Paste it into your AI app.

The sentence asks the app to read and run the prompt at Prompts/Setup library.md in your library. A library admin can designate a different setup item later, and the sentence follows it.

If you would rather write your own, this does the same job in any connected app:

Read the prompt “Setup library” in my library and follow it.

The first week

A new library is writable for 7 days before it is on a plan. After that it reads until one is chosen, and it still exports whole. That week is enough to find out whether the library changes how your team works. The checklist in the web app tracks the same four steps this page does.

Connect an AI app. Reach your library from Claude, ChatGPT, Cursor or another AI app.
Run the setup prompt. Paste the sentence above.
Use your library. Ask your AI app to use a prompt or skill from your library in your next task. On a Cloud plan, start a run instead.
Invite a teammate. Everybody in the library works from the same files.

What to put in it

Three kinds of file, and each is markdown.

Notes are things to read: a style guide, a competitor digest, a product spec, the standing rules for the Monday plan.
Prompts are instructions to run later: the Thursday digest, the ad-copy brief, the investor-update draft. A prompt can carry JSON Schemas for its inputs and output so an app fills it in the same way every time.
Skills are folders holding a SKILL.md and support files: a reusable capability an AI app follows again and again. Claude and Codex read the same format natively.

A task is a file, and how to do it is links to other files. So write the task, link the style guide, link the prior art, link the skill, and let every run start with exactly that context and nothing else.

Things to ask a connected app

These all work the moment the connection lands.

“List my libraries.” Confirms the connection and shows which libraries you can write to.
“What skills are in my library?” Lists every skill with its description, wherever it sits.
“Search my library for the pricing page.” Searches by content and by name, which is the only way to find an attachment.
“Read the brand voice note and rewrite this draft in it.”
“Turn this conversation into a skill called weekly-digest.” Creates a skill folder with a SKILL.md.
“Save that as a prompt in the Marketing folder.”
“Update the competitor digest with what we just found.” Saves a new version; the old one is kept.
“Archive the old onboarding note.” Hides it without destroying it.

Borrow instead of write

A folder can mirror a GitHub repository, or one folder of it, read-only and pinned to a branch, tag or commit. Every skill inside is found by its SKILL.md, and the mirror carries the repository’s license. Choose Mirror from GitHub when creating content in the web app.

Invite a teammate to the library from its settings, and everybody works from the same files. To share one folder with somebody outside the team, give them a guest grant: they read that folder and everything under it, write only in their own dropbox, and can copy what they read into it. A guest never sees version history or runs.

Next: The MCP tools, for everything a connected app can do.