aiblueprint-cli 1.4.81 → 1.4.83

package/agents-config/commands/prompts/saas-create-landing-copywritting.md

@@ -1,267 +0,0 @@
----
-description: Generate conversion-focused landing page copywriting based on PRD and marketing context
----
-
-<objective>
-Generate a complete, ready-to-use landing page copywriting document that converts visitors into customers.
-
-Focus on benefits over features, emotional resonance, and proven conversion frameworks. This comes AFTER the PRD and ARCHI - the PRD defines WHAT to build, ARCHI defines HOW, this creates the COPY that sells.
-</objective>
-
-<process>
-## Phase 1: Locate Project Files
-
-1. **Ask for project location**:
-   > "Where is your project located?"
-
-2. **Find and read all files** (use Glob):
-   - `**/PRD.md` or `**/*prd*.md`
-   - `**/ARCHI.md` or `**/*archi*.md`
-   - `**/*marketing*/**/*.md`
-   - `**/*objection*.md`
-   - `**/*competitive*.md`
-
-3. **Save PRD directory path** - Create LANDING_PAGE.md in SAME directory as PRD
-
-## Phase 2: Extract Context
-
-4. **From PRD extract**:
-   - Target users and personas
-   - Pain points and problems
-   - Features and solutions
-   - Success metrics
-
-5. **From ARCHI extract**:
-   - Technical advantages to translate into benefits
-   - Unique capabilities
-
-6. **From marketing files extract**:
-   - Existing headlines and value props
-   - Objections that need handling
-   - Competitive positioning angles
-
-## Phase 3: Research Best Practices
-
-7. **Web search for**:
-   - "SaaS landing page copywriting 2025 best practices"
-   - "conversion copywriting frameworks AIDA PAS PRESTO"
-   - "high converting landing page examples [industry]"
-
-8. **Analyze 3-5 top landing pages** in same category using WebFetch
-
-## Phase 4: Choose Framework
-
-9. **Select copywriting framework**:
-
-**AIDA** (Attention, Interest, Desire, Action):
-- Use for: Broad audiences, new categories, educational sells
-- Best when: Need to build interest gradually
-
-**PAS** (Problem, Agitate, Solution):
-- Use for: Strong pain points, clear problems, urgent needs
-- Best when: Users actively seeking solutions
-
-**PRESTO** (Promise, Repeat, Evidence, Stakes, Transition, Offer):
-- Use for: Complex products, B2B, service-heavy SaaS
-- Best when: Longer sales cycles, need credibility building
-
-**Hybrid**: Combine frameworks for different sections
-
-## Phase 5: Generate Copy
-
-10. **Create LANDING_PAGE.md** with ALL sections:
-
-```markdown
-# Landing Page Copywriting: [Product Name]
-
-## Target Audience Summary
-[From PRD - who, pain points, goals]
-
-## Copywriting Framework
-**Primary**: [AIDA/PAS/PRESTO/Hybrid]
-**Strategy**: [Brief explanation]
-
----
-
-## HERO SECTION
-
-### Headline (H1)
-**Option 1**: [Benefit-focused]
-**Option 2**: [Timeline/result-focused]
-**Option 3**: [Transformation-focused]
-**Recommended**: [Which and why]
-
-### Subheadline (H2)
-[Supporting detail that clarifies the promise]
-
-### Primary CTA
-**Button**: [Action-oriented text]
-**Micro-copy**: [Trust-building text under button]
-
-### Social Proof Snippet
-[Quick credibility: "Join 10,000+ creators"]
-
----
-
-## PROBLEM SECTION
-
-### Section Headline
-[Empathetic headline calling out the pain]
-
-### Pain Points
-- **[Pain 1]**: [Emotional description]
-- **[Pain 2]**: [Emotional description]
-- **[Pain 3]**: [Emotional description]
-
-### Agitation Paragraph
-[2-3 sentences deepening the pain]
-
----
-
-## SOLUTION SECTION
-
-### Headline
-[How your product solves the problem]
-
-### Value Proposition
-[2-3 sentences on unique approach]
-
-### Benefits (3-4 cards)
-**Benefit 1**: [Headline]
-- Copy: [2-3 sentences]
-- Icon: [Suggestion]
-
-[Repeat for each benefit]
-
----
-
-## FEATURES SECTION
-
-### Section Headline
-[Features presented as benefits]
-
-### Feature 1: [Name]
-**Headline**: [Benefit-focused]
-**Description**: [2-3 sentences - benefit + how it works]
-
-[Repeat for each feature]
-
----
-
-## SOCIAL PROOF
-
-### Section Headline
-[Trust-building headline]
-
-### Testimonials
-**Quote 1**: "[Specific result achieved]"
-- Author: [Name, Role, Company]
-- Result: [Specific metric]
-
-[Repeat 2-3 more]
-
-### Trust Indicators
-- [Number of users]
-- [Notable clients]
-- [Recognition/awards]
-
----
-
-## OBJECTION HANDLING
-
-### Objection 1: [Common concern]
-**Response**: [How you address it]
-
-[Repeat for each objection]
-
----
-
-## FAQ
-
-### Q: [Most common question]
-**A**: [Clear answer]
-
-[5-8 FAQs covering blockers]
-
----
-
-## PRICING (if applicable)
-
-### Section Headline
-[Value-focused]
-
-### Tier 1: [Name] - $X/mo
-**For**: [Who]
-**Features**: [List]
-**CTA**: [Button text]
-
-[Repeat for each tier]
-
-### Guarantee
-[Money-back guarantee text]
-
----
-
-## FINAL CTA
-
-### Headline
-[Compelling call to action]
-
-### Supporting Copy
-[2-3 sentences creating urgency]
-
-### CTA
-**Button**: [Strong action verb]
-**Trust**: [Final reassurance]
-
----
-
-## TONE & VOICE
-
-**Overall**: [Professional/Casual/Technical]
-**Words to use**: [Power words]
-**Words to avoid**: [Jargon to skip]
-```
-</process>
-
-<constraints>
-**BENEFIT TRANSLATION FORMULA**:
-- Feature: "We have X"
-- Function: "X does Y"
-- Benefit: "So you can Z" ← ALWAYS get here
-
-**HEADLINE PATTERNS**:
-- [Benefit] in [Timeframe]: "Create your SaaS in 30 days"
-- [Transformation] for [Audience]: "From Zero to Developer for Entrepreneurs"
-- [Promise] without [Pain]: "Build apps without coding headaches"
-
-**CTA RULES**:
-- Use action verbs: Start, Create, Build, Launch, Join, Get
-- Add value context: "Start Building Free" vs "Sign Up"
-- Create urgency: "Join 500 Early Users"
-
-**NEVER**:
-- Write generic copy that fits any product
-- Lead with features instead of benefits
-- Skip the research phase
-- Use placeholder text instead of real copy
-- Save file in wrong location
-</constraints>
-
-<output>
-**File**: LANDING_PAGE.md in same directory as PRD
-**Content**: Complete copy for all sections (not placeholders)
-**Headlines**: 3 options for hero with recommendation
-**Benefits**: All features translated using benefit formula
-**Objections**: All objections from files addressed
-</output>
-
-<success_criteria>
-- Hero section has 3 headline options with clear recommendation
-- ALL sections have benefit-focused copy (not feature-focused)
-- CTAs are action-oriented and specific
-- All objections from files are addressed
-- Copy aligns with PRD target users and pain points
-- Technical advantages from ARCHI translated to benefits
-- File saved in same directory as PRD
-</success_criteria>

