@cubis/foundry 0.3.11 → 0.3.12

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/windsurf/skills/sql-pro/references/window-functions.md

@@ -1,328 +0,0 @@
-# Window Functions
-
-## Ranking Functions
-
-```sql
--- ROW_NUMBER: Sequential numbering within partition
-SELECT
-    customer_id,
-    order_date,
-    total,
-    ROW_NUMBER() OVER (PARTITION BY customer_id ORDER BY order_date DESC) as row_num
-FROM orders;
-
--- Get most recent order per customer
-SELECT *
-FROM (
-    SELECT
-        customer_id,
-        order_id,
-        order_date,
-        total,
-        ROW_NUMBER() OVER (PARTITION BY customer_id ORDER BY order_date DESC) as rn
-    FROM orders
-) ranked
-WHERE rn = 1;
-
--- RANK: Same values get same rank, gaps in sequence
-SELECT
-    student_id,
-    score,
-    RANK() OVER (ORDER BY score DESC) as rank,
-    DENSE_RANK() OVER (ORDER BY score DESC) as dense_rank,
-    ROW_NUMBER() OVER (ORDER BY score DESC) as row_num
-FROM exam_results;
-/*
-score=100: rank=1, dense_rank=1, row_num=1
-score=100: rank=1, dense_rank=1, row_num=2
-score=95:  rank=3, dense_rank=2, row_num=3
-*/
-
--- NTILE: Divide into N buckets
-SELECT
-    customer_id,
-    total_spent,
-    NTILE(4) OVER (ORDER BY total_spent DESC) as quartile
-FROM customer_lifetime_value;
-```
-
-## Aggregate Window Functions
-
-```sql
--- Running totals and cumulative sums
-SELECT
-    order_date,
-    daily_revenue,
-    SUM(daily_revenue) OVER (ORDER BY order_date) as cumulative_revenue,
-    AVG(daily_revenue) OVER (
-        ORDER BY order_date
-        ROWS BETWEEN 6 PRECEDING AND CURRENT ROW
-    ) as rolling_7day_avg
-FROM daily_sales;
-
--- Moving average with RANGE
-SELECT
-    sale_date,
-    amount,
-    AVG(amount) OVER (
-        ORDER BY sale_date
-        RANGE BETWEEN INTERVAL '7 days' PRECEDING AND CURRENT ROW
-    ) as avg_last_7_days
-FROM sales;
-
--- Partition-specific aggregates
-SELECT
-    product_id,
-    sale_date,
-    quantity,
-    SUM(quantity) OVER (PARTITION BY product_id ORDER BY sale_date) as cumulative_qty,
-    AVG(quantity) OVER (PARTITION BY product_id) as avg_qty_for_product,
-    quantity::FLOAT / SUM(quantity) OVER (PARTITION BY product_id) as pct_of_total
-FROM product_sales;
-```
-
-## LAG and LEAD Functions
-
-```sql
--- Compare with previous/next row
-SELECT
-    order_date,
-    total,
-    LAG(total) OVER (ORDER BY order_date) as previous_day_total,
-    LEAD(total) OVER (ORDER BY order_date) as next_day_total,
-    total - LAG(total) OVER (ORDER BY order_date) as day_over_day_change
-FROM daily_orders;
-
--- Find gaps in time series
-SELECT
-    event_date,
-    LAG(event_date) OVER (ORDER BY event_date) as prev_date,
-    event_date - LAG(event_date) OVER (ORDER BY event_date) as days_since_last
-FROM events
-WHERE event_date - LAG(event_date) OVER (ORDER BY event_date) > 7;
-
--- Session analysis with time gaps
-SELECT
-    user_id,
-    action_time,
-    LAG(action_time) OVER (PARTITION BY user_id ORDER BY action_time) as prev_action,
-    EXTRACT(EPOCH FROM (
-        action_time - LAG(action_time) OVER (PARTITION BY user_id ORDER BY action_time)
-    )) / 60 as minutes_since_last_action,
-    CASE
-        WHEN EXTRACT(EPOCH FROM (
-            action_time - LAG(action_time) OVER (PARTITION BY user_id ORDER BY action_time)
-        )) / 60 > 30 THEN 1
-        ELSE 0
-    END as new_session
-FROM user_actions;
-```
-
-## FIRST_VALUE and LAST_VALUE
-
-```sql
--- Compare each row to first/last in partition
-SELECT
-    product_id,
-    price_date,
-    price,
-    FIRST_VALUE(price) OVER (
-        PARTITION BY product_id
-        ORDER BY price_date
-        ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING
-    ) as initial_price,
-    LAST_VALUE(price) OVER (
-        PARTITION BY product_id
-        ORDER BY price_date
-        ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING
-    ) as current_price,
-    price - FIRST_VALUE(price) OVER (
-        PARTITION BY product_id
-        ORDER BY price_date
-        ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING
-    ) as price_change_from_start
-FROM product_price_history;
-
--- NTH_VALUE: Get specific positioned value
-SELECT
-    sale_date,
-    amount,
-    NTH_VALUE(amount, 2) OVER (
-        ORDER BY sale_date
-        ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING
-    ) as second_day_amount
-FROM daily_sales;
-```
-
-## Frame Specifications
-
-```sql
--- ROWS vs RANGE difference
-SELECT
-    order_date,
-    amount,
-    -- ROWS: Physical row offset
-    SUM(amount) OVER (
-        ORDER BY order_date
-        ROWS BETWEEN 2 PRECEDING AND 2 FOLLOWING
-    ) as sum_5_rows,
-    -- RANGE: Logical value range
-    SUM(amount) OVER (
-        ORDER BY order_date
-        RANGE BETWEEN INTERVAL '2 days' PRECEDING AND INTERVAL '2 days' FOLLOWING
-    ) as sum_5_day_range
-FROM orders;
-
--- Common frame patterns
-SELECT
-    sale_date,
-    revenue,
-    -- All preceding rows
-    SUM(revenue) OVER (
-        ORDER BY sale_date
-        ROWS UNBOUNDED PRECEDING
-    ) as running_total,
-    -- Last 3 rows including current
-    AVG(revenue) OVER (
-        ORDER BY sale_date
-        ROWS BETWEEN 2 PRECEDING AND CURRENT ROW
-    ) as ma_3,
-    -- Entire partition
-    SUM(revenue) OVER (
-        PARTITION BY EXTRACT(YEAR FROM sale_date)
-    ) as yearly_total,
-    -- Centered window
-    AVG(revenue) OVER (
-        ORDER BY sale_date
-        ROWS BETWEEN 3 PRECEDING AND 3 FOLLOWING
-    ) as centered_ma_7
-FROM sales;
-```
-
-## Advanced Analytics
-
-```sql
--- Percentile calculations
-SELECT
-    employee_id,
-    salary,
-    PERCENT_RANK() OVER (ORDER BY salary) as pct_rank,
-    CUME_DIST() OVER (ORDER BY salary) as cumulative_dist,
-    PERCENTILE_CONT(0.5) WITHIN GROUP (ORDER BY salary) OVER () as median_salary,
-    PERCENTILE_DISC(0.9) WITHIN GROUP (ORDER BY salary) OVER () as p90_salary
-FROM employees;
-
--- Cohort retention analysis
-WITH user_cohorts AS (
-    SELECT
-        user_id,
-        DATE_TRUNC('month', signup_date) as cohort_month,
-        DATE_TRUNC('month', activity_date) as activity_month
-    FROM user_activity
-),
-cohort_sizes AS (
-    SELECT
-        cohort_month,
-        COUNT(DISTINCT user_id) as cohort_size
-    FROM user_cohorts
-    GROUP BY cohort_month
-)
-SELECT
-    uc.cohort_month,
-    uc.activity_month,
-    EXTRACT(MONTH FROM AGE(uc.activity_month, uc.cohort_month)) as months_since_signup,
-    COUNT(DISTINCT uc.user_id) as active_users,
-    cs.cohort_size,
-    ROUND(100.0 * COUNT(DISTINCT uc.user_id) / cs.cohort_size, 2) as retention_pct
-FROM user_cohorts uc
-JOIN cohort_sizes cs ON uc.cohort_month = cs.cohort_month
-GROUP BY uc.cohort_month, uc.activity_month, cs.cohort_size
-ORDER BY uc.cohort_month, months_since_signup;
-
--- Time-series gap filling
-SELECT
-    date_series.date,
-    COALESCE(s.revenue, 0) as revenue,
-    AVG(s.revenue) OVER (
-        ORDER BY date_series.date
-        ROWS BETWEEN 6 PRECEDING AND CURRENT ROW
-    ) as ma_7day
-FROM generate_series(
-    '2024-01-01'::DATE,
-    '2024-12-31'::DATE,
-    '1 day'::INTERVAL
-) AS date_series(date)
-LEFT JOIN sales s ON date_series.date = s.sale_date;
-```
-
-## Conditional Aggregation with Windows
-
-```sql
--- Filter within window function
-SELECT
-    product_id,
-    sale_date,
-    quantity,
-    SUM(quantity) FILTER (WHERE quantity > 10) OVER (
-        PARTITION BY product_id
-        ORDER BY sale_date
-    ) as cumulative_large_orders,
-    COUNT(*) FILTER (WHERE quantity > 100) OVER (
-        PARTITION BY product_id
-    ) as total_bulk_orders
-FROM sales;
-
--- Multiple conditions
-SELECT
-    customer_id,
-    order_date,
-    total,
-    COUNT(*) FILTER (WHERE total > 1000) OVER (
-        PARTITION BY customer_id
-    ) as high_value_order_count,
-    AVG(total) FILTER (WHERE total < 100) OVER (
-        PARTITION BY customer_id
-    ) as avg_small_order_value
-FROM orders;
-```
-
-## Performance Considerations
-
-```sql
--- Avoid multiple window passes - combine into one
--- Bad: Multiple scans
-SELECT
-    product_id,
-    (SELECT AVG(price) FROM products) as avg_price,
-    (SELECT MAX(price) FROM products) as max_price
-FROM products;
-
--- Good: Single window pass
-SELECT DISTINCT
-    AVG(price) OVER () as avg_price,
-    MAX(price) OVER () as max_price
-FROM products;
-
--- Materialize expensive windows
-CREATE MATERIALIZED VIEW product_rankings AS
-SELECT
-    product_id,
-    category,
-    sales_count,
-    RANK() OVER (PARTITION BY category ORDER BY sales_count DESC) as category_rank,
-    PERCENT_RANK() OVER (ORDER BY sales_count DESC) as overall_percentile
-FROM product_sales_summary;
-
-CREATE INDEX idx_product_rankings_category ON product_rankings(category, category_rank);
-```
-
-## Common Patterns
-
-1. **Top N per Group**: Use ROW_NUMBER() with WHERE rn <= N
-2. **Running Totals**: SUM() OVER (ORDER BY date)
-3. **Moving Averages**: AVG() with ROWS BETWEEN N PRECEDING
-4. **Session Analysis**: LAG() to detect time gaps
-5. **Deduplication**: ROW_NUMBER() OVER (PARTITION BY key ORDER BY priority) WHERE rn = 1
-6. **Percentiles**: PERCENT_RANK() or PERCENTILE_CONT()
-7. **Year-over-Year**: LAG(value, 12) OVER (ORDER BY month)
-8. **Cohort Analysis**: PARTITION BY cohort_date, aggregate over activity periods

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/windsurf/skills/supabase-postgres-best-practices/AGENTS.md

@@ -1,90 +0,0 @@
-# supabase-postgres-best-practices
-
-> **Note:** `CLAUDE.md` is a symlink to this file.
-
-## Overview
-
-Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
-
-## Structure
-
-```
-supabase-postgres-best-practices/
-  SKILL.md       # Main skill file - read this first
-  AGENTS.md      # This navigation guide
-  CLAUDE.md      # Symlink to AGENTS.md
-  references/    # Detailed reference files
-```
-
-## Usage
-
-1. Read `SKILL.md` for the main skill instructions
-2. Browse `references/` for detailed documentation on specific topics
-3. Reference files are loaded on-demand - read only what you need
-
-## Reference Categories
-
-| Priority | Category | Impact | Prefix |
-|----------|----------|--------|--------|
-| 1 | Query Performance | CRITICAL | `query-` |
-| 2 | Connection Management | CRITICAL | `conn-` |
-| 3 | Security & RLS | CRITICAL | `security-` |
-| 4 | Schema Design | HIGH | `schema-` |
-| 5 | Concurrency & Locking | MEDIUM-HIGH | `lock-` |
-| 6 | Data Access Patterns | MEDIUM | `data-` |
-| 7 | Monitoring & Diagnostics | LOW-MEDIUM | `monitor-` |
-| 8 | Advanced Features | LOW | `advanced-` |
-
-Reference files are named `{prefix}-{topic}.md` (e.g., `query-missing-indexes.md`).
-
-## Available References
-
-**Advanced Features** (`advanced-`):
-- `references/advanced-full-text-search.md`
-- `references/advanced-jsonb-indexing.md`
-
-**Connection Management** (`conn-`):
-- `references/conn-idle-timeout.md`
-- `references/conn-limits.md`
-- `references/conn-pooling.md`
-- `references/conn-prepared-statements.md`
-
-**Data Access Patterns** (`data-`):
-- `references/data-batch-inserts.md`
-- `references/data-n-plus-one.md`
-- `references/data-pagination.md`
-- `references/data-upsert.md`
-
-**Concurrency & Locking** (`lock-`):
-- `references/lock-advisory.md`
-- `references/lock-deadlock-prevention.md`
-- `references/lock-short-transactions.md`
-- `references/lock-skip-locked.md`
-
-**Monitoring & Diagnostics** (`monitor-`):
-- `references/monitor-explain-analyze.md`
-- `references/monitor-pg-stat-statements.md`
-- `references/monitor-vacuum-analyze.md`
-
-**Query Performance** (`query-`):
-- `references/query-composite-indexes.md`
-- `references/query-covering-indexes.md`
-- `references/query-index-types.md`
-- `references/query-missing-indexes.md`
-- `references/query-partial-indexes.md`
-
-**Schema Design** (`schema-`):
-- `references/schema-data-types.md`
-- `references/schema-foreign-key-indexes.md`
-- `references/schema-lowercase-identifiers.md`
-- `references/schema-partitioning.md`
-- `references/schema-primary-keys.md`
-
-**Security & RLS** (`security-`):
-- `references/security-privileges.md`
-- `references/security-rls-basics.md`
-- `references/security-rls-performance.md`
-
----
-
-*30 reference files across 8 categories*

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/windsurf/skills/supabase-postgres-best-practices/README.md

@@ -1,116 +0,0 @@
-# Supabase Postgres Best Practices - Contributor Guide
-
-This skill contains Postgres performance optimization references optimized for
-AI agents and LLMs. It follows the [Agent Skills Open Standard](https://agentskills.io/).
-
-## Quick Start
-
-```bash
-# From repository root
-npm install
-
-# Validate existing references
-npm run validate
-
-# Build AGENTS.md
-npm run build
-```
-
-## Creating a New Reference
-
-1. **Choose a section prefix** based on the category:
-   - `query-` Query Performance (CRITICAL)
-   - `conn-` Connection Management (CRITICAL)
-   - `security-` Security & RLS (CRITICAL)
-   - `schema-` Schema Design (HIGH)
-   - `lock-` Concurrency & Locking (MEDIUM-HIGH)
-   - `data-` Data Access Patterns (MEDIUM)
-   - `monitor-` Monitoring & Diagnostics (LOW-MEDIUM)
-   - `advanced-` Advanced Features (LOW)
-
-2. **Copy the template**:
-   ```bash
-   cp references/_template.md references/query-your-reference-name.md
-   ```
-
-3. **Fill in the content** following the template structure
-
-4. **Validate and build**:
-   ```bash
-   npm run validate
-   npm run build
-   ```
-
-5. **Review** the generated `AGENTS.md`
-
-## Skill Structure
-
-```
-skills/supabase-postgres-best-practices/
-├── SKILL.md           # Agent-facing skill manifest (Agent Skills spec)
-├── AGENTS.md          # [GENERATED] Compiled references document
-├── README.md          # This file
-└── references/
-    ├── _template.md      # Reference template
-    ├── _sections.md      # Section definitions
-    ├── _contributing.md  # Writing guidelines
-    └── *.md              # Individual references
-
-packages/skills-build/
-├── src/               # Generic build system source
-└── package.json       # NPM scripts
-```
-
-## Reference File Structure
-
-See `references/_template.md` for the complete template. Key elements:
-
-````markdown
----
-title: Clear, Action-Oriented Title
-impact: CRITICAL|HIGH|MEDIUM-HIGH|MEDIUM|LOW-MEDIUM|LOW
-impactDescription: Quantified benefit (e.g., "10-100x faster")
-tags: relevant, keywords
----
-
-## [Title]
-
-[1-2 sentence explanation]
-
-**Incorrect (description):**
-
-```sql
--- Comment explaining what's wrong
-[Bad SQL example]
-```
-````
-
-**Correct (description):**
-
-```sql
--- Comment explaining why this is better
-[Good SQL example]
-```
-
-```
-## Writing Guidelines
-
-See `references/_contributing.md` for detailed guidelines. Key principles:
-
-1. **Show concrete transformations** - "Change X to Y", not abstract advice
-2. **Error-first structure** - Show the problem before the solution
-3. **Quantify impact** - Include specific metrics (10x faster, 50% smaller)
-4. **Self-contained examples** - Complete, runnable SQL
-5. **Semantic naming** - Use meaningful names (users, email), not (table1, col1)
-
-## Impact Levels
-
-| Level | Improvement | Examples |
-|-------|-------------|----------|
-| CRITICAL | 10-100x | Missing indexes, connection exhaustion |
-| HIGH | 5-20x | Wrong index types, poor partitioning |
-| MEDIUM-HIGH | 2-5x | N+1 queries, RLS optimization |
-| MEDIUM | 1.5-3x | Redundant indexes, stale statistics |
-| LOW-MEDIUM | 1.2-2x | VACUUM tuning, config tweaks |
-| LOW | Incremental | Advanced patterns, edge cases |
-```

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/windsurf/skills/supabase-postgres-best-practices/SKILL.md

@@ -1,64 +0,0 @@
----
-name: supabase-postgres-best-practices
-description: "Supabase-specific Postgres best practices (RLS/auth patterns, connection pooling, managed Postgres constraints, and performance rules) for Supabase-hosted workloads."
-license: MIT
-metadata:
-  author: supabase
-  version: "1.1.0"
-  organization: Supabase
-  date: January 2026
-  abstract: Comprehensive Postgres performance optimization guide for developers using Supabase and Postgres. Contains performance rules across 8 categories, prioritized by impact from critical (query performance, connection management) to incremental (advanced features). Each rule includes detailed explanations, incorrect vs. correct SQL examples, query plan analysis, and specific performance metrics to guide automated optimization and code generation.
----
-
-# Supabase Postgres Best Practices
-
-Comprehensive performance optimization guide for Postgres, maintained by Supabase. Contains rules across 8 categories, prioritized by impact to guide automated query optimization and schema design.
-
-## When to Apply
-
-Reference these guidelines when:
-- Writing SQL queries or designing schemas
-- Implementing indexes or query optimization
-- Reviewing database performance issues
-- Configuring connection pooling or scaling
-- Optimizing for Postgres-specific features
-- Working with Row-Level Security (RLS)
-
-## Rule Categories by Priority
-
-| Priority | Category | Impact | Prefix |
-|----------|----------|--------|--------|
-| 1 | Query Performance | CRITICAL | `query-` |
-| 2 | Connection Management | CRITICAL | `conn-` |
-| 3 | Security & RLS | CRITICAL | `security-` |
-| 4 | Schema Design | HIGH | `schema-` |
-| 5 | Concurrency & Locking | MEDIUM-HIGH | `lock-` |
-| 6 | Data Access Patterns | MEDIUM | `data-` |
-| 7 | Monitoring & Diagnostics | LOW-MEDIUM | `monitor-` |
-| 8 | Advanced Features | LOW | `advanced-` |
-
-## How to Use
-
-Read individual rule files for detailed explanations and SQL examples:
-
-```
-references/query-missing-indexes.md
-references/schema-partial-indexes.md
-references/_sections.md
-```
-
-Each rule file contains:
-- Brief explanation of why it matters
-- Incorrect SQL example with explanation
-- Correct SQL example with explanation
-- Optional EXPLAIN output or metrics
-- Additional context and references
-- Supabase-specific notes (when applicable)
-
-## References
-
-- https://www.postgresql.org/docs/current/
-- https://supabase.com/docs
-- https://wiki.postgresql.org/wiki/Performance_Optimization
-- https://supabase.com/docs/guides/database/overview
-- https://supabase.com/docs/guides/auth/row-level-security