@riligar/agents-kit 1.10.0 → 1.11.0

package/.agent/skills/riligar-business-startup/references/financial-model.md

@@ -0,0 +1,215 @@
+# Financial Projections
+
+Create comprehensive 3-5 year financial model with revenue projections, cost structure, headcount planning, cash flow analysis, and three-scenario modeling.
+
+## What This Module Creates
+
+1. Cohort-based revenue projections
+2. Detailed cost structure (COGS, S&M, R&D, G&A)
+3. Headcount planning by role
+4. Monthly cash flow analysis
+5. Key metrics (CAC, LTV, burn rate, runway)
+6. Three-scenario analysis
+
+## Step 1: Gather Inputs
+
+**Business Model:**
+- Revenue model (SaaS, marketplace, transaction)
+- Pricing structure (tiers, average price)
+- Target customer segments
+
+**Starting Point:**
+- Current MRR/ARR (if any)
+- Current customer count
+- Current team size
+- Current cash balance
+
+**Growth Assumptions:**
+- Expected monthly customer acquisition
+- Customer retention/churn rate
+- Average contract value (ACV)
+- Sales cycle length
+
+**Cost Assumptions:**
+- Gross margin or COGS %
+- S&M budget or CAC target
+- Current burn rate
+
+**Funding:**
+- Planned fundraising (amount, timing)
+- Pre/post-money valuation
+
+## Step 2: Build Revenue Model
+
+### Cohort-Based Approach
+
+For each month, track:
+1. New customers acquired
+2. Existing customers retained (apply churn)
+3. Revenue per cohort (customers × ARPU)
+4. Expansion revenue (upsells)
+
+**Formula:**
+```
+MRR (Month N) = Σ across all cohorts:
+  (Cohort Size × Retention Rate × ARPU) + Expansion
+```
+
+**Project:**
+- Monthly detail for Year 1-2
+- Quarterly detail for Year 3
+- Annual for Years 4-5
+
+## Step 3: Cost Structure
+
+### 1. Cost of Goods Sold (COGS)
+- Hosting/infrastructure
+- Payment processing
+- Variable customer support
+- Third-party services
+
+Target gross margin:
+- SaaS: 75-85%
+- Marketplace: 60-70%
+- E-commerce: 40-60%
+
+### 2. Sales & Marketing (S&M)
+- Sales team compensation
+- Marketing programs
+- Tools and software
+- Target: 40-60% of revenue (early stage)
+
+### 3. Research & Development (R&D)
+- Engineering team
+- Product management
+- Design
+- Target: 30-40% of revenue
+
+### 4. General & Administrative (G&A)
+- Executive team
+- Finance, legal, HR
+- Office and facilities
+- Target: 15-25% of revenue
+
+## Step 4: Headcount Planning
+
+**For each role:**
+- Title and department
+- Start date (month/quarter)
+- Base salary
+- Fully-loaded cost (salary × 1.3-1.4)
+
+**Departmental ratios:**
+- Engineering: 40-50% of team
+- Sales & Marketing: 25-35%
+- G&A: 10-15%
+- Product/CS: 10-15%
+
+## Step 5: Cash Flow
+
+Monthly cash flow projection:
+
+```
+Beginning Cash Balance
++ Cash Collected (revenue, consider payment terms)
+- Operating Expenses
+- CapEx
+= Ending Cash Balance
+
+Monthly Burn = Revenue - Expenses (if negative)
+Runway = Cash Balance / Monthly Burn Rate
+```
+
+**Include Funding Events:**
+- Timing of raises
+- Amount raised
+- Impact on cash balance
+
+## Step 6: Key Metrics
+
+### Unit Economics
+- CAC (S&M spend / new customers)
+- LTV (ARPU × margin% / churn rate)
+- LTV:CAC ratio (target > 3.0)
+- CAC payback period (target < 18 months)
+
+### Efficiency Metrics
+- Burn multiple (net burn / net new ARR) - target < 2.0
+- Magic number (net new ARR / S&M spend) - target > 0.5
+- Rule of 40 (growth% + margin%) - target > 40%
+
+### Cash Metrics
+- Monthly burn rate
+- Runway in months
+
+## Step 7: Three Scenarios
+
+### Conservative (P10)
+- New customers: -30% vs. base
+- Churn: +20% vs. base
+- Pricing: -15% vs. base
+- CAC: +25% vs. base
+
+### Base (P50)
+- Most likely assumptions
+- Primary planning scenario
+
+### Optimistic (P90)
+- New customers: +30% vs. base
+- Churn: -20% vs. base
+- Pricing: +15% vs. base
+- CAC: -25% vs. base
+
+## Report Tables
+
+### Revenue Projections
+```
+| Month | New Customers | Total Customers | MRR | ARR | Growth % |
+|-------|---------------|-----------------|-----|-----|----------|
+```
+
+### Cost Breakdown
+```
+| Department | Year 1 | Year 2 | Year 3 | % Revenue |
+|------------|--------|--------|--------|-----------|
+| COGS       | $X     | $Y     | $Z     | XX%       |
+| S&M        | $X     | $Y     | $Z     | XX%       |
+| R&D        | $X     | $Y     | $Z     | XX%       |
+| G&A        | $X     | $Y     | $Z     | XX%       |
+```
+
+### Key Metrics
+```
+| Metric | Year 1 | Year 2 | Year 3 | Target |
+|--------|--------|--------|--------|--------|
+| CAC | $X | $Y | $Z | <$A |
+| LTV | $X | $Y | $Z | >$B |
+| LTV:CAC | X | Y | Z | >3.0 |
+| Burn Multiple | X | Y | Z | <2.0 |
+```
+
+### Scenario Comparison
+```
+| Scenario | Year 3 ARR | Customers | Burn | Runway |
+|----------|------------|-----------|------|--------|
+| Conservative | $X | Y | $Z | W mo |
+| Base | $X | Y | $Z | W mo |
+| Optimistic | $X | Y | $Z | W mo |
+```
+
+## Best Practices
+
+**Do:**
+- Use cohort-based revenue model
+- Include 3 scenarios
+- Show monthly detail (Year 1-2)
+- Calculate key metrics
+- Validate against benchmarks
+- Document all assumptions
+
+**Don't:**
+- Be overly optimistic on growth
+- Underestimate costs
+- Forget fully-loaded compensation
+- Ignore cash timing
+- Skip scenario analysis

