namnam-skills 1.0.3 → 1.0.4

package/src/templates/antigravity-skills/crewai/SKILL.md

@@ -0,0 +1,243 @@
+---
+name: crewai
+description: "Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies. Covers agent design with roles and goals, task definition, crew orchestration, process types (sequential, hierarchical, parallel), memory systems, and flows for complex workflows. Essential for building collaborative AI agent teams. Use when: crewai, multi-agent team, agent roles, crew of agents, role-based agents."
+source: vibeship-spawner-skills (Apache 2.0)
+---
+
+# CrewAI
+
+**Role**: CrewAI Multi-Agent Architect
+
+You are an expert in designing collaborative AI agent teams with CrewAI. You think
+in terms of roles, responsibilities, and delegation. You design clear agent personas
+with specific expertise, create well-defined tasks with expected outputs, and
+orchestrate crews for optimal collaboration. You know when to use sequential vs
+hierarchical processes.
+
+## Capabilities
+
+- Agent definitions (role, goal, backstory)
+- Task design and dependencies
+- Crew orchestration
+- Process types (sequential, hierarchical)
+- Memory configuration
+- Tool integration
+- Flows for complex workflows
+
+## Requirements
+
+- Python 3.10+
+- crewai package
+- LLM API access
+
+## Patterns
+
+### Basic Crew with YAML Config
+
+Define agents and tasks in YAML (recommended)
+
+**When to use**: Any CrewAI project
+
+```python
+# config/agents.yaml
+researcher:
+  role: "Senior Research Analyst"
+  goal: "Find comprehensive, accurate information on {topic}"
+  backstory: |
+    You are an expert researcher with years of experience
+    in gathering and analyzing information. You're known
+    for your thorough and accurate research.
+  tools:
+    - SerperDevTool
+    - WebsiteSearchTool
+  verbose: true
+
+writer:
+  role: "Content Writer"
+  goal: "Create engaging, well-structured content"
+  backstory: |
+    You are a skilled writer who transforms research
+    into compelling narratives. You focus on clarity
+    and engagement.
+  verbose: true
+
+# config/tasks.yaml
+research_task:
+  description: |
+    Research the topic: {topic}
+
+    Focus on:
+    1. Key facts and statistics
+    2. Recent developments
+    3. Expert opinions
+    4. Contrarian viewpoints
+
+    Be thorough and cite sources.
+  agent: researcher
+  expected_output: |
+    A comprehensive research report with:
+    - Executive summary
+    - Key findings (bulleted)
+    - Sources cited
+
+writing_task:
+  description: |
+    Using the research provided, write an article about {topic}.
+
+    Requirements:
+    - 800-1000 words
+    - Engaging introduction
+    - Clear structure with headers
+    - Actionable conclusion
+  agent: writer
+  expected_output: "A polished article ready for publication"
+  context:
+    - research_task  # Uses output from research
+
+# crew.py
+from crewai import Agent, Task, Crew, Process
+from crewai.project import CrewBase, agent, task, crew
+
+@CrewBase
+class ContentCrew:
+    agents_config = 'config/agents.yaml'
+    tasks_config = 'config/tasks.yaml'
+
+    @agent
+    def researcher(self) -> Agent:
+        return Agent(config=self.agents_config['researcher'])
+
+    @agent
+    def writer(self) -> Agent:
+        return Agent(config=self.agents_config['writer'])
+
+    @task
+    def research_task(self) -> Task:
+        return Task(config=self.tasks_config['research_task'])
+
+    @task
+    def writing_task(self) -> Task:
+        return Task(config
+```
+
+### Hierarchical Process
+
+Manager agent delegates to workers
+
+**When to use**: Complex tasks needing coordination
+
+```python
+from crewai import Crew, Process
+
+# Define specialized agents
+researcher = Agent(
+    role="Research Specialist",
+    goal="Find accurate information",
+    backstory="Expert researcher..."
+)
+
+analyst = Agent(
+    role="Data Analyst",
+    goal="Analyze and interpret data",
+    backstory="Expert analyst..."
+)
+
+writer = Agent(
+    role="Content Writer",
+    goal="Create engaging content",
+    backstory="Expert writer..."
+)
+
+# Hierarchical crew - manager coordinates
+crew = Crew(
+    agents=[researcher, analyst, writer],
+    tasks=[research_task, analysis_task, writing_task],
+    process=Process.hierarchical,
+    manager_llm=ChatOpenAI(model="gpt-4o"),  # Manager model
+    verbose=True
+)
+
+# Manager decides:
+# - Which agent handles which task
+# - When to delegate
+# - How to combine results
+
+result = crew.kickoff()
+```
+
+### Planning Feature
+
+Generate execution plan before running
+
+**When to use**: Complex workflows needing structure
+
+```python
+from crewai import Crew, Process
+
+# Enable planning
+crew = Crew(
+    agents=[researcher, writer, reviewer],
+    tasks=[research, write, review],
+    process=Process.sequential,
+    planning=True,  # Enable planning
+    planning_llm=ChatOpenAI(model="gpt-4o")  # Planner model
+)
+
+# With planning enabled:
+# 1. CrewAI generates step-by-step plan
+# 2. Plan is injected into each task
+# 3. Agents see overall structure
+# 4. More consistent results
+
+result = crew.kickoff()
+
+# Access the plan
+print(crew.plan)
+```
+
+## Anti-Patterns
+
+### ❌ Vague Agent Roles
+
+**Why bad**: Agent doesn't know its specialty.
+Overlapping responsibilities.
+Poor task delegation.
+
+**Instead**: Be specific:
+- "Senior React Developer" not "Developer"
+- "Financial Analyst specializing in crypto" not "Analyst"
+Include specific skills in backstory.
+
+### ❌ Missing Expected Outputs
+
+**Why bad**: Agent doesn't know done criteria.
+Inconsistent outputs.
+Hard to chain tasks.
+
+**Instead**: Always specify expected_output:
+expected_output: |
+  A JSON object with:
+  - summary: string (100 words max)
+  - key_points: list of strings
+  - confidence: float 0-1
+
+### ❌ Too Many Agents
+
+**Why bad**: Coordination overhead.
+Inconsistent communication.
+Slower execution.
+
+**Instead**: 3-5 agents with clear roles.
+One agent can handle multiple related tasks.
+Use tools instead of agents for simple actions.
+
+## Limitations
+
+- Python-only
+- Best for structured workflows
+- Can be verbose for simple cases
+- Flows are newer feature
+
+## Related Skills
+
+Works well with: `langgraph`, `autonomous-agents`, `langfuse`, `structured-output`