package/agents-config/commands/prompts/saas-create-legals-docs.md

@@ -1,176 +0,0 @@
----
-description: Generate GDPR-compliant Privacy Policy and Terms of Service based on product and data practices
----
-
-<objective>
-Generate comprehensive, GDPR-compliant legal documentation for a SaaS application.
-
-Create a Privacy Policy and Terms of Service that are understandable by regular users while being legally sound. These documents protect both the business and users while building trust.
-</objective>
-
-<process>
-## Phase 1: Locate PRD
-
-1. **Ask for PRD location**:
-   > "Where is your PRD? Please provide the file path."
-
-2. **Extract from PRD**:
-   - Product name and company name
-   - What data is collected (user input, analytics, files)
-   - Third-party integrations (Stripe, analytics, email)
-   - Target regions (EU, US, global)
-   - User account features
-
-3. **Save output path** - Legal docs go in same directory as PRD
-
-## Phase 2: Information Gathering
-
-4. **Collect required information** (ask in batches, not all at once):
-
-**Company Information**:
-- Legal company name and structure (LLC, Inc, SARL)
-- Jurisdiction (State/Country)
-- Registration number (EIN for US, SIRET for France)
-- Complete legal address
-- Contact email for legal/privacy matters
-
-**For French Companies** (CGV required):
-- Numéro SIRET
-- Numéro de TVA intracommunautaire
-- Capital social (if SARL/SAS)
-- RCS (Registre du Commerce et des Sociétés)
-
-**Data Collection**:
-- Account data: email, name, profile info?
-- Payment data: credit cards via Stripe/LemonSqueezy?
-- Content data: what user-created content is stored?
-- Usage data: analytics, logs, interaction data?
-- Cookies: essential only, or analytics/marketing too?
-
-**Third-Party Services** (check which apply):
-- Payment: Stripe / LemonSqueezy / Other
-- Analytics: PostHog / Plausible / Google Analytics
-- Email: Resend / SendGrid / Other
-- Hosting: Vercel / AWS / Other
-- AI: OpenAI / Anthropic / Other
-- Error tracking: Sentry / Other
-
-**Data Practices**:
-- Data retention: How long is data kept?
-- Data deletion: Can users delete their account/data?
-- Data export: Can users export their data?
-- Data sharing: Shared with anyone beyond service providers?
-
-**Terms Specifics**:
-- Free tier available? Limitations?
-- Paid tiers? Refund policy?
-- User-generated content? Moderation?
-- API access? Rate limits?
-- Prohibited uses? (spam, illegal, abuse)
-
-**Dispute Resolution**:
-- Preferred governing law? (Delaware common for US)
-- Mandatory arbitration? (faster, cheaper than court)
-- Class action waiver? (individual claims only)
-
-**Languages Needed**:
-- English version?
-- French version (CGV)?
-- Both?
-
-## Phase 3: Generate Privacy Policy
-
-5. **Create PRIVACY_POLICY.md** with these sections:
-
-- **Introduction**: Company name, what the policy covers
-- **Information We Collect**:
-  - Information provided (account, payment, content)
-  - Information collected automatically (usage, device, cookies)
-- **How We Use Information**: Provide service, process payments, improve, legal compliance
-- **Data Sharing**: Service providers listed by name, legal requirements, business transfers
-- **Data Retention**: How long for each data type
-- **Your Rights**:
-  - All users: access, correct, delete, export
-  - EU users (GDPR): erasure, portability, restrict, object
-  - California users (CCPA): know, delete, opt-out, non-discrimination
-- **Data Security**: Encryption, access controls, limitations
-- **International Transfers**: Where data stored, safeguards
-- **Cookies**: Essential, analytics, marketing - with opt-out info
-- **Children's Privacy**: Not for under 16
-- **Changes to Policy**: How updates are communicated
-- **Contact**: Privacy email and address
-
-## Phase 4: Generate Terms of Service
-
-6. **Create TERMS_OF_SERVICE.md** with these sections:
-
-- **Agreement to Terms**: Using service = agreeing
-- **Description of Service**: What the product does
-- **Accounts**: Creation, security, termination
-- **Subscription and Payment** (if paid):
-  - Pricing and billing
-  - Refund policy
-  - Cancellation
-  - Free tier limitations
-- **Acceptable Use**: What users must NOT do
-- **Intellectual Property**: Company owns service, user owns their content, limited license
-- **Third-Party Services**: Not responsible for integrations
-- **Disclaimer of Warranties**: AS IS, no guarantees
-- **Limitation of Liability**: No indirect damages, liability cap
-- **Indemnification**: User holds company harmless
-- **Governing Law**: Jurisdiction
-- **Dispute Resolution**: Informal first, then arbitration/courts
-- **Changes to Terms**: How updates work
-- **Miscellaneous**: Entire agreement, severability, waiver, assignment
-- **Contact**: Legal email
-
-## Phase 5: Generate French CGV (if needed)
-
-7. **Create CGV.md** if French market - includes:
-- Required company information (SIRET, RCS, TVA)
-- Article structure required by French law
-- Droit de rétractation (14-day withdrawal right)
-- Exception for digital content accessed immediately
-- Médiation de la consommation (required mediator info)
-- Garantie légale de conformité
-</process>
-
-<output>
-**Files created**:
-- `PRIVACY_POLICY.md` - Complete privacy policy
-- `TERMS_OF_SERVICE.md` - Complete terms of service
-- `CGV.md` - French conditions générales de vente (if requested)
-
-All saved in same directory as PRD.
-</output>
-
-<constraints>
-**CRITICAL NOTES**:
-- These are templates, NOT legal advice
-- Recommend professional legal review before production use
-- Adapt based on actual business practices and jurisdiction
-- Keep language understandable to regular users
-
-**DO NOT**:
-- Generate with placeholders - fill in ALL details from gathered info
-- Skip GDPR requirements if serving EU users
-- Omit required disclosures for third-party services
-- Generate without asking for required company information first
-- Skip French-specific requirements if CGV requested
-
-**LEGAL PROTECTION PRIORITY**:
-- Include liability caps and disclaimers
-- Clearly define prohibited uses
-- Specify governing law and venue
-- Include arbitration clause if requested
-</constraints>
-
-<success_criteria>
-- All company and product details filled in (no [brackets])
-- All third-party services disclosed in privacy policy
-- Data practices match actual product features
-- User rights section complete (GDPR, CCPA if applicable)
-- Terms cover payment, refunds, acceptable use
-- Documents saved in same directory as PRD
-- Clear recommendation for professional legal review included
-</success_criteria>