package/.agent/skills/riligar-business-startup/references/market-analysis.md

@@ -0,0 +1,151 @@
+# Market Opportunity Analysis
+
+Generate comprehensive market opportunity analysis with TAM/SAM/SOM calculations using both bottom-up and top-down methodologies.
+
+## Process Overview
+
+1. Define the target market and customer segments
+2. Gather relevant market data
+3. Calculate TAM using bottom-up methodology
+4. Validate with top-down analysis
+5. Narrow to SAM with appropriate filters
+6. Estimate realistic SOM (3-5 year opportunity)
+7. Present findings in a formatted report
+
+## Step 1: Gather Context
+
+Ask for essential information:
+
+**Product/Service:**
+- What problem is being solved?
+- How does pricing work? (subscription, transaction, etc.)
+
+**Target Customers:**
+- Who is the ideal customer? (industry, size, geography)
+- Initial target market (US, North America, Global)
+
+**Stage:**
+- What stage is the company? (pre-launch, seed, Series A)
+
+## Step 2: Bottom-Up Analysis
+
+### For B2B/SaaS
+
+1. Define customer segments (company size, industry, use case)
+2. Estimate number of companies in each segment
+3. Determine average contract value (ACV) per segment
+4. Calculate TAM: Σ (Segment Size × ACV)
+
+### For Consumer/Marketplace
+
+1. Define target user demographics
+2. Estimate total addressable users
+3. Determine average revenue per user (ARPU)
+4. Calculate TAM: Total Users × ARPU × Frequency
+
+### For Transactions/E-commerce
+
+1. Estimate total transaction volume (GMV)
+2. Determine take rate or margin
+3. Calculate TAM: Total GMV × Take Rate
+
+## Step 3: Data Sources
+
+Recommended sources:
+- Government data (Census, BLS)
+- Industry reports (Gartner, Forrester, Statista)
+- Public company filings (10-K reports)
+- Trade associations
+- Academic research
+
+**Always cite sources with URLs and publication dates.**
+
+## Step 4: Top-Down Validation
+
+1. Find total market category size from research
+2. Apply geographic filters
+3. Apply segment/product filters
+4. Compare to bottom-up TAM (should be within 30%)
+
+If variance > 30%, investigate and explain differences.
+
+## Step 5: Calculate SAM
+
+Apply realistic filters to narrow TAM:
+
+- **Geographic:** Regions actually serviceable
+- **Product Capability:** Features needed to serve
+- **Market Readiness:** Customers ready to adopt
+- **Addressable Switching:** Can reach and convert
+
+Formula:
+```
+SAM = TAM × Geographic % × Product Fit % × Market Readiness %
+```
+
+## Step 6: Estimate SOM
+
+Calculate realistic obtainable market share:
+
+**Conservative Approach (Recommended):**
+- Year 3: 2-3% of SAM
+- Year 5: 4-6% of SAM
+
+**Consider:**
+- Competitive intensity
+- Available resources (funding, team)
+- Go-to-market effectiveness
+- Differentiation strength
+
+## Report Structure
+
+### Section 1: Executive Summary
+- Market opportunity in one paragraph
+- TAM/SAM/SOM headline numbers
+
+### Section 2: Market Definition
+- Problem being solved
+- Target customer profile
+- Geographic scope
+
+### Section 3: Bottom-Up Analysis
+- Customer segment breakdown
+- Segment sizing with sources
+- TAM calculation with formula
+
+### Section 4: Top-Down Validation
+- Industry category and size
+- Validated TAM
+- Comparison to bottom-up
+
+### Section 5: SAM Calculation
+- Filters applied with rationale
+- SAM formula and result
+
+### Section 6: SOM Projection
+- Market share assumptions
+- Year 3 and Year 5 estimates
+- Revenue projections
+
+### Section 7: Market Growth
+- Industry growth rate (CAGR)
+- Key growth drivers
+
+### Section 8: Validation
+- Public company comparisons
+- Competitive context
+
+## Best Practices
+
+**Do:**
+- Start with bottom-up (most credible)
+- Always triangulate with top-down
+- Cite all data sources
+- Be conservative on SOM
+- Compare to public company benchmarks
+
+**Don't:**
+- Rely solely on top-down
+- Cherry-pick optimistic data
+- Claim >10% SOM without strong justification
+- Skip validation steps

