nemonix-cli 1.0.0

package/src/config/claude-code-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>

package/src/config/claude-code-config/commands/prompts/saas-create-logos.md

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

package/src/config/claude-code-config/commands/prompts/saas-create-prd.md

@@ -0,0 +1,195 @@
+---
+description: Create a lean Product Requirements Document through interactive discovery conversation
+---
+
+<objective>
+Create a focused Product Requirements Document (PRD) for an MVP through iterative conversation.
+
+Guide the user through defining product vision, user personas, core features, and success metrics. Keep the PRD minimal and focused on essential features that solve real problems. This is the FOUNDATION - the PRD comes FIRST, then ARCHI, then implementation.
+</objective>
+
+<process>
+## Phase 1: Information Discovery
+
+1. **Do NOT write anything until you have answers to ALL 5 areas below**
+
+Ask questions progressively (2-3 at a time, not all at once) until you have complete clarity:
+
+### Area 1: Problem & Vision
+- What problem does this product solve?
+- Who experiences this problem most acutely?
+- What makes this solution unique or different?
+- What does success look like?
+
+### Area 2: Target Users
+- Who are the primary users? (1-3 personas max)
+- What are their key characteristics? (role, context, pain points)
+- What motivates them to use this product?
+- What would make them stop using it?
+
+### Area 3: Core Features
+- What is the ONE thing this product must do? (critical feature)
+- What 2-3 features support that core capability?
+- What features are nice-to-have but not critical for MVP?
+- How will users accomplish their primary goal?
+
+### Area 4: Success Metrics
+- How will you measure if this product is working?
+- What user behavior indicates success?
+- What business metrics matter most?
+
+### Area 5: Constraints & Scope
+- What technical constraints exist?
+- What timeline are you working with?
+- What resources are available?
+- What are you explicitly NOT building in v1?
+
+## Phase 2: Verify Completeness
+
+2. **Before generating PRD**, confirm you have:
+
+- ✅ Core problem clearly defined with specific user experiencing it
+- ✅ 1-3 specific personas with roles, pain points, motivations
+- ✅ THE ONE critical feature + 2-4 supporting must-have features
+- ✅ Specific, measurable metrics (not vague goals)
+- ✅ Clear list of what is NOT being built in v1
+- ✅ Timeline and constraints understood
+
+**IF ANY MISSING**: Ask more questions first. Do NOT generate PRD with gaps.
+
+## Phase 3: Generate PRD
+
+3. **Create PRD.md** with this structure:
+
+```markdown
+# Product Requirements Document: [Product Name]
+
+## Product Vision
+
+**Problem Statement**
+[2-3 sentences describing the core problem]
+
+**Solution**
+[2-3 sentences describing how this product solves it]
+
+**Success Criteria**
+- [Metric 1: quantitative measure]
+- [Metric 2: user behavior indicator]
+- [Metric 3: business outcome]
+
+## Target Users
+
+### Primary Persona: [Name]
+- **Role**: [User role/context]
+- **Pain Points**:
+  - [Pain point 1]
+  - [Pain point 2]
+- **Motivations**: [What drives them]
+- **Goals**: [What they want to accomplish]
+
+### Secondary Persona: [Name] (if applicable)
+- **Role**: [User role/context]
+- **Pain Points**: [Key challenges]
+- **Motivations**: [What drives adoption]
+
+## Core Features (MVP)
+
+### Must-Have Features
+
+#### 1. [Feature Name]
+**Description**: [What this feature does - 2-3 sentences]
+**User Value**: [Why this matters to users]
+**Success Metric**: [How to measure if working]
+
+#### 2. [Feature Name]
+**Description**: [Feature explanation]
+**User Value**: [Benefit to users]
+**Success Metric**: [Measurement criteria]
+
+#### 3. [Feature Name]
+**Description**: [Feature explanation]
+**User Value**: [Benefit to users]
+**Success Metric**: [Measurement criteria]
+
+### Should-Have Features (Post-MVP)
+- [Feature 1]: [Brief description]
+- [Feature 2]: [Brief description]
+
+## User Flows
+
+### Primary User Journey
+1. [Step 1: User action]
+2. [Step 2: User action]
+3. [Step 3: User action]
+4. [Step 4: Outcome achieved]
+
+## Out of Scope (v1)
+
+Explicitly NOT building in MVP:
+- [Feature/capability 1]
+- [Feature/capability 2]
+- [Feature/capability 3]
+
+## Open Questions
+- [Question 1 needing resolution]
+- [Question 2 requiring validation]
+
+## Success Metrics
+
+**Primary Metrics**:
+- [Metric 1]: [Target/goal]
+- [Metric 2]: [Target/goal]
+
+**Secondary Metrics**:
+- [Metric 3]: [Target/goal]
+
+## Timeline & Milestones
+- **MVP Completion**: [Target timeframe]
+- **First User Testing**: [Target]
+- **Launch**: [Target]
+```
+
+## Phase 4: Save and Next Steps
+
+4. **Save PRD.md** in project directory
+
+5. **Suggest next steps**:
+   > "PRD created! Next steps in order:
+   > 1. `/prompts/saas-create-architecture` - Design technical architecture
+   > 2. `/prompts/saas-define-pricing` - Define pricing strategy
+   > 3. `/prompts/saas-create-landing-copy` - Create landing page copy"
+</process>
+
+<constraints>
+**DISCOVERY RULES**:
+- NEVER write PRD until ALL 5 information areas are covered
+- Ask 2-3 questions at a time, not all at once
+- Dig deeper based on responses - don't accept vague answers
+- Push for specific metrics, not goals like "increase engagement"
+
+**MVP FOCUS**:
+- Maximum 3-5 must-have features
+- If user lists 10 features, help them prioritize to 3-5
+- "Out of Scope" section is critical - define boundaries clearly
+- Post-MVP features go in "Should-Have" section
+
+**OUTPUT RULES**:
+- Target 2-3 pages max, not a 20-page spec
+- Every feature needs Description, User Value, Success Metric
+- Be specific and actionable, not vague
+
+**CONVERSATION STYLE**:
+- Keep it conversational, not interrogation
+- Adapt questions based on their industry/context
+- Help users think through trade-offs
+</constraints>
+
+<success_criteria>
+- All 5 information areas have complete answers
+- 1-3 specific personas defined with pain points
+- 3-5 must-have features clearly described
+- Each feature has measurable success metric
+- Out of Scope section explicitly defines boundaries
+- PRD saved as PRD.md in project directory
+- Next steps provided for workflow continuation
+</success_criteria>