package/agents-config/commands/prompts/saas-create-logos.md

@@ -1,240 +0,0 @@
----
-description: Generate 20 abstract SVG logo variations with brainstorming and HTML showcase
-arguments:
-  - name: app-name
-    description: Name of your app/product
-    required: true
-  - name: app-description
-    description: What does your app do? Who is it for?
-    required: true
----
-
-<objective>
-Generate 20 unique, minimalist SVG logo variations inspired by iconic logos (Stripe, Google, Claude, ChatGPT, Dub, Excalidraw).
-
-Output:
-
-1. `specs/logos/brainstorm.md` - Logo concepts and rationale
-2. `specs/logos/showcase-v1.html` - First batch of 20 logos (increment version for iterations)
-   </objective>
-
-<context>
-**App Name**: #$ARGUMENTS.app-name
-**Description**: #$ARGUMENTS.app-description
-</context>
-
-<process>
-## Phase 0: Ask Clarifying Questions
-
-**BEFORE doing anything**, ask the user these questions using AskUserQuestion:
-
-1. **Logo Style**:
-   - Lettermark (stylized letter like Stripe's "S")
-   - Abstract symbol (like Claude's icon)
-   - Geometric shape (like Airbnb)
-   - Wordmark (full name stylized)
-
-2. **Brand Personality**:
-   - Modern & Techy
-   - Playful & Friendly
-   - Professional & Corporate
-   - Bold & Edgy
-   - Minimal & Clean
-
-3. **Visual Inspiration** (can select multiple):
-   - Stripe (depth, gradients)
-   - Google (simple geometry)
-   - Linear (sharp, modern)
-   - Notion (clean, minimal)
-   - Discord (friendly, rounded)
-
-Wait for user answers before proceeding.
-
-## Phase 1: Analyze & Brainstorm
-
-1. **Study the app name** with user preferences in mind:
-   - Break down letters, sounds, meaning
-   - Find visual metaphors (e.g., "Mail" → envelope, arrow, @ symbol)
-   - Match to selected brand personality
-
-2. **Apply user's style choices**:
-   - Use selected logo style as primary direction
-   - Incorporate visual inspiration references
-   - Align with brand personality
-
-3. **Create brainstorm.md**:
-
-```markdown
-# Logo Brainstorm: [App Name]
-
-## Brand Analysis
-
-- **Name meaning**: [What does the name evoke?]
-- **Core function**: [What does the app do?]
-- **Target vibe**: [Modern/Playful/Professional/Bold/Minimal]
-
-## Visual Concepts
-
-### Lettermark Ideas
-
-1. [First letter stylized - describe approach]
-2. [Initials combined - describe approach]
-3. [Full name simplified - describe approach]
-
-### Symbol Ideas
-
-1. [Abstract shape representing core function]
-2. [Geometric interpretation of name]
-3. [Metaphor visualization]
-
-### Style Direction
-
-- **Colors**: Black/white primary (can add accent later)
-- **Style**: Geometric, clean, SVG-optimized
-- **Inspiration**: [Which logos to draw from]
-
-## 20 Variations Plan
-
-1-5: Lettermark variations
-6-10: Abstract symbols
-11-15: Geometric shapes
-16-20: Experimental/unique
-```
-
-## Phase 2: Generate HTML Showcase
-
-4. **Check for existing versions**:
-   - Look for `specs/logos/showcase-v*.html`
-   - Increment version number (v1, v2, v3...)
-   - If v1 exists, create v2, etc.
-
-5. **Create showcase-vX.html** with this structure:
-
-```html
-<!DOCTYPE html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>[App Name] - Logos</title>
-    <style>
-      * {
-        margin: 0;
-        padding: 0;
-        box-sizing: border-box;
-      }
-      body {
-        background: #fff;
-      }
-      .grid {
-        display: grid;
-        grid-template-columns: repeat(5, 1fr);
-      }
-      .cell {
-        aspect-ratio: 1;
-        border: 1px solid #e5e5e5;
-        display: flex;
-        align-items: center;
-        justify-content: center;
-        padding: 24px;
-      }
-      .cell svg {
-        width: 100%;
-        height: 100%;
-        max-width: 80px;
-        max-height: 80px;
-      }
-    </style>
-  </head>
-  <body>
-    <div class="grid">
-      <div class="cell">
-        <svg
-          viewBox="0 0 500 500"
-          fill="none"
-          xmlns="http://www.w3.org/2000/svg"
-        >
-          <!-- SVG content here - use #000 for fills -->
-        </svg>
-      </div>
-      <!-- ... 19 more cells -->
-    </div>
-  </body>
-</html>
-```
-
-## Phase 3: Design 20 Logos
-
-6. **Generate each SVG** following these rules:
-   - ViewBox: `0 0 500 500`
-   - Colors: Black (`#000`) on white background
-   - No gradients in base version
-   - Clean paths, minimal complexity
-   - Must work at 16px and 512px
-
-7. **Logo categories** (adapt based on user's style choice):
-   - **1-5**: Primary style (user's selected logo style)
-   - **6-10**: Secondary variations
-   - **11-15**: Alternative interpretations
-   - **16-20**: Experimental (unique, creative approaches)
-
-8. **Document in brainstorm.md** (not in HTML):
-   - Each logo's concept and rationale
-   - Why it fits the brand
-
-## Phase 4: Iteration Support
-
-9. **After generating**, ask user:
-
-   > "Which logos do you like? I can create v2 with variations of your favorites."
-
-10. **For next iteration**: - Note favorites from previous version - Create `showcase-v2.html` with 20 new variations inspired by favorites - Each version builds on user feedback
-    </process>
-
-<constraints>
-**SVG RULES**:
-- Pure SVG, no raster images
-- Black (`#000`) fills only
-- Simple paths, no complex effects
-- Must scale from favicon to billboard
-
-**DESIGN RULES**:
-
-- Inspired by: Stripe, Google, Claude, ChatGPT, Dub
-- Minimalist, geometric, modern
-- Recognizable at small sizes
-- No text (unless lettermark)
-
-**HTML RULES**:
-
-- Light mode only (white background)
-- 5x4 grid of logos
-- NO titles, NO descriptions, NO text
-- Just logos in cells separated by borders
-- Clean, minimal presentation
-
-**OUTPUT RULES**:
-
-- Create `specs/logos/` directory first
-- Save `brainstorm.md` with concepts and rationale
-- Save `showcase-vX.html` with just the logo grid
-- ONE HTML file per version
-  </constraints>
-
-<output>
-**Files created**:
-1. `specs/logos/brainstorm.md` - Logo concepts and rationale (all text here)
-2. `specs/logos/showcase-v1.html` - Clean 5x4 grid of logos (no text)
-
-**HTML structure**:
-
-- 5x4 grid (20 logos)
-- Each cell: just the SVG, no text
-- Light gray borders between cells
-- White background
-
-**Iteration flow**:
-
-- v1: Initial 20 based on user preferences
-- v2+: Refinements based on user favorites
-  </output>