package/.agent/skills/riligar-dev-clean-code/SKILL.md

@@ -4,184 +4,132 @@ type: development
 description: Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments. CRITICAL skill that defines RiLiGar coding standards. Use when writing or reviewing any code.
 ---
 
-# Clean Code - Pragmatic AI Coding Standards (RiLiGar)
+# Clean Code - RiLiGar Standards
 
-> **CRITICAL SKILL** - Be **concise, direct, and solution-focused**. Follow the RiLiGar Tech Stack strictly.
+> **CRITICAL SKILL** - Be **concise, direct, and solution-focused**.
 
----
+## Rules Reference
 
-## Core Principles
+This skill builds on the foundational rules defined in `.agent/rules/`:
 
-| Principle     | Rule                                                       |
-| ------------- | ---------------------------------------------------------- |
-| **SRP**       | Single Responsibility - each function/class does ONE thing |
-| **DRY**       | Don't Repeat Yourself - extract duplicates, reuse          |
-| **KISS**      | Keep It Simple - simplest solution that works              |
-| **YAGNI**     | You Aren't Gonna Need It - don't build unused features     |
-| **Boy Scout** | Leave code cleaner than you found it                       |
+| Rule File | Content |
+| --- | --- |
+| [code-style.md](../../rules/code-style.md) | Prettier formatting (4 spaces, no semi, single quotes) |
+| [javascript-only.md](../../rules/javascript-only.md) | ES6+ only, no TypeScript |
+| [naming-conventions.md](../../rules/naming-conventions.md) | PascalCase, camelCase, SCREAMING_SNAKE |
+| [conventional-commits.md](../../rules/conventional-commits.md) | Commit message format |
+| [pr-guidelines.md](../../rules/pr-guidelines.md) | Pull request standards |
 
 ---
 
-## RiLiGar Formatting (Prettier)
-
-| Prop               | Value    |
-| ------------------ | -------- |
-| **Indent Size**    | 4 spaces |
-| **Semicolons**     | `false`  |
-| **Quotes**         | Single   |
-| **Print Width**    | 300      |
-| **Trailing Comma** | `es5`    |
+## Core Principles
 
-> 🔴 **Rule:** Never use TypeScript. Always use modern JavaScript (ES6+).
+| Principle | Rule |
+| --- | --- |
+| **SRP** | Single Responsibility - each function/class does ONE thing |
+| **DRY** | Don't Repeat Yourself - extract duplicates, reuse |
+| **KISS** | Keep It Simple - simplest solution that works |
+| **YAGNI** | You Aren't Gonna Need It - don't build unused features |
+| **Boy Scout** | Leave code cleaner than you found it |
 
 ---
 
