> ## Documentation Index > Fetch the complete documentation index at: https://docs.loisforword.com/llms.txt > Use this file to discover all available pages before exploring further. # Building Prompt Libraries > How to build a reusable prompt library in LOIS for Word for consistent legal review, with templates organized by contract type, clause, and review stage. A prompt library is your collection of tested, refined prompts that work reliably for specific situations. Instead of recreating prompts from scratch, you build a repository of proven instructions that you and your team can reuse. ## Why build a prompt library Prompt libraries turn individual expertise into team assets. They: * Ensure consistent quality across all reviews * Save time by eliminating redundant prompt writing * Capture best practices discovered through trial and error * Enable less experienced team members to work at a higher level * Create institutional knowledge that survives staff changes Think of it as your team's collective playbook for AI interactions. ## What makes a good library prompt ### Proven reliability Only save prompts that consistently produce good results. Test each prompt on at least 3-5 different documents before adding it to your library. ### Clear purpose Each prompt should solve a specific problem. Name and describe it so others know exactly when to use it. ``` Name: "BAA HIPAA Compliance Check" Purpose: "Identifies gaps in Business Associate Agreements for HIPAA compliance" When to use: "First review of any healthcare vendor agreement" ``` ### Flexible structure Good library prompts work across variations while maintaining quality: ``` Base prompt: "Review this [document type] as [party role]" Variables: [document type] and [party role] can change Constants: Review structure stays the same ``` ## Organizing your library ### By document type Create folders for each agreement type: ``` /NDA - Mutual NDA First Review - Unilateral NDA Recipient Check - NDA Compliance Verification /MSA - Vendor MSA Risk Assessment - Customer MSA Negotiation Prep - MSA Amendment Review ``` ### By function Organize by what the prompt does: ``` /Diagnostics - Find Missing Provisions - Check Internal Consistency - Identify Ambiguous Terms /Negotiation - Predict Counterparty Pushback - Generate Fallback Positions - Draft Compromise Proposals ``` ### By risk level Group by deal importance: ``` /High Stakes - Board-Level Review - Regulatory Compliance Check - Multi-Million Dollar Deal Prep /Routine - Standard Vendor Review - Quick NDA Check - Amendment Summary ``` ## Building library prompts ### Start with working prompts When a prompt works well, immediately save it: 1. Copy the exact prompt you used 2. Note what made it successful 3. Document any adjustments needed 4. Test on similar documents 5. Refine and save to library ### Create modular components Build prompts in reusable pieces: ``` Context Module: "I am [role] reviewing [document]" Industry Module: "Apply [industry] standards and [regulation]" Output Module: "Provide results as [format]" ``` Combine modules for different situations. ### Include usage instructions Every library prompt needs: ``` Title: Clear, descriptive name Purpose: What problem this solves When to use: Specific triggers or situations Variables: What you need to customize Expected output: What they'll get back Example: One real use case ``` ### Version control Track prompt evolution: ``` v1.0 - Initial prompt (date) v1.1 - Added regulatory context (date) v1.2 - Refined output format (date) v2.0 - Major revision for new AI model (date) ``` ## Common library prompts ### The universal diagnostic ``` Identify in this [document type]: 1. Missing standard provisions 2. Unusual or non-market terms 3. Internal contradictions 4. Undefined important terms 5. One-sided rights or obligations Focus on material business risks only. ``` ### The negotiation predictor ``` As opposing counsel for [counterparty description]: 1. What are your top 3 objections to our changes? 2. What fallback would you accept? 3. What would make you walk away? ``` ### The compliance checker ``` Review for [regulation] compliance: 1. Required provisions present? 2. Prohibited terms included? 3. Gaps that need addressing? Cite specific regulatory sections. ``` ### The executive briefer ``` For [executive role] review: - Deal value and structure (1 sentence) - Critical risks (3 bullets max) - Recommended action (1 sentence) - Decisions needed (bullet list) One page maximum. ``` ## Maintaining your library ### Regular testing Prompts degrade over time as AI models update. Test your library quarterly: * Run key prompts on new documents * Check if output quality has changed * Update prompts that no longer perform * Archive obsolete prompts ### Team contributions Encourage prompt sharing: * Create submission process for new prompts * Reward effective prompt creation * Share success stories * Build collaborative improvement culture ### Performance tracking Monitor which prompts get used and how they perform: * Usage frequency * Success rate * Time saved * User feedback Focus improvement efforts on high-use prompts. ## Sharing and security ### Access control Prompts are strategic IP. Control who can: * View prompts * Use prompts * Edit prompts * Add new prompts ### Documentation standards Require consistent documentation: * Clear naming conventions * Complete usage instructions * Test results * Update history ### Training integration Use the library for onboarding: * New team members start with proven prompts * Learn what works through examples * Understand firm's approach to AI ## Common library mistakes * **Saving everything** Only save prompts that prove their value repeatedly. Quality over quantity. * **No maintenance** Abandoned libraries become prompt graveyards. Schedule regular reviews. * **Over-specificity** Too narrow prompts rarely get reused. Find the right abstraction level. * **Poor documentation** Without context, even good prompts become useless. ## The key insight Your prompt library is your team's collective intelligence about working with AI. Every refined prompt represents hours of learning compressed into reusable knowledge. The teams that build and maintain strong libraries consistently outperform those that start from scratch each time. ## Remember Building a prompt library isn't extra work – it's an investment that pays compound returns. Every prompt you save is future time saved, errors avoided, and quality assured. Start small, build systematically, and watch your team's AI capabilities grow exponentially.