fraim-framework 2.0.56 → 2.0.58

package/dist/registry/workflows/legal/saas-contract-development.md

@@ -1,213 +0,0 @@
-# Learned Skill: saas-contract-development
-
-**Category:** legal
-**Created:** 2026-02-03
-**Last Updated:** 2026-02-03
-**Project Context:** SaaS business contract creation and negotiation
-
----
-
-## INTENT
-Create comprehensive, legally protective contract packages for SaaS engagements including SOWs, Terms & Conditions, and strategic pricing negotiations. This skill enables rapid development of professional-grade legal documents that protect IP, limit liability, and position for business growth.
-
-## PRINCIPLES
-- **Legal Protection First**: Always prioritize IP protection and liability limitation
-- **Business Growth Alignment**: Structure contracts to enable expansion and renewal
-- **Clear Boundaries**: Explicitly define scope, responsibilities, and limitations
-- **Professional Positioning**: Use language that establishes expertise and authority
-- **Flexibility with Protection**: Allow for scope changes while maintaining legal safeguards
-
-## WORKFLOW
-
-### Step 1: Engagement Analysis
-**Objective**: Understand the business context and legal requirements
-
-**Actions**:
-1. Analyze customer profile and industry (financial services, healthcare, etc.)
-2. Identify service delivery model (training, managed services, software licensing)
-3. Assess pricing strategy and revenue model
-4. Determine liability exposure and risk factors
-5. Review existing customer feedback and scope changes
-
-**Tools/Resources**:
-- Customer discovery documents
-- Pricing strategy documents
-- Industry-specific compliance requirements
-- Existing contract templates
-
-**Output**: Clear understanding of engagement scope, risks, and legal requirements
-
-### Step 2: Document Structure Planning
-**Objective**: Design the optimal contract package structure
-
-**Actions**:
-1. Determine if MSA is needed (single engagement vs. ongoing relationship)
-2. Plan SOW scope and deliverables structure
-3. Identify Terms & Conditions requirements
-4. Map pricing model to contract terms
-5. Plan signature and execution process
-
-**Tools/Resources**:
-- Contract template library
-- Legal precedent research
-- Industry standard practices
-
-**Output**: Complete document package plan with clear hierarchy
-
-### Step 3: SOW Development
-**Objective**: Create a comprehensive Statement of Work
-
-**Actions**:
-1. **Engagement Summary**: Clear objective and delivery model
-2. **Scope Definition**: Detailed in-scope and out-of-scope items
-3. **Pricing Structure**: Transparent pricing with flexibility clauses
-4. **Success Metrics**: Measurable outcomes and evaluation criteria
-5. **IP and Confidentiality**: Clear ownership and protection terms
-6. **Signature Block**: Professional execution format
-
-**Key SOW Elements**:
-- Advisory vs. delivery accountability boundaries
-- Pricing reevaluation clauses for expansion
-- Flexible scope change management
-- Clear customer responsibility statements
-
-**Tools/Resources**:
-- SOW templates (`templates/sow-template.md`)
-- Pricing calculators
-- Success metrics frameworks
-- Template variables guide (`templates/template-variables.md`)
-
-**Output**: Complete, professional SOW ready for negotiation
-
-### Step 4: Terms & Conditions Creation
-**Objective**: Develop comprehensive SaaS Terms & Conditions
-
-**Actions**:
-1. **Service Description**: Clear platform and service definitions
-2. **IP Protection**: Comprehensive ownership and licensing terms
-3. **Liability Limitation**: Maximum protection within legal bounds
-4. **Data Protection**: Privacy and security commitments
-5. **Service Levels**: Realistic availability and support commitments
-6. **Legal Framework**: Governing law, dispute resolution, termination
-
-**Critical T&C Sections**:
-- Zero or minimal liability clauses
-- Strong IP retention language
-- Minimal data retention policies
-- Flexible support commitments
-- Comprehensive indemnification
-
-**Tools/Resources**:
-- Legal template libraries (`templates/saas-terms-template.md`)
-- Industry standard T&C examples
-- Jurisdiction-specific requirements
-- Template variables guide (`templates/template-variables.md`)
-
-**Output**: Legally protective Terms & Conditions document
-
-### Step 5: Document Integration & Review
-**Objective**: Ensure document consistency and legal coherence
-
-**Actions**:
-1. Cross-reference SOW and T&C for consistency
-2. Verify pricing alignment across documents
-3. Check IP ownership consistency
-4. Validate liability protection coverage
-5. Ensure professional formatting and presentation
-
-**Review Checklist**:
-- [ ] IP ownership clearly defined in both documents
-- [ ] Liability limitations consistent
-- [ ] Pricing terms align with business model
-- [ ] Scope boundaries clearly established
-- [ ] Professional presentation quality
-
-**Tools/Resources**:
-- Document comparison tools
-- Legal review checklists
-- Professional formatting standards
-
-**Output**: Integrated, consistent contract package
-
-### Step 6: PDF Generation & Delivery
-**Objective**: Create professional presentation-ready documents
-
-**Actions**:
-1. Install markdown-to-PDF conversion tools (`npm install -g md-to-pdf`)
-2. Convert documents with professional formatting
-3. Verify PDF quality and readability
-4. Organize files for client delivery
-5. Prepare document package for negotiation
-
-**PDF Generation Commands**:
-```bash
-md-to-pdf "document.md" --pdf-options '{"format": "A4", "margin": {"top": "1in", "right": "1in", "bottom": "1in", "left": "1in"}}'
-```
-
-**Tools/Resources**:
-- md-to-pdf npm package
-- PDF formatting standards
-- Professional document templates
-
-**Output**: Professional PDF contract package ready for client presentation
-
-
-### Common Pitfalls
-- **Scope Creep**: Not clearly defining out-of-scope items
-- **Liability Exposure**: Insufficient liability limitation language
-- **IP Confusion**: Unclear ownership of work product vs. platform
-- **Pricing Rigidity**: No mechanism for scope or pricing adjustments
-- **Poor Presentation**: Unprofessional document formatting
-
-## SUCCESS CRITERIA
-- [ ] Complete contract package (SOW + T&C) created
-- [ ] IP ownership clearly protected
-- [ ] Liability exposure minimized or eliminated
-- [ ] Pricing structure supports business growth
-- [ ] Professional PDF documents generated
-- [ ] Client-ready presentation package delivered
-- [ ] Legal boundaries clearly established
-- [ ] Expansion/renewal mechanisms included
-
-## PRICING STRATEGY INTEGRATION
-
-### Tier-Based Pricing Approach
-- **Core Framework**: Low-cost entry point
-- **Acceleration Academy**: Training + software bundle
-- **Managed Delivery**: High-touch service delivery
-
-### Contract Pricing Tactics
-- Hybrid models (licensing + services)
-- Reevaluation clauses for expansion
-- Volume discounts for longer commitments
-- Success-based pricing adjustments
-
-## LEGAL PROTECTION CHECKLIST
-
-### IP Protection
-- [ ] Platform ownership retained
-- [ ] Work product ownership defined
-- [ ] Improvement rights reserved
-- [ ] Feedback usage rights secured
-
-### Liability Limitation
-- [ ] Zero liability clause (where legally permissible)
-- [ ] Warranty disclaimers included
-- [ ] Consequential damages excluded
-- [ ] Maximum liability caps set
-
-### Data Protection
-- [ ] Minimal data retention policies
-- [ ] Processing purpose limitations
-- [ ] Security commitment levels
-- [ ] Breach notification procedures
-
-## NOTES
-- Always customize jurisdiction and governing law based on business location
-- Consider industry-specific compliance requirements (SOC 2, HIPAA, etc.)
-- Maintain template library for rapid contract development
-- Keep pricing strategy documents aligned with contract terms
-- Regular legal review recommended for template updates
-- PDF generation ensures professional presentation and prevents unauthorized edits
-- **Templates Available**: Use `templates/sow-template.md` and `templates/saas-terms-template.md` with `templates/template-variables.md` guide for rapid contract creation. Get these files using get_fraim_file MCP toolcall
-- **Variable Substitution**: All `[VARIABLE]` placeholders must be replaced before finalizing documents