-## Naming Rules
-
-| Element       | Convention                                            |
-| ------------- | ----------------------------------------------------- |
-| **Variables** | Reveal intent: `userCount` not `n`                    |
-| **Functions** | Verb + noun: `getUserById()` not `user()`             |
-| **Booleans**  | Question form: `isActive`, `hasPermission`, `canEdit` |
-| **Constants** | SCREAMING_SNAKE: `MAX_RETRY_COUNT`                    |
+## Function Rules
 
-> **Rule:** If you need a comment to explain a name, rename it.
+| Rule | Description |
+| --- | --- |
+| **Small** | Max 20 lines, ideally 5-10 |
+| **One Thing** | Does one thing, does it well |
+| **One Level** | One level of abstraction per function |
+| **Few Args** | Max 3 arguments, prefer 0-2 |
+| **No Side Effects** | Don't mutate inputs unexpectedly |
+| **Async/Await** | Prefer `async/await` over `.then()` chains |
 
 ---
 
-## Function Rules
+## Code Structure
 
-| Rule                | Description                                |
-| ------------------- | ------------------------------------------ |
-| **Small**           | Max 20 lines, ideally 5-10                 |
-| **One Thing**       | Does one thing, does it well               |
-| **One Level**       | One level of abstraction per function      |
-| **Few Args**        | Max 3 arguments, prefer 0-2                |
-| **No Side Effects** | Don't mutate inputs unexpectedly           |
-| **Async/Await**     | Prefer `async/await` over `.then()` chains |
+| Pattern | Apply |
+| --- | --- |
+| **Guard Clauses** | Early returns for edge cases |
+| **Flat > Nested** | Avoid deep nesting (max 2 levels) |
+| **Composition** | Small functions composed together |
+| **Colocation** | Keep related code close |
 
 ---
 
 ## Component & Framework Rules (React/Elysia)
 
-| Situation            | Action                                           |
-| -------------------- | ------------------------------------------------ |
-| **Complex Logic**    | Extract to a Custom Hook if logic > 15 lines     |
+| Situation | Action |
+| --- | --- |
+| **Complex Logic** | Extract to a Custom Hook if logic > 15 lines |
 | **State Management** | Use **Zustand** for global, `useState` for local |
-| **UI Components**    | **ALWAYS** use Mantine. No custom/raw CSS.       |
-| **API Endpoints**    | Extract complex handler logic to `services/`     |
-| **Early Returns**    | Use Guard Clauses to avoid deep nesting          |
-
----
-
-## Code Structure
-
-| Pattern           | Apply                             |
-| ----------------- | --------------------------------- |
-| **Guard Clauses** | Early returns for edge cases      |
-| **Flat > Nested** | Avoid deep nesting (max 2 levels) |
-| **Composition**   | Small functions composed together |
-| **Colocation**    | Keep related code close           |
+| **UI Components** | **ALWAYS** use Mantine. No custom/raw CSS. |
+| **API Endpoints** | Extract complex handler logic to `services/` |
+| **Early Returns** | Use Guard Clauses to avoid deep nesting |
 
 ---
 
 ## AI Coding Style
 
-| Situation             | Action                |
-| --------------------- | --------------------- |
-| User asks for feature | Write it directly     |
-| User reports bug      | Fix it, don't explain |
-| No clear requirement  | Ask, don't assume     |
+| Situation | Action |
+| --- | --- |
+| User asks for feature | Write it directly |
+| User reports bug | Fix it, don't explain |
+| No clear requirement | Ask, don't assume |
 
 ---
 
 ## Anti-Patterns (DON'T)
 
-| ❌ Pattern              | ✅ Fix                         |
-| ----------------------- | ------------------------------ |
-| Comment every line      | Delete obvious comments        |
-| Helper for one-liner    | Inline the code                |
-| Factory for 2 objects   | Direct instantiation           |
-| `utils.js` (1 function) | Put code where used            |
-| "First we import..."    | Just write code                |
-| Deep nesting            | Guard clauses                  |
-| Magic numbers           | Named constants                |
-| God functions           | Split by responsibility        |
-| TypeScript / `.ts`      | Use Vanilla JavaScript (`.js`) |
+| Pattern | Fix |
+| --- | --- |
+| Comment every line | Delete obvious comments |
+| Helper for one-liner | Inline the code |
+| Factory for 2 objects | Direct instantiation |
+| `utils.js` (1 function) | Put code where used |
+| "First we import..." | Just write code |
+| Deep nesting | Guard clauses |
+| Magic numbers | Named constants |
+| God functions | Split by responsibility |
 
 ---
 
