Prompt Library

The Prompt Library is a powerful feature that lets you create, manage, and version prompts for AI agents. It ensures consistency across your organization and allows you to optimize prompts over time.

Why Use a Prompt Library?

Without a Library

• Each team member writes prompts differently
• No way to share effective prompts
• Can't track what worked and what didn't
• Prompts get lost in chat history

With Fabric's Prompt Library

• Consistency — Everyone uses the same optimized prompts
• Versioning — Track changes and rollback if needed
• Sharing — Share effective prompts across teams
• Analytics — See which prompts perform best
• Templates — Use variables for dynamic content

Prompt Types

System Prompts (Read-Only)

Platform-provided prompts optimized for specific tasks:

• PRD Generator — Creates Product Requirement Documents
• Technical Spec — Generates technical specifications
• Architecture Doc — Designs system architecture documents
• User Story — Creates user stories with acceptance criteria
• API Documentation — Documents API endpoints

These prompts are:

• Tested and optimized by Fabric
• Can't be edited directly
• Can be forked to create custom versions

User Prompts (Editable)

Custom prompts created by you or your organization:

• Full editing control
• Version history
• Organization-wide or personal scope
• Can be based on system prompts

Creating Prompts

You are writing a PRD for {{projectName}}.

The target audience is {{audience}}.

Requirements:
{{#each requirements}}
- {{this}}
{{/each}}

{{#if includeTimeline}}
Include a timeline section with milestones.
{{/if}}

Template Variables

Template variables make prompts dynamic and reusable.

Syntax

{{variableName}}           — Simple variable
{{#if condition}}...{{/if}} — Conditional block
{{#each items}}...{{/each}} — Loop over array
{{#unless condition}}...{{/unless}} — Negative conditional

Built-in Variables

Fabric automatically provides these variables:

Custom Variables

Define your own variables when using prompts:

Create a {{documentType}} for {{featureName}}.

Target users: {{targetUsers}}
Priority: {{priority}}

When using this prompt, you'll be asked to provide values for each variable.

Prompt Bindings

Bindings connect prompts to specific agents or features.

How Bindings Work

┌─────────────────────────────────────────────────────────┐
│                   Prompt Resolution                      │
├─────────────────────────────────────────────────────────┤
│                                                          │
│  1. User-selected prompt (from dropdown)                 │
│     ↓ if not selected                                    │
│  2. User-bound prompt (personal default)                 │
│     ↓ if not found                                       │
│  3. Org-bound prompt (organization default)              │
│     ↓ if not found                                       │
│  4. System-bound prompt (platform default)               │
│     ↓ if not found                                       │
│  5. Fallback (hardcoded prompt)                         │
│                                                          │
└─────────────────────────────────────────────────────────┘

Creating a Binding

Versioning

Every prompt maintains a version history.

Automatic Versioning

When you edit a prompt:

1. A new version is created automatically
2. Previous versions are preserved
3. You can view the diff between versions
4. Rollback is available anytime

Version History

v3 (current) — Added timeline section
v2           — Improved formatting
v1           — Initial version

Rollback

To rollback to a previous version:

1. Open the prompt
2. Click Version History
3. Select the version to restore
4. Click Restore This Version

A new version is created (rollbacks don't delete history).

Organization Prompts

Sharing Prompts

Share prompts with your organization:

1. Create or edit a prompt
2. Set scope to Organization
3. Save the prompt

All organization members can now:

• View the prompt
• Use the prompt
• Fork to create personal versions

Admin Controls

Organization admins can:

• Create organization-wide prompts
• Set default prompts for the organization
• Manage prompt access permissions
• View usage analytics

Best Practices

Writing Effective Prompts

Be Specific

❌ "Write a document about the feature"
✅ "Write a PRD for {{featureName}} that includes:
    - Problem statement
    - Proposed solution
    - User stories
    - Success metrics"

Use Context

❌ "Create user stories"
✅ "Based on the PRD for {{projectName}}, create user stories
    that follow the format:
    As a [user type], I want [goal] so that [benefit]"

Include Examples

"Format the output like this example:

## User Story 1
**As a** customer
**I want** to reset my password
**So that** I can regain access to my account

### Acceptance Criteria
- [ ] User receives reset email within 1 minute
- [ ] Reset link expires after 24 hours"

Prompt Organization

Naming Convention

[Type] - [Purpose] - [Version/Variant]

Examples:
"PRD - Feature Request - Technical"
"Story - Bug Fix Template"
"Spec - API Documentation - REST"

Categories

• Document generation prompts
• Code review prompts
• Analysis prompts
• Communication prompts

Testing Prompts

Before making a prompt organization-wide:

1. Test with various inputs
2. Check output quality
3. Verify variable handling
4. Get feedback from team members
5. Iterate based on results

Analytics

Track prompt performance:

Access analytics in Settings → Prompt Library → Analytics.

Next Steps