package/dist/registry/workflows/legal/trademark-filing.md

@@ -1,77 +0,0 @@
-# Workflow: trademark-filing
-
-**Path:** `workflows/legal/trademark-filing.md`
-
----
-
-# Trademark Filing Workflow
-
-## INTENT
-To conduct comprehensive trademark searches, analyze registrability, and file trademark applications that protect brand names, logos, and slogans while avoiding conflicts with existing marks and maximizing protection scope.
-
-## PRINCIPLES
-- **Comprehensive Search**: Thorough analysis of existing trademarks and common law rights
-- **Strategic Classification**: Optimal selection of goods/services classes for maximum protection
-- **Strong Distinctiveness**: Ensure marks are distinctive and protectable
-- **Global Perspective**: Consider international trademark strategy and Madrid Protocol
-- **Brand Protection**: Create comprehensive brand protection strategy
-
-## TRADEMARK FILING WORKFLOW
-
-### Step 1: Trademark Identification
-Define the marks to be protected:
-- Word marks (brand names, slogans)
-- Design marks (logos, symbols)
-- Combined marks (word + design)
-- Trade dress (product appearance)
-- Sound marks or other non-traditional marks
-
-### Step 2: Comprehensive Trademark Search
-Conduct multi-level search strategy:
-- USPTO Trademark Electronic Search System (TESS)
-- State trademark databases
-- Common law trademark search
-- Domain name availability
-- Social media handle availability
-- International trademark databases
-
-### Step 3: Registrability Analysis
-Evaluate trademark strength and registrability:
-- **Distinctiveness**: Arbitrary, suggestive, descriptive, or generic
-- **Likelihood of Confusion**: Similarity to existing marks
-- **Absolute Bars**: Descriptive, deceptive, scandalous content
-- **Prior Rights**: Common law and registered trademark conflicts
-
-### Step 4: Goods and Services Classification
-Strategic class selection and description:
-- International Classification (Nice Classification)
-- Broad vs. narrow descriptions
-- Future business expansion considerations
-- Multi-class filing strategy
-
-### Step 5: Filing Strategy Development
-Determine optimal filing approach:
-- Intent-to-Use vs. Use-in-Commerce
-- Madrid Protocol for international protection
-- Priority filing jurisdictions
-- Timing and budget considerations
-
-### Step 6: Application Preparation and Filing
-Create complete trademark application:
-- Mark identification and description
-- Goods/services descriptions
-- Specimens of use (if applicable)
-- Declaration and signatures
-- Filing fees and forms
-
-## TEMPLATE USAGE
-
-Use `get_fraim_file({ path: "templates/legal/TRADEMARK-TEMPLATE.md" })` to create:
-- `docs/legal/trademarks/{mark-name}-{date}-application.md`
-
-## OUTPUT
-- Comprehensive trademark search report
-- Registrability analysis and recommendations
-- Professional trademark application
-- International filing strategy
-- Brand protection roadmap