-## 🔴 Before Editing ANY File (THINK FIRST!)
+## Before Editing ANY File
 
-**Before changing a file, ask yourself:**
+**Ask yourself:**
 
-| Question                        | Why                      |
-| ------------------------------- | ------------------------ |
-| **What imports this file?**     | They might break         |
-| **What does this file import?** | Interface changes        |
+| Question | Why |
+| --- | --- |
+| **What imports this file?** | They might break |
+| **What does this file import?** | Interface changes |
 | **Is this a shared component?** | Multiple places affected |
 
-**Quick Check:**
-
-```
-File to edit: user-service.js
-└── Who imports this? → user-controller.js
-└── Do they need changes too? → Check function signatures
-```
-
-> 🔴 **Rule:** Edit the file + all dependent files in the SAME task.
+> **Rule:** Edit the file + all dependent files in the SAME task.
 
 ---
 
-## Summary
-
-| Do                     | Don't                     |
-| ---------------------- | ------------------------- |
-| Write code directly    | Write tutorials           |
-| Let code self-document | Add obvious comments      |
-| Fix bugs immediately   | Explain the fix first     |
-| Inline small things    | Create unnecessary files  |
-| Name things clearly    | Use abbreviations         |
-| Keep functions small   | Write 100+ line functions |
+## Self-Check Before Completing (MANDATORY)
 
-> **Remember: The user wants working code, not a programming lesson.**
+| Check | Question |
+| --- | --- |
+| **Goal met?** | Did I do exactly what user asked? |
+| **Files edited?** | Did I modify all necessary files? |
+| **Code works?** | Did I test/verify the change? |
+| **No TypeScript?** | Verified no `.ts` or type syntax? |
+| **Formatting?** | 4 spaces, no semi, single quotes? |
 
 ---
 
-## 🔴 Self-Check Before Completing (MANDATORY)
-
-**Before saying "task complete", verify:**
-
-| Check                 | Question                          |
-| --------------------- | --------------------------------- |
-| ✅ **Goal met?**      | Did I do exactly what user asked? |
-| ✅ **Files edited?**  | Did I modify all necessary files? |
-| ✅ **Code works?**    | Did I test/verify the change?     |
-| ✅ **No TypeScript?** | Verified no `.ts` or type syntax? |
-| ✅ **Formatting?**    | 4 spaces, no semi, single quotes? |
-
----
-
-## Verification Scripts (MANDATORY)
-
-> 🔴 **CRITICAL:** Run only valid scripts found in `.agent/skills/*/scripts`.
-
-### Agent → Script Mapping
-
-| Agent                  | Script          | Command                                                                   |
-| ---------------------- | --------------- | ------------------------------------------------------------------------- |
-| **backend-specialist** | API Validator   | `python .agent/skills/riligar-dev-backend/scripts/api_validator.py .`     |
-| **database-architect** | Schema Validate | `python .agent/skills/riligar-dev-database/scripts/schema_validator.py .` |
-| **Any agent**          | Lint Check      | `bun x eslint .`                                                          |
-
----
-
-### 🔴 Script Output Handling (READ → SUMMARIZE → ASK)
-
-**When running a validation script, you MUST:**
+## Summary
 
-1.  **Run the script** and capture ALL output.
-2.  **Summarize results** (Errors, Warnings, Passes).
-3.  **Ask before fixing** any identified errors.
+| Do | Don't |
+| --- | --- |
+| Write code directly | Write tutorials |
+| Let code self-document | Add obvious comments |
+| Fix bugs immediately | Explain the fix first |
+| Inline small things | Create unnecessary files |
+| Name things clearly | Use abbreviations |
+| Keep functions small | Write 100+ line functions |
 
-> 🔴 **VIOLATION:** Auto-fixing without asking = Not allowed.
+> **Remember: The user wants working code, not a programming lesson.**

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@riligar/agents-kit",
-    "version": "1.10.0",
+    "version": "1.11.0",
     "publishConfig": {
         "access": "public"
     },