nemonix-cli 1.0.0

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

@@ -0,0 +1,242 @@
+---
+description: Design technical architecture for a Next.js SaaS application based on PRD requirements
+---
+
+<objective>
+Design the complete technical architecture for a Next.js application based on the Product Requirements Document.
+
+Define tool selection, technology stack decisions, infrastructure choices, and architecture patterns. Challenge every decision to ensure the best fit for specific needs. This comes AFTER the PRD - the PRD defines WHAT to build, this defines HOW to build it.
+</objective>
+
+<context>
+Tools reference: @https://github.com/Melvynx/aiblueprint/blob/main/ai-coding/tools.md
+</context>
+
+<process>
+## Phase 1: Read PRD
+
+1. **Ask for PRD location**:
+   > "Where is your PRD? Please provide the file path or paste the content."
+
+2. **Extract from PRD**:
+   - **Core Features**: What features drive architecture decisions
+   - **User Personas**: Who uses this (impacts willingness to pay for tools)
+   - **Success Metrics**: Performance/scale targets
+   - **Timeline**: MVP timeline (impacts complexity decisions)
+   - **Out of Scope**: What WON'T be built in v1
+
+3. **Map technical implications**:
+   - Real-time features → Need WebSocket/real-time database
+   - File uploads → Need storage solution
+   - AI features → Need LLM integration
+   - Multi-user/teams → Need robust auth and permissions
+   - High traffic → Need caching and performance optimization
+
+## Phase 2: Read Tools Reference
+
+4. **Fetch tools.md** - Read the complete tool reference at:
+   https://github.com/Melvynx/aiblueprint/blob/main/ai-coding/tools.md
+
+5. **Use as primary source** for tool recommendations
+
+## Phase 3: Information Gathering
+
+6. **Ask questions progressively** (don't ask all at once):
+
+**Frontend Requirements**:
+- UI component strategy? (shadcn/ui, custom, other)
+- Client-side state management beyond React?
+- URL state requirements? (filters, search, pagination)
+- Data fetching pattern? (Server Components, TanStack Query, mix)
+
+**Backend & API**:
+- API pattern preference? (Server Actions, API Routes, both)
+- External API access needed?
+- Validation/security layer? (Zod, rate limiting)
+- Third-party API integrations?
+
+**Authentication & Authorization**:
+- Authentication method? (email/password, OAuth, magic link, OTP)
+- Organizations/team features?
+- Permission model? (simple roles, complex RBAC, none)
+
+**Database & Data**:
+- Data type? (relational, document, real-time, files)
+- SQL vs NoSQL preference?
+- Real-time features? (live updates, collaborative editing)
+- Expected data volume and query patterns?
+- ORM preference? (Prisma, Drizzle)
+
+**AI & LLM** (if applicable):
+- AI features needed? (chat, completion, embeddings, vision)
+- LLM providers? (OpenAI, Anthropic, multiple)
+- Streaming responses needed?
+
+**Infrastructure**:
+- Deployment platform? (default: Vercel)
+- Expected traffic/scale?
+- Background jobs or cron tasks?
+- Budget constraints?
+
+**Additional**:
+- Email sending? (transactional, marketing)
+- File uploads/storage?
+- Payment processing?
+- Analytics/monitoring?
+
+## Phase 4: Challenge Every Decision
+
+7. **For EVERY tool choice**, challenge with:
+
+**"Why This?" Challenge**:
+- Why this tool specifically?
+- What are the alternatives?
+- What's the trade-off?
+
+**"Do You Really Need It?" Challenge**:
+- Can you ship without this?
+- Is this solving a real problem or hypothetical future problem?
+- What's the simplest solution that could work?
+
+**"What's The Cost?" Challenge**:
+- Learning curve for the team?
+- Monetary cost at scale?
+- Maintenance burden?
+
+## Phase 5: Generate Architecture Document
+
+8. **Only after gathering ALL information**, create ARCHI.md:
+
+```markdown
+# Technical Architecture: [Project Name]
+
+## Architecture Overview
+
+**Philosophy**: [2-3 sentences on approach and principles]
+
+**Tech Stack Summary**:
+- Framework: [e.g., Next.js 15 with App Router]
+- Deployment: [e.g., Vercel serverless]
+- Database: [e.g., Neon PostgreSQL with Prisma]
+- Authentication: [e.g., Better Auth with email/password]
+
+## Frontend Architecture
+
+### Core Stack
+- **Framework**: [Tool + version]
+  - **Why**: [Specific reason]
+  - **Trade-off**: [What you gain vs sacrifice]
+
+- **UI Components**: [Tool]
+  - **Why**: [Reason]
+  - **Trade-off**: [Analysis]
+
+### State Management
+- **Global State**: [Tool or "React hooks only"]
+- **Server State**: [Tool + pattern]
+- **URL State**: [Tool or "Not needed"]
+
+### Data Fetching Strategy
+[Describe pattern - Server Components first, Client when needed, etc.]
+
+## Backend Architecture
+
+### API Layer
+- **Pattern**: [Server Actions / API Routes / Both]
+- **Validation**: [Tool]
+- **Security**: [Rate limiting, CORS config]
+
+### Authentication & Authorization
+- **Provider**: [Tool] - **Why**: [Reason]
+- **Method**: [Email/password, OAuth, etc.]
+- **Authorization**: [Permission model description]
+
+### Database & Data Layer
+- **Database**: [Tool + type] - **Why**: [Reason]
+- **ORM**: [Tool] - **Why**: [Justification]
+- **Real-time**: [Tool/approach if needed]
+
+### AI Integration (if applicable)
+- **SDK**: [Tool]
+- **Providers**: [Primary + fallback]
+- **Use Cases**: [Feature → model mapping]
+
+## Infrastructure & Deployment
+
+- **Platform**: [Platform] - **Why**: [Reason]
+- **Region Strategy**: [Single/multi/edge]
+- **Background Jobs**: [Tool or "Not needed"]
+- **Monitoring**: [Tools for app monitoring, errors, analytics]
+
+## Additional Services
+
+- **Email**: [Provider or "Not needed"]
+- **Storage**: [Provider or "Not needed"]
+- **Payments**: [Provider or "Not needed"]
+
+## Architecture Decision Records
+
+### ADR-001: [Key Decision Title]
+- **Context**: [Why decision was needed]
+- **Decision**: [What was decided]
+- **Alternatives**: [What else was evaluated]
+- **Rationale**: [Why this choice]
+- **Consequences**: [Trade-offs]
+
+## Folder Structure
+[Project structure diagram]
+
+## Cost Estimation
+
+### Monthly at Scale
+- Database: $[amount]
+- Hosting: $[amount]
+- [Other services]
+- **Total**: ~$[total]/month at [expected scale]
+
+### Free Tier Limits
+- [Service]: [Limits]
+
+## Implementation Priority
+
+### Phase 1: Foundation
+1. [Setup task]
+2. [Setup task]
+
+### Phase 2: Core Features
+1. [Feature]
+2. [Feature]
+
+### Phase 3: Enhancement
+1. [Enhancement]
+```
+</process>
+
+<constraints>
+**MANDATORY BEFORE WRITING**:
+- PRD read completely
+- Tools reference read
+- ALL 8 information areas answered
+- Every tool choice challenged
+
+**CHECKLIST**:
+- ✅ PRD understanding complete
+- ✅ Frontend stack decided (aligned with PRD UI needs)
+- ✅ Backend stack decided (supporting PRD features)
+- ✅ Auth strategy decided (matching PRD user personas)
+- ✅ Database choice made (based on PRD data requirements)
+- ✅ AI requirements specified (from PRD AI features)
+- ✅ Infrastructure decided (based on PRD timeline/metrics)
+- ✅ Additional services identified (driven by PRD features)
+
+**IF ANY MISSING**: Ask more questions first
+</constraints>
+
+<success_criteria>
+- Every technology choice has clear "Why" and "Trade-off"
+- Architecture aligns with ALL PRD features
+- Cost estimation included
+- Implementation phases defined
+- Architecture Decision Records for key choices
+- ARCHI.md saved in same directory as PRD
+</success_criteria>

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