package/dist/registry/workflows/marketing/content-creation.md

@@ -1,37 +0,0 @@
-# Workflow: content-creation
-
-**Path:** `workflows/marketing/content-creation.md`
-
----
-
-# Content Creation Phase
-
-## INTENT
-To produce high-quality marketing assets, including blog posts, social media content, and email campaigns, that effectively communicate the feature's value.
-
-## PRINCIPLES
-- **Storytelling**: Use narratives to engage the audience.
-- **Visual Excellence**: Ensure all assets are visually appealing and on-brand.
-- **Consistency**: Maintain a consistent voice and style across all content.
-- **Action-Oriented**: Include clear calls to action in all materials.
-
-## CONTENT CREATION WORKFLOW
-
-### Step 1: Asset Identification
-- What assets are needed based on the strategy? (Blog post, Social thread, Email)
-
-### Step 2: Drafting
-- Create drafts for each asset in `docs/marketing/content/{issue_number}/`
-- Follow the brand voice guidelines.
-
-### Step 3: Visual Asset Prep
-- Identify core screenshots or diagrams needed.
-- Write descriptions for images.
-
-### Step 4: Review
-- Ensure content is free of errors and aligns with the strategy.
-
-## OUTPUT
-- Blog Post Draft
-- Social Media Thread Draft
-- Email Campaign Draft

