Project Assets

Project assets are reference files you upload to help Trinity's AI agents understand your project visually and contextually — wireframes, brand guides, specs, screenshots, mockups, PDFs.

Accessing Assets

Two places show the same pool of assets:

  • Project Settings → General → Project Assets — full view, upload, import folders, AI-generate descriptions
  • Onboarding Plan step — upload reference files inline while describing your idea

Assets are also surfaced during Align and Architect conversations so you can attach context to a specific feature proposal.

Uploading

You can upload:

  • Individual files — drag and drop or click to browse
  • Entire folders — directory imports preserve the full parent / child / grandchild structure

Supported file types include images (PNG, JPG, SVG, WebP), PDFs, and other common document formats. Files are stored according to your project's storage configuration (Local Only, Trinity Cloud, or BYO S3 — see Project Settings → Storage).

Folder Organization

When you import a folder, Trinity preserves the directory structure with parent-child relationships in the asset tree. This keeps your reference library organized the same way you had it on disk.

AI-Generated Descriptions

After uploading, Trinity can automatically generate descriptions using AI:

  1. Files are analyzed first (up to 3 concurrently)
  2. Folders are described from their children's descriptions
  3. Descriptions are saved back to each asset row

This makes assets searchable and, more importantly, lets agents understand what each file contains without having to open it.

How Agents Use Assets

Planning prompts include an asset block ({{ASSET_BLOCK}}) that tells the planning pipeline what references are available. The planning pipeline then:

  • Lists which uploaded assets each story should consult
  • Passes the relevant asset IDs into the story's assets field
  • Implementing agents read those assets when they hit that story

For example: upload a wireframe for a login page, and the story for building the login page will reference the wireframe so the implementing agent can match the design.

If a story's plan references assets that don't exist (or there are fewer than 3 image assets total when the story expects them), Trinity pauses with a missing_assets gate — skippable via the Skip asset check setting.

Session Scoping

Assets can be scoped to where they were uploaded so the right ones surface in each context:

  • onboarding — assets uploaded during the greenfield wizard
  • architect — assets attached while using Architect to plan a PRD
  • align — assets attached during an Align session
  • audit — assets attached during an Audit chat
  • project-wide (no scope) — global references visible everywhere

The Plan step upload, for example, writes assets under the onboarding scope; Align uploads write under the matching Align scope.

Manifest View

When assets are injected into a prompt, Trinity uses a lightweight manifest — a tree view with just file names, types, and descriptions (no binary content, no storage paths). That keeps the prompt compact while still giving agents enough information to decide what to fetch.

Storage Limits

When using Trinity Cloud storage, every paid seat gets one 5 GB managed pool shared across the user's personal scope and every team they own. Team uploads come out of the team owner's pool — not a separate team bucket. Add-on packs of 10 GB ($5/mo, stack without limit) also attach to the owner's pool.

If you're uploading to a team you don't own and the owner's pool is full, the upload is blocked — the error names the owner so you know whose pool is at capacity. Uploads block immediately on overage; reads keep working for 7 days (grace period), then also block until the pool owner frees space or buys an add-on.

BYO S3 and Local Only storage have no Trinity-imposed limits — good choice for teams that need real volume without growing the owner's managed pool.

See Project Settings → Storage for storage setup details.