---
name: prism-project-builder
description: "Use when an AI client needs to create or structure a Prism Project with sources, notes, links, relationships, artifacts, and a durable research map."
---

# Project builder

Turn source inputs into a connected Project with reusable notes, artifacts, and research structure.

## Before you start

Copy this guidance into ChatGPT, Claude, Codex, Grok, or another client that accepts custom instructions. It changes the client's instructions only; it does not grant Prism access. Direct MCP calls require the client's current MCP support, a configured connection, and separately authorized scopes.

Scopes this workflow may need:

- `knowledge:read`
- `library:write`
- `graph:write`

The installed skill does not grant these permissions. Use only the scopes and Projects authorized on the current Prism MCP connection.

## Workflow

1. Orient first and reuse an existing Project when it already matches the user's goal.
2. Create a top-level Project only when needed, then link the relevant companies.
3. Add sources through their canonical ingestion paths and create original notes only for synthesized or user-supplied text.
4. Create requested artifacts or research outputs, then connect them with explicit graph relationships.
5. Create a Project Canvas only when a visual workspace will help, and report progress for longer buildouts.

## Tool routing

- `create_library_folder`, `add_library_folder_company`: Create the Project spine and canonical company context.
- `create_library_note`, `create_artifact`: Save durable synthesis and visual outputs into the Project.
- `create_library_relationships`: Connect outputs to sources, claims, companies, drafts, or other precise nodes.
- `create_library_canvas`: Create a user-visible visual workspace when the research benefits from one.

## Expected result

- A Project with clear purpose, appropriate source inputs, and useful durable outputs.
- New notes, artifacts, claims, and sources are connected to the most precise relevant Prism nodes.
- The user can inspect what was created, which evidence informed it, and what remains open.

## Boundaries

- A skill does not grant Prism access. The connection must separately authorize every required scope and Project.
- Call only tools verified callable by the current AI host. Use discover_prism_actions for granular actions. If a default workflow tool is missing, follow the capability-handshake recovery guidance instead of inventing a substitute tool.
- Read before writing. Mutate Prism only when the user asked for a durable change and the connected tool exposes that exact action.
- Keep retrieved evidence separate from analysis. Cite Prism source ids, titles, snippets, locations, and chunk ids when available.
- Do not create a second Project merely to avoid understanding the existing workspace.
- A new top-level Project already receives an inbound Email address. Create replacement aliases only when the user asks.
- Folder archive, rename, moves, and permanent deletion belong to the separate library:manage scope.