package/dist/registry/workflows/marketing/convert-to-pdf.md

@@ -1,235 +0,0 @@
-# Convert to PDF Workflow
-
-## INTENT
-To provide agents with a reliable workflow for converting markdown files to professional PDF documents, enabling seamless document sharing and archival while maintaining formatting integrity and visual appeal.
-
-## PRINCIPLES
-- **Format Preservation**: Maintain all markdown formatting including tables, code blocks, and images
-- **Professional Output**: Generate clean, readable PDFs suitable for business use
-- **Flexible Configuration**: Support various paper formats, margins, and styling options
-- **Error Resilience**: Handle common conversion issues gracefully with clear error messages
-- **Cross-Platform Compatibility**: Work consistently across Windows, macOS, and Linux
-
-## Overview
-This workflow guides agents through converting markdown files to PDF format using the markdown-to-pdf script. The conversion maintains formatting, supports code highlighting, tables, and images while producing professional-looking PDF documents.
-
-## When to Use
-- User requests converting markdown documentation to PDF
-- Need to generate PDF reports from markdown content
-- Creating printable versions of specifications or documentation
-- Sharing formatted documents with stakeholders who prefer PDF format
-- Archiving documentation in a portable format
-
-## Prerequisites
-Before using this workflow, ensure the following dependencies are installed:
-
-```bash
-npm install puppeteer markdown-it markdown-it-highlightjs
-```
-
-## Script Location
-The conversion script is synced to: `~/.fraim/scripts/markdown-to-pdf.js`
-
-## Workflow Steps
-
-### Phase 1: Validate Environment
-
-1. **Check Dependencies**
-   ```bash
-   node -e "console.log('puppeteer:', require.resolve('puppeteer')); console.log('markdown-it:', require.resolve('markdown-it')); console.log('markdown-it-highlightjs:', require.resolve('markdown-it-highlightjs'));"
-   ```
-
-2. **Verify Script Availability**
-   - Confirm `~/.fraim/scripts/markdown-to-pdf.js` exists
-   - Check script permissions (executable on Unix systems)
-
-3. **Test Basic Functionality**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js --help
-   ```
-
-### Phase 2: Prepare Input
-
-1. **Validate Input File**
-   - Confirm markdown file exists and is readable
-   - Check for any syntax issues in markdown
-   - Verify image paths are correct and accessible
-
-2. **Determine Output Requirements**
-   - Ask user about desired output location
-   - Confirm paper format preferences (A4, Letter, etc.)
-   - Check if custom styling is needed
-   - Determine header/footer requirements
-
-3. **Prepare Output Directory**
-   - Ensure output directory exists
-   - Verify write permissions
-
-### Phase 3: Execute Conversion
-
-1. **Basic Conversion**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js <input.md>
-   ```
-
-2. **Advanced Conversion with Options**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js <input.md> [output.pdf] [options]
-   ```
-
-3. **Monitor Progress**
-   - Watch for error messages
-   - Verify successful completion
-   - Check output file size and accessibility
-
-### Phase 4: Validate Output
-
-1. **Verify PDF Generation**
-   - Confirm PDF file was created
-   - Check file size is reasonable
-   - Verify file is not corrupted
-
-2. **Quality Check**
-   - Review formatting preservation
-   - Check image rendering
-   - Verify code block highlighting
-   - Confirm table alignment
-
-3. **User Acceptance**
-   - Share output location with user
-   - Confirm output meets requirements
-   - Offer to regenerate with different options if needed
-
-### Available Options
-
-| Option | Description | Example |
-|--------|-------------|---------|
-| `--format <format>` | Paper format (A4, Letter, Legal, etc.) | `--format Letter` |
-| `--margin <margin>` | Page margins in inches | `--margin 1` |
-| `--css <file>` | Custom CSS file for styling | `--css custom.css` |
-| `--header <text>` | Header text | `--header "Company Report"` |
-| `--footer <text>` | Footer text | `--footer "Page <span class='pageNumber'></span>"` |
-| `--landscape` | Use landscape orientation | `--landscape` |
-| `--no-background` | Disable background graphics | `--no-background` |
-
-### Common Examples
-
-1. **Basic conversion:**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js README.md
-   ```
-
-2. **Specify output location:**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js docs/spec.md output/specification.pdf
-   ```
-
-3. **Letter format with custom margins:**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js report.md --format Letter --margin 0.75
-   ```
-
-4. **With custom styling:**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js document.md --css styles/custom.css --header "Project Documentation"
-   ```
-
-5. **Landscape orientation:**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js wide-table.md --landscape --format A3
-   ```
-
-## Agent Instructions
-
-When a user requests markdown to PDF conversion:
-
-1. **Identify the source file(s)**: Confirm which markdown file(s) need to be converted
-2. **Check dependencies**: Verify that required npm packages are installed
-3. **Determine output requirements**: Ask about:
-   - Desired output location
-   - Paper format preferences
-   - Custom styling needs
-   - Header/footer requirements
-4. **Execute conversion**: Run the appropriate command with the specified options
-5. **Verify output**: Confirm the PDF was generated successfully and meets requirements
-
-### Error Handling
-
-If the script fails:
-- Check that all dependencies are installed
-- Verify the input file exists and is readable
-- Ensure the output directory is writable
-- Check for any syntax errors in the markdown file
-
-### Troubleshooting Common Issues
-
-1. **Missing dependencies**: Install required packages with npm
-2. **Permission errors**: Ensure write permissions for output directory
-3. **Large files**: Consider breaking large markdown files into smaller sections
-4. **Image issues**: Verify image paths are correct and accessible
-5. **Font rendering**: Use web-safe fonts or include custom font CSS
-
-## Customization
-
-### Custom CSS Styling
-Create a CSS file to customize the PDF appearance:
-
-```css
-/* custom-style.css */
-body {
-  font-family: 'Times New Roman', serif;
-  font-size: 12pt;
-}
-
-h1 {
-  color: #2c3e50;
-  border-bottom: 3px solid #3498db;
-}
-
-code {
-  background-color: #f0f0f0;
-  border: 1px solid #ccc;
-}
-
-@page {
-  margin: 1in;
-  @top-center {
-    content: "Confidential Document";
-  }
-}
-```
-
-### Batch Processing
-For converting multiple files, create a simple loop:
-
-```bash
-for file in docs/*.md; do
-  node ~/.fraim/scripts/markdown-to-pdf.js "$file" "output/$(basename "$file" .md).pdf"
-done
-```
-
-## Quality Assurance
-
-After conversion, verify:
-- All content is present and properly formatted
-- Images are displayed correctly
-- Code blocks maintain syntax highlighting
-- Tables are properly aligned
-- Page breaks occur at appropriate locations
-- Headers and footers appear as expected
-
-## Best Practices
-
-1. **Test with sample content** before processing important documents
-2. **Use consistent styling** across related documents
-3. **Optimize images** for better PDF file size
-4. **Consider accessibility** when choosing fonts and colors
-5. **Version control** both source markdown and generated PDFs when appropriate
-
-## Integration with Other Workflows
-
-This workflow can be combined with:
-- Documentation generation workflows
-- Report automation processes
-- CI/CD pipelines for document publishing
-- Content review and approval workflows