aiblueprint-cli 1.4.59 → 1.4.61

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

@@ -0,0 +1,132 @@
+---
+description: Generate clickbait headlines that sound too good to be true for your landing page
+arguments:
+  - name: product-description
+    description: Brief description of your product and what it does
+    required: true
+---
+
+<objective>
+Generate 10+ headline options for a landing page that make visitors say "Wait… what?"
+
+Headlines should sound slightly clickbait - bold enough to spark curiosity and open a loop in the reader's brain.
+</objective>
+
+<process>
+## Phase 1: Understand the Product
+
+**Product**: #$ARGUMENTS.product-description
+
+1. **If project exists**, find and read:
+   - `**/PRD.md` or `**/*prd*.md`
+   - `**/*marketing*/**/*.md`
+   - Existing landing page files
+
+2. **Extract**:
+   - Core transformation (before → after)
+   - Main pain point
+   - Target audience
+   - Key differentiator
+
+## Phase 2: Generate Headlines
+
+4. **Apply the TechCrunch test**: If TechCrunch wrote an article about this product, what would the headline be?
+
+5. **Generate 10+ headlines** using these patterns:
+
+**Result + Timeline**:
+
+- "Launch your SaaS in days, not months"
+- "Learn to code in weeks, not years"
+
+**Transformation Promise**:
+
+- "From zero to shipped in one weekend"
+- "Turn your idea into a live product tonight"
+
+**Pain Elimination**:
+
+- "Never write boilerplate code again"
+- "Stop wasting months building the same features"
+
+**Social Proof + Promise**:
+
+- "Join 7,000+ developers who ship faster"
+- "The secret 10,000 entrepreneurs use to launch"
+
+**Specific Number**:
+
+- "Get 10x more done with half the work"
+- "Build a $10K/month SaaS in 30 days"
+
+**Question Format**:
+
+- "What if you could launch this weekend?"
+- "Ready to ship your startup in 48 hours?"
+
+**Too-Good-To-Be-True**:
+
+- "All the code you need. None of the headaches."
+- "Build like a senior dev on day one."
+
+## Phase 3: Output
+
+6. **Create HEADLINE.md** with this exact format:
+
+```markdown
+# Headline Options for [Product Name]
+
+## Recommended
+
+**[Best headline]**
+_Why: [One sentence explaining why this works]_
+
+## All Options
+
+1. [Headline]
+2. [Headline]
+3. [Headline]
+4. [Headline]
+5. [Headline]
+6. [Headline]
+7. [Headline]
+8. [Headline]
+9. [Headline]
+10. [Headline]
+
+## Testing Advice
+
+Send to 5 friends. After 24h, ask which they remember. Pick that one.
+```
+
+</process>
+
+<constraints>
+**GOOD HEADLINES**:
+- Sound too good to be true
+- Open a curiosity loop
+- Focus on results, not features
+- Are specific (numbers, timeframes)
+- Make people scroll to learn more
+
+**BAD HEADLINES**:
+
+- Generic: "The best solution for X"
+- Feature-focused: "We have AI-powered..."
+- Boring: "Welcome to our product"
+- Safe: "A tool for developers"
+- Vague: "Build better software"
+
+**NEVER**:
+
+- Write "clean" or "safe" copy that nobody remembers
+- Use corporate jargon
+- Lead with features
+- Be forgettable
+  </constraints>
+
+<output>
+**File**: HEADLINE.md in same directory as PRD (or current directory)
+**Content**: 10+ headline options with clear recommendation
+**Format**: Simple list, no fluff
+</output>

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

@@ -0,0 +1,267 @@
+---
+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

@@ -0,0 +1,176 @@
+---
+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>