package/src/templates/antigravity-skills/database-design/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: database-design
+description: Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
+allowed-tools: Read, Write, Edit, Glob, Grep
+---
+
+# Database Design
+
+> **Learn to THINK, not copy SQL patterns.**
+
+## 🎯 Selective Reading Rule
+
+**Read ONLY files relevant to the request!** Check the content map, find what you need.
+
+| File | Description | When to Read |
+|------|-------------|--------------|
+| `database-selection.md` | PostgreSQL vs Neon vs Turso vs SQLite | Choosing database |
+| `orm-selection.md` | Drizzle vs Prisma vs Kysely | Choosing ORM |
+| `schema-design.md` | Normalization, PKs, relationships | Designing schema |
+| `indexing.md` | Index types, composite indexes | Performance tuning |
+| `optimization.md` | N+1, EXPLAIN ANALYZE | Query optimization |
+| `migrations.md` | Safe migrations, serverless DBs | Schema changes |
+
+---
+
+## ⚠️ Core Principle
+
+- ASK user for database preferences when unclear
+- Choose database/ORM based on CONTEXT
+- Don't default to PostgreSQL for everything
+
+---
+
+## Decision Checklist
+
+Before designing schema:
+
+- [ ] Asked user about database preference?
+- [ ] Chosen database for THIS context?
+- [ ] Considered deployment environment?
+- [ ] Planned index strategy?
+- [ ] Defined relationship types?
+
+---
+
+## Anti-Patterns
+
+❌ Default to PostgreSQL for simple apps (SQLite may suffice)
+❌ Skip indexing
+❌ Use SELECT * in production
+❌ Store JSON when structured data is better
+❌ Ignore N+1 queries

package/src/templates/antigravity-skills/database-design/database-selection.md

@@ -0,0 +1,43 @@
+# Database Selection (2025)
+
+> Choose database based on context, not default.
+
+## Decision Tree
+
+```
+What are your requirements?
+│
+├── Full relational features needed
+│   ├── Self-hosted → PostgreSQL
+│   └── Serverless → Neon, Supabase
+│
+├── Edge deployment / Ultra-low latency
+│   └── Turso (edge SQLite)
+│
+├── AI / Vector search
+│   └── PostgreSQL + pgvector
+│
+├── Simple / Embedded / Local
+│   └── SQLite
+│
+└── Global distribution
+    └── PlanetScale, CockroachDB, Turso
+```
+
+## Comparison
+
+| Database | Best For | Trade-offs |
+|----------|----------|------------|
+| **PostgreSQL** | Full features, complex queries | Needs hosting |
+| **Neon** | Serverless PG, branching | PG complexity |
+| **Turso** | Edge, low latency | SQLite limitations |
+| **SQLite** | Simple, embedded, local | Single-writer |
+| **PlanetScale** | MySQL, global scale | No foreign keys |
+
+## Questions to Ask
+
+1. What's the deployment environment?
+2. How complex are the queries?
+3. Is edge/serverless important?
+4. Vector search needed?
+5. Global distribution required?

package/src/templates/antigravity-skills/database-design/indexing.md

@@ -0,0 +1,39 @@
+# Indexing Principles
+
+> When and how to create indexes effectively.
+
+## When to Create Indexes
+
+```
+Index these:
+├── Columns in WHERE clauses
+├── Columns in JOIN conditions
+├── Columns in ORDER BY
+├── Foreign key columns
+└── Unique constraints
+
+Don't over-index:
+├── Write-heavy tables (slower inserts)
+├── Low-cardinality columns
+├── Columns rarely queried
+```
+
+## Index Type Selection
+
+| Type | Use For |
+|------|---------|
+| **B-tree** | General purpose, equality & range |
+| **Hash** | Equality only, faster |
+| **GIN** | JSONB, arrays, full-text |
+| **GiST** | Geometric, range types |
+| **HNSW/IVFFlat** | Vector similarity (pgvector) |
+
+## Composite Index Principles
+
+```
+Order matters for composite indexes:
+├── Equality columns first
+├── Range columns last
+├── Most selective first
+└── Match query pattern
+```

package/src/templates/antigravity-skills/database-design/migrations.md

@@ -0,0 +1,48 @@
+# Migration Principles
+
+> Safe migration strategy for zero-downtime changes.
+
+## Safe Migration Strategy
+
+```
+For zero-downtime changes:
+│
+├── Adding column
+│   └── Add as nullable → backfill → add NOT NULL
+│
+├── Removing column
+│   └── Stop using → deploy → remove column
+│
+├── Adding index
+│   └── CREATE INDEX CONCURRENTLY (non-blocking)
+│
+└── Renaming column
+    └── Add new → migrate data → deploy → drop old
+```
+
+## Migration Philosophy
+
+- Never make breaking changes in one step
+- Test migrations on data copy first
+- Have rollback plan
+- Run in transaction when possible
+
+## Serverless Databases
+
+### Neon (Serverless PostgreSQL)
+
+| Feature | Benefit |
+|---------|---------|
+| Scale to zero | Cost savings |
+| Instant branching | Dev/preview |
+| Full PostgreSQL | Compatibility |
+| Autoscaling | Traffic handling |
+
+### Turso (Edge SQLite)
+
+| Feature | Benefit |
+|---------|---------|
+| Edge locations | Ultra-low latency |
+| SQLite compatible | Simple |
+| Generous free tier | Cost |
+| Global distribution | Performance |

package/src/templates/antigravity-skills/database-design/optimization.md

@@ -0,0 +1,36 @@
+# Query Optimization
+
+> N+1 problem, EXPLAIN ANALYZE, optimization priorities.
+
+## N+1 Problem
+
+```
+What is N+1?
+├── 1 query to get parent records
+├── N queries to get related records
+└── Very slow!
+
+Solutions:
+├── JOIN → Single query with all data
+├── Eager loading → ORM handles JOIN
+├── DataLoader → Batch and cache (GraphQL)
+└── Subquery → Fetch related in one query
+```
+
+## Query Analysis Mindset
+
+```
+Before optimizing:
+├── EXPLAIN ANALYZE the query
+├── Look for Seq Scan (full table scan)
+├── Check actual vs estimated rows
+└── Identify missing indexes
+```
+
+## Optimization Priorities
+
+1. **Add missing indexes** (most common issue)
+2. **Select only needed columns** (not SELECT *)
+3. **Use proper JOINs** (avoid subqueries when possible)
+4. **Limit early** (pagination at database level)
+5. **Cache** (when appropriate)

package/src/templates/antigravity-skills/database-design/orm-selection.md

@@ -0,0 +1,30 @@
+# ORM Selection (2025)
+
+> Choose ORM based on deployment and DX needs.
+
+## Decision Tree
+
+```
+What's the context?
+│
+├── Edge deployment / Bundle size matters
+│   └── Drizzle (smallest, SQL-like)
+│
+├── Best DX / Schema-first
+│   └── Prisma (migrations, studio)
+│
+├── Maximum control
+│   └── Raw SQL with query builder
+│
+└── Python ecosystem
+    └── SQLAlchemy 2.0 (async support)
+```
+
+## Comparison
+
+| ORM | Best For | Trade-offs |
+|-----|----------|------------|
+| **Drizzle** | Edge, TypeScript | Newer, less examples |
+| **Prisma** | DX, schema management | Heavier, not edge-ready |
+| **Kysely** | Type-safe SQL builder | Manual migrations |
+| **Raw SQL** | Complex queries, control | Manual type safety |

package/src/templates/antigravity-skills/database-design/schema-design.md

@@ -0,0 +1,56 @@
+# Schema Design Principles
+
+> Normalization, primary keys, timestamps, relationships.
+
+## Normalization Decision
+
+```
+When to normalize (separate tables):
+├── Data is repeated across rows
+├── Updates would need multiple changes
+├── Relationships are clear
+└── Query patterns benefit
+
+When to denormalize (embed/duplicate):
+├── Read performance critical
+├── Data rarely changes
+├── Always fetched together
+└── Simpler queries needed
+```
+
+## Primary Key Selection
+
+| Type | Use When |
+|------|----------|
+| **UUID** | Distributed systems, security |
+| **ULID** | UUID + sortable by time |
+| **Auto-increment** | Simple apps, single database |
+| **Natural key** | Rarely (business meaning) |
+
+## Timestamp Strategy
+
+```
+For every table:
+├── created_at → When created
+├── updated_at → Last modified
+└── deleted_at → Soft delete (if needed)
+
+Use TIMESTAMPTZ (with timezone) not TIMESTAMP
+```
+
+## Relationship Types
+
+| Type | When | Implementation |
+|------|------|----------------|
+| **One-to-One** | Extension data | Separate table with FK |
+| **One-to-Many** | Parent-children | FK on child table |
+| **Many-to-Many** | Both sides have many | Junction table |
+
+## Foreign Key ON DELETE
+
+```
+├── CASCADE → Delete children with parent
+├── SET NULL → Children become orphans
+├── RESTRICT → Prevent delete if children exist
+└── SET DEFAULT → Children get default value
+```