agcel 1.0.1

package/skills/postgresql/SKILL.md

@@ -0,0 +1,73 @@
+# PostgreSQL
+
+## Description
+
+PostgreSQL database patterns including queries, indexing, and optimization.
+
+## When to Use
+
+- PostgreSQL database operations
+- SQL query optimization
+- Schema design
+
+---
+
+## Core Patterns
+
+### Basic Queries
+
+```sql
+-- Select with filtering
+SELECT id, name, email
+FROM users
+WHERE active = true
+ORDER BY created_at DESC
+LIMIT 20 OFFSET 0;
+
+-- Join
+SELECT u.*, COUNT(p.id) as post_count
+FROM users u
+LEFT JOIN posts p ON p.user_id = u.id
+GROUP BY u.id;
+```
+
+### Indexes
+
+```sql
+-- Single column index
+CREATE INDEX idx_users_email ON users(email);
+
+-- Composite index
+CREATE INDEX idx_posts_user_date ON posts(user_id, created_at DESC);
+
+-- Partial index
+CREATE INDEX idx_active_users ON users(email) WHERE active = true;
+```
+
+### Migrations
+
+```sql
+-- Add column with default
+ALTER TABLE users ADD COLUMN role VARCHAR(50) DEFAULT 'user';
+
+-- Add constraint
+ALTER TABLE users ADD CONSTRAINT unique_email UNIQUE (email);
+```
+
+## Best Practices
+
+1. Use indexes for filtered/sorted columns
+2. Use EXPLAIN ANALYZE for slow queries
+3. Avoid SELECT * in production
+4. Use transactions for multiple operations
+5. Use connection pooling
+
+## Common Pitfalls
+
+- **N+1 queries**: Use JOINs or batch loading
+- **Missing indexes**: Add indexes for WHERE/ORDER BY
+- **Large transactions**: Keep transactions short
+
+
+## Gap Analysis Rule
+Always identify gaps and suggest next steps to users. In case there is no gaps anymore, then AI should clearly state that there is no gap left.

package/skills/pricing-strategy/SKILL.md

@@ -0,0 +1,360 @@
+---
+name: pricing-strategy
+description: Design pricing, packaging, and monetization strategies based on value, customer willingness to pay, and growth objectives.
+---
+
+# Pricing Strategy
+
+You are an expert in pricing and monetization strategy. Your goal is to help design pricing that **captures value, supports growth, and aligns with customer willingness to pay**—without harming conversion, trust, or long-term retention.
+
+This skill covers **pricing research, value metrics, tier design, and pricing change strategy**.
+It does **not** implement pricing pages or experiments directly.
+
+---
+
+## 1. Required Context (Ask If Missing)
+
+### 1. Business Model
+
+* Product type (SaaS, marketplace, service, usage-based)
+* Current pricing (if any)
+* Target customer (SMB, mid-market, enterprise)
+* Go-to-market motion (self-serve, sales-led, hybrid)
+
+### 2. Market & Competition
+
+* Primary value delivered
+* Key alternatives customers compare against
+* Competitor pricing models
+* Differentiation vs. alternatives
+
+### 3. Current Performance (If Existing)
+
+* Conversion rate
+* ARPU / ARR
+* Churn and expansion
+* Qualitative pricing feedback
+
+### 4. Objectives
+
+* Growth vs. revenue vs. profitability
+* Move upmarket or downmarket
+* Planned pricing changes (if any)
+
+---
+
+## 2. Pricing Fundamentals
+
+### The Three Pricing Decisions
+
+Every pricing strategy must explicitly answer:
+
+1. **Packaging** – What is included in each tier?
+2. **Value Metric** – What customers pay for (users, usage, outcomes)?
+3. **Price Level** – How much each tier costs
+
+Failure in any one weakens the system.
+
+---
+
+## 3. Value-Based Pricing Framework
+
+Pricing should be anchored to **customer-perceived value**, not internal cost.
+
+```
+Customer perceived value
+───────────────────────────────
+Your price
+───────────────────────────────
+Next best alternative
+───────────────────────────────
+Your cost to serve
+```
+
+**Rules**
+
+* Price above the next best alternative
+* Leave customer surplus (value they keep)
+* Cost is a floor, not a pricing basis
+
+---
+
+## 4. Pricing Research Methods
+
+### Van Westendorp (Price Sensitivity Meter)
+
+Used to identify acceptable price ranges.
+
+**Questions**
+
+* Too expensive
+* Too cheap
+* Expensive but acceptable
+* Cheap / good value
+
+**Key Outputs**
+
+* PMC (too cheap threshold)
+* PME (too expensive threshold)
+* OPP (optimal price point)
+* IDP (indifference price point)
+
+**Use Case**
+
+* Early pricing
+* Price increase validation
+* Segment comparison
+
+---
+
+### Feature Value Research (MaxDiff / Conjoint)
+
+Used to inform **packaging**, not price levels.
+
+**Insights Produced**
+
+* Table-stakes features
+* Differentiators
+* Premium-only features
+* Low-value candidates to remove
+
+---
+
+### Willingness-to-Pay Testing
+
+| Method        | Use Case                    |
+| ------------- | --------------------------- |
+| Direct WTP    | Directional only            |
+| Gabor-Granger | Demand curve                |
+| Conjoint      | Feature + price sensitivity |
+
+---
+
+## 5. Value Metrics
+
+### Definition
+
+The value metric is **what scales price with customer value**.
+
+### Good Value Metrics
+
+* Align with value delivered
+* Scale with customer success
+* Easy to understand
+* Difficult to game
+
+### Common Patterns
+
+| Metric             | Best For             |
+| ------------------ | -------------------- |
+| Per user           | Collaboration tools  |
+| Per usage          | APIs, infrastructure |
+| Per record/contact | CRMs, email          |
+| Flat fee           | Simple products      |
+| Revenue share      | Marketplaces         |
+
+### Validation Test
+
+> As customers get more value, do they naturally pay more?
+
+If not → metric is misaligned.
+
+---
+
+## 6. Tier Design
+
+### Number of Tiers
+
+| Count | When to Use                    |
+| ----- | ------------------------------ |
+| 2     | Simple segmentation            |
+| 3     | Default (Good / Better / Best) |
+| 4+    | Broad market, careful UX       |
+
+### Good / Better / Best
+
+**Good**
+
+* Entry point
+* Limited usage
+* Removes friction
+
+**Better (Anchor)**
+
+* Where most customers should land
+* Full core value
+* Best value-per-dollar
+
+**Best**
+
+* Power users / enterprise
+* Advanced controls, scale, support
+
+---
+
+### Differentiation Levers
+
+* Usage limits
+* Advanced features
+* Support level
+* Security & compliance
+* Customization / integrations
+
+---
+
+## 7. Persona-Based Packaging
+
+### Step 1: Define Personas
+
+Segment by:
+
+* Company size
+* Use case
+* Sophistication
+* Budget norms
+
+### Step 2: Map Value to Tiers
+
+Ensure each persona clearly maps to *one* tier.
+
+### Step 3: Price to Segment WTP
+
+Avoid “one price fits all” across fundamentally different buyers.
+
+---
+
+## 8. Freemium vs. Free Trial
+
+### Freemium Works When
+
+* Large market
+* Viral or network effects
+* Clear upgrade trigger
+* Low marginal cost
+
+### Free Trial Works When
+
+* Value requires setup
+* Higher price points
+* B2B evaluation cycles
+* Sticky post-activation usage
+
+### Hybrid Models
+
+* Reverse trials
+* Feature-limited free + premium trial
+
+---
+
+## 9. Price Increases
+
+### Signals It’s Time
+
+* Very high conversion
+* Low churn
+* Customers under-paying relative to value
+* Market price movement
+
+### Increase Strategies
+
+1. New customers only
+2. Delayed increase for existing
+3. Value-tied increase
+4. Full plan restructure
+
+---
+
+## 10. Pricing Page Alignment (Strategy Only)
+
+This skill defines **what** pricing should be.
+Execution belongs to **page-cro**.
+
+Strategic requirements:
+
+* Clear recommended tier
+* Transparent differentiation
+* Annual discount logic
+* Enterprise escape hatch
+
+---
+
+## 11. Price Testing (Safe Methods)
+
+Preferred:
+
+* New-customer pricing
+* Sales-led experimentation
+* Geographic tests
+* Packaging tests
+
+Avoid:
+
+* Blind A/B price tests on same page
+* Surprise customer discovery
+
+---
+
+## 12. Enterprise Pricing
+
+### When to Introduce
+
+* Deals > $10k ARR
+* Custom contracts
+* Security/compliance needs
+* Sales involvement required
+
+### Common Structures
+
+* Volume-discounted per seat
+* Platform fee + usage
+* Outcome-based pricing
+
+---
+
+## 13. Output Expectations
+
+This skill produces:
+
+### Pricing Strategy Document
+
+* Target personas
+* Value metric selection
+* Tier structure
+* Price rationale
+* Research inputs
+* Risks & tradeoffs
+
+### Change Recommendation (If Applicable)
+
+* Who is affected
+* Expected impact
+* Rollout plan
+* Measurement plan
+
+---
+
+## 14. Validation Checklist
+
+* [ ] Clear value metric
+* [ ] Distinct tier personas
+* [ ] Research-backed price range
+* [ ] Conversion-safe entry tier
+* [ ] Expansion path exists
+* [ ] Enterprise handled explicitly
+
+---
+Related Skills
+
+page-cro – Pricing page conversion
+
+copywriting – Pricing copy
+
+analytics-tracking – Measure impact
+
+ab-test-setup – Safe experimentation
+
+marketing-psychology – Behavioral pricing effects
+
+
+## Gap Analysis Rule
+Always identify gaps and suggest next steps to users. In case there is no gaps anymore, then AI should clearly state that there is no gap left.

package/skills/product-manager/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: product-manager
+description: Define product vision, user stories, acceptance criteria, and roadmap planning
+---
+
+# Product Manager
+
+## Overview
+
+Your role is to bridge the gap between business goals and technical implementation. You focus on the "Why" and "What" before the "How".
+
+## When to Use This Skill
+
+- Clarifying vague feature requests
+- Writing User Stories and Acceptance Criteria
+- Prioritizing features (MoSCoW method)
+- Defining the MVP (Minimum Viable Product)
+- Breaking down large epics into manageable tasks
+
+## Core Responsibilities
+
+1.  **Requirement Elicitation**: Ask probing questions to understand the true user need.
+2.  **User Story Creation**: Format: "As a [user], I want to [action], so that [benefit]".
+3.  **Acceptance Criteria**: Define clear, testable conditions for "done".
+4.  **Scope Management**: Prevent scope creep by clearly defining what is out of scope.
+
+## Deliverables
+
+### Product Requirements Document (PRD) Structure
+- **Problem Statement**: What are we solving?
+- **Target Audience**: Who are we solving it for?
+- **Goals & Non-Goals**: Success metrics.
+- **User Stories**: Detailed functional requirements.
+- **UI/UX Guidelines**: High-level flow descriptions.
+
+### Example User Story
+**Title**: User Login
+**As a**: Registered User
+**I want to**: Log in with my email and password
+**So that**: I can access my personalized dashboard
+
+**Acceptance Criteria**:
+- [ ] User can enter email and password.
+- [ ] System validates credentials against database.
+- [ ] Successful login redirects to Dashboard.
+- [ ] Invalid login shows "Invalid credentials" error.
+- [ ] "Forgot Password" link is visible.
+
+## Related Skills
+
+- [ui-ux-designer](../ui-ux-designer/SKILL.md): For wireframes and detailed designs.
+- [writing-plans](../writing-plans/SKILL.md): For creating implementation checklists.
+- [brainstorming](../brainstorming/SKILL.md): For ideation sessions.
+
+
+## Gap Analysis Rule
+Always identify gaps and suggest next steps to users. In case there is no gaps anymore, then AI should clearly state that there is no gap left.