@cubis/foundry 0.3.11 → 0.3.13

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/supabase-postgres-best-practices/references/schema-data-types.md

@@ -1,46 +0,0 @@
----
-title: Choose Appropriate Data Types
-impact: HIGH
-impactDescription: 50% storage reduction, faster comparisons
-tags: data-types, schema, storage, performance
----
-
-## Choose Appropriate Data Types
-
-Using the right data types reduces storage, improves query performance, and prevents bugs.
-
-**Incorrect (wrong data types):**
-
-```sql
-create table users (
-  id int,                    -- Will overflow at 2.1 billion
-  email varchar(255),        -- Unnecessary length limit
-  created_at timestamp,      -- Missing timezone info
-  is_active varchar(5),      -- String for boolean
-  price varchar(20)          -- String for numeric
-);
-```
-
-**Correct (appropriate data types):**
-
-```sql
-create table users (
-  id bigint generated always as identity primary key,  -- 9 quintillion max
-  email text,                     -- No artificial limit, same performance as varchar
-  created_at timestamptz,         -- Always store timezone-aware timestamps
-  is_active boolean default true, -- 1 byte vs variable string length
-  price numeric(10,2)             -- Exact decimal arithmetic
-);
-```
-
-Key guidelines:
-
-```sql
--- IDs: use bigint, not int (future-proofing)
--- Strings: use text, not varchar(n) unless constraint needed
--- Time: use timestamptz, not timestamp
--- Money: use numeric, not float (precision matters)
--- Enums: use text with check constraint or create enum type
-```
-
-Reference: [Data Types](https://www.postgresql.org/docs/current/datatype.html)

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/supabase-postgres-best-practices/references/schema-foreign-key-indexes.md

@@ -1,59 +0,0 @@
----
-title: Index Foreign Key Columns
-impact: HIGH
-impactDescription: 10-100x faster JOINs and CASCADE operations
-tags: foreign-key, indexes, joins, schema
----
-
-## Index Foreign Key Columns
-
-Postgres does not automatically index foreign key columns. Missing indexes cause slow JOINs and CASCADE operations.
-
-**Incorrect (unindexed foreign key):**
-
-```sql
-create table orders (
-  id bigint generated always as identity primary key,
-  customer_id bigint references customers(id) on delete cascade,
-  total numeric(10,2)
-);
-
--- No index on customer_id!
--- JOINs and ON DELETE CASCADE both require full table scan
-select * from orders where customer_id = 123;  -- Seq Scan
-delete from customers where id = 123;          -- Locks table, scans all orders
-```
-
-**Correct (indexed foreign key):**
-
-```sql
-create table orders (
-  id bigint generated always as identity primary key,
-  customer_id bigint references customers(id) on delete cascade,
-  total numeric(10,2)
-);
-
--- Always index the FK column
-create index orders_customer_id_idx on orders (customer_id);
-
--- Now JOINs and cascades are fast
-select * from orders where customer_id = 123;  -- Index Scan
-delete from customers where id = 123;          -- Uses index, fast cascade
-```
-
-Find missing FK indexes:
-
-```sql
-select
-  conrelid::regclass as table_name,
-  a.attname as fk_column
-from pg_constraint c
-join pg_attribute a on a.attrelid = c.conrelid and a.attnum = any(c.conkey)
-where c.contype = 'f'
-  and not exists (
-    select 1 from pg_index i
-    where i.indrelid = c.conrelid and a.attnum = any(i.indkey)
-  );
-```
-
-Reference: [Foreign Keys](https://www.postgresql.org/docs/current/ddl-constraints.html#DDL-CONSTRAINTS-FK)

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/supabase-postgres-best-practices/references/schema-lowercase-identifiers.md

@@ -1,55 +0,0 @@
----
-title: Use Lowercase Identifiers for Compatibility
-impact: MEDIUM
-impactDescription: Avoid case-sensitivity bugs with tools, ORMs, and AI assistants
-tags: naming, identifiers, case-sensitivity, schema, conventions
----
-
-## Use Lowercase Identifiers for Compatibility
-
-PostgreSQL folds unquoted identifiers to lowercase. Quoted mixed-case identifiers require quotes forever and cause issues with tools, ORMs, and AI assistants that may not recognize them.
-
-**Incorrect (mixed-case identifiers):**
-
-```sql
--- Quoted identifiers preserve case but require quotes everywhere
-CREATE TABLE "Users" (
-  "userId" bigint PRIMARY KEY,
-  "firstName" text,
-  "lastName" text
-);
-
--- Must always quote or queries fail
-SELECT "firstName" FROM "Users" WHERE "userId" = 1;
-
--- This fails - Users becomes users without quotes
-SELECT firstName FROM Users;
--- ERROR: relation "users" does not exist
-```
-
-**Correct (lowercase snake_case):**
-
-```sql
--- Unquoted lowercase identifiers are portable and tool-friendly
-CREATE TABLE users (
-  user_id bigint PRIMARY KEY,
-  first_name text,
-  last_name text
-);
-
--- Works without quotes, recognized by all tools
-SELECT first_name FROM users WHERE user_id = 1;
-```
-
-Common sources of mixed-case identifiers:
-
-```sql
--- ORMs often generate quoted camelCase - configure them to use snake_case
--- Migrations from other databases may preserve original casing
--- Some GUI tools quote identifiers by default - disable this
-
--- If stuck with mixed-case, create views as a compatibility layer
-CREATE VIEW users AS SELECT "userId" AS user_id, "firstName" AS first_name FROM "Users";
-```
-
-Reference: [Identifiers and Key Words](https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS)

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/supabase-postgres-best-practices/references/schema-partitioning.md

@@ -1,55 +0,0 @@
----
-title: Partition Large Tables for Better Performance
-impact: MEDIUM-HIGH
-impactDescription: 5-20x faster queries and maintenance on large tables
-tags: partitioning, large-tables, time-series, performance
----
-
-## Partition Large Tables for Better Performance
-
-Partitioning splits a large table into smaller pieces, improving query performance and maintenance operations.
-
-**Incorrect (single large table):**
-
-```sql
-create table events (
-  id bigint generated always as identity,
-  created_at timestamptz,
-  data jsonb
-);
-
--- 500M rows, queries scan everything
-select * from events where created_at > '2024-01-01';  -- Slow
-vacuum events;  -- Takes hours, locks table
-```
-
-**Correct (partitioned by time range):**
-
-```sql
-create table events (
-  id bigint generated always as identity,
-  created_at timestamptz not null,
-  data jsonb
-) partition by range (created_at);
-
--- Create partitions for each month
-create table events_2024_01 partition of events
-  for values from ('2024-01-01') to ('2024-02-01');
-
-create table events_2024_02 partition of events
-  for values from ('2024-02-01') to ('2024-03-01');
-
--- Queries only scan relevant partitions
-select * from events where created_at > '2024-01-15';  -- Only scans events_2024_01+
-
--- Drop old data instantly
-drop table events_2023_01;  -- Instant vs DELETE taking hours
-```
-
-When to partition:
-
-- Tables > 100M rows
-- Time-series data with date-based queries
-- Need to efficiently drop old data
-
-Reference: [Table Partitioning](https://www.postgresql.org/docs/current/ddl-partitioning.html)

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/supabase-postgres-best-practices/references/schema-primary-keys.md

@@ -1,61 +0,0 @@
----
-title: Select Optimal Primary Key Strategy
-impact: HIGH
-impactDescription: Better index locality, reduced fragmentation
-tags: primary-key, identity, uuid, serial, schema
----
-
-## Select Optimal Primary Key Strategy
-
-Primary key choice affects insert performance, index size, and replication
-efficiency.
-
-**Incorrect (problematic PK choices):**
-
-```sql
--- identity is the SQL-standard approach
-create table users (
-  id serial primary key  -- Works, but IDENTITY is recommended
-);
-
--- Random UUIDs (v4) cause index fragmentation
-create table orders (
-  id uuid default gen_random_uuid() primary key  -- UUIDv4 = random = scattered inserts
-);
-```
-
-**Correct (optimal PK strategies):**
-
-```sql
--- Use IDENTITY for sequential IDs (SQL-standard, best for most cases)
-create table users (
-  id bigint generated always as identity primary key
-);
-
--- For distributed systems needing UUIDs, use UUIDv7 (time-ordered)
--- Requires pg_uuidv7 extension: create extension pg_uuidv7;
-create table orders (
-  id uuid default uuid_generate_v7() primary key  -- Time-ordered, no fragmentation
-);
-
--- Alternative: time-prefixed IDs for sortable, distributed IDs (no extension needed)
-create table events (
-  id text default concat(
-    to_char(now() at time zone 'utc', 'YYYYMMDDHH24MISSMS'),
-    gen_random_uuid()::text
-  ) primary key
-);
-```
-
-Guidelines:
-
-- Single database: `bigint identity` (sequential, 8 bytes, SQL-standard)
-- Distributed/exposed IDs: UUIDv7 (requires pg_uuidv7) or ULID (time-ordered, no
-  fragmentation)
-- `serial` works but `identity` is SQL-standard and preferred for new
-  applications
-- Avoid random UUIDs (v4) as primary keys on large tables (causes index
-  fragmentation)
-
-Reference:
-[Identity Columns](https://www.postgresql.org/docs/current/sql-createtable.html#SQL-CREATETABLE-PARMS-GENERATED-IDENTITY)

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/supabase-postgres-best-practices/references/security-privileges.md

@@ -1,54 +0,0 @@
----
-title: Apply Principle of Least Privilege
-impact: MEDIUM
-impactDescription: Reduced attack surface, better audit trail
-tags: privileges, security, roles, permissions
----
-
-## Apply Principle of Least Privilege
-
-Grant only the minimum permissions required. Never use superuser for application queries.
-
-**Incorrect (overly broad permissions):**
-
-```sql
--- Application uses superuser connection
--- Or grants ALL to application role
-grant all privileges on all tables in schema public to app_user;
-grant all privileges on all sequences in schema public to app_user;
-
--- Any SQL injection becomes catastrophic
--- drop table users; cascades to everything
-```
-
-**Correct (minimal, specific grants):**
-
-```sql
--- Create role with no default privileges
-create role app_readonly nologin;
-
--- Grant only SELECT on specific tables
-grant usage on schema public to app_readonly;
-grant select on public.products, public.categories to app_readonly;
-
--- Create role for writes with limited scope
-create role app_writer nologin;
-grant usage on schema public to app_writer;
-grant select, insert, update on public.orders to app_writer;
-grant usage on sequence orders_id_seq to app_writer;
--- No DELETE permission
-
--- Login role inherits from these
-create role app_user login password 'xxx';
-grant app_writer to app_user;
-```
-
-Revoke public defaults:
-
-```sql
--- Revoke default public access
-revoke all on schema public from public;
-revoke all on all tables in schema public from public;
-```
-
-Reference: [Roles and Privileges](https://supabase.com/blog/postgres-roles-and-privileges)

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/supabase-postgres-best-practices/references/security-rls-basics.md

@@ -1,50 +0,0 @@
----
-title: Enable Row Level Security for Multi-Tenant Data
-impact: CRITICAL
-impactDescription: Database-enforced tenant isolation, prevent data leaks
-tags: rls, row-level-security, multi-tenant, security
----
-
-## Enable Row Level Security for Multi-Tenant Data
-
-Row Level Security (RLS) enforces data access at the database level, ensuring users only see their own data.
-
-**Incorrect (application-level filtering only):**
-
-```sql
--- Relying only on application to filter
-select * from orders where user_id = $current_user_id;
-
--- Bug or bypass means all data is exposed!
-select * from orders;  -- Returns ALL orders
-```
-
-**Correct (database-enforced RLS):**
-
-```sql
--- Enable RLS on the table
-alter table orders enable row level security;
-
--- Create policy for users to see only their orders
-create policy orders_user_policy on orders
-  for all
-  using (user_id = current_setting('app.current_user_id')::bigint);
-
--- Force RLS even for table owners
-alter table orders force row level security;
-
--- Set user context and query
-set app.current_user_id = '123';
-select * from orders;  -- Only returns orders for user 123
-```
-
-Policy for authenticated role:
-
-```sql
-create policy orders_user_policy on orders
-  for all
-  to authenticated
-  using (user_id = auth.uid());
-```
-
-Reference: [Row Level Security](https://supabase.com/docs/guides/database/postgres/row-level-security)

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/cursor/skills/supabase-postgres-best-practices/references/security-rls-performance.md

@@ -1,57 +0,0 @@
----
-title: Optimize RLS Policies for Performance
-impact: HIGH
-impactDescription: 5-10x faster RLS queries with proper patterns
-tags: rls, performance, security, optimization
----
-
-## Optimize RLS Policies for Performance
-
-Poorly written RLS policies can cause severe performance issues. Use subqueries and indexes strategically.
-
-**Incorrect (function called for every row):**
-
-```sql
-create policy orders_policy on orders
-  using (auth.uid() = user_id);  -- auth.uid() called per row!
-
--- With 1M rows, auth.uid() is called 1M times
-```
-
-**Correct (wrap functions in SELECT):**
-
-```sql
-create policy orders_policy on orders
-  using ((select auth.uid()) = user_id);  -- Called once, cached
-
--- 100x+ faster on large tables
-```
-
-Use security definer functions for complex checks:
-
-```sql
--- Create helper function (runs as definer, bypasses RLS)
-create or replace function is_team_member(team_id bigint)
-returns boolean
-language sql
-security definer
-set search_path = ''
-as $$
-  select exists (
-    select 1 from public.team_members
-    where team_id = $1 and user_id = (select auth.uid())
-  );
-$$;
-
--- Use in policy (indexed lookup, not per-row check)
-create policy team_orders_policy on orders
-  using ((select is_team_member(team_id)));
-```
-
-Always add indexes on columns used in RLS policies:
-
-```sql
-create index orders_user_id_idx on orders (user_id);
-```
-
-Reference: [RLS Performance](https://supabase.com/docs/guides/database/postgres/row-level-security#rls-performance-recommendations)

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/windsurf/skills/mongoose-nestjs/POWER.md

@@ -1,211 +0,0 @@
----
-name: mongoose-nestjs
-displayName: Mongoose NestJS
-description: Mongoose integration with NestJS including schema design, repository pattern, transactions, migrations, and multi-tenancy. Use for MongoDB database layer implementation.
-keywords:
-  - Mongoose
-  - MongoDB
-  - NestJS Mongoose
-  - schema
-  - repository pattern
-  - transactions
-  - ODM
-author: OneUp
----
-
-# Mongoose NestJS
-
-## Overview
-
-Expert guidance for integrating Mongoose with NestJS applications. Covers schema design, repository pattern implementation, transaction handling, data migrations, and multi-tenant architecture patterns.
-
-## Role Definition
-
-You are a database specialist with deep expertise in MongoDB and Mongoose ODM. You design efficient schemas, implement clean repository abstractions, and ensure data integrity through proper transaction handling.
-
-## When to Use This Power
-
-- Designing Mongoose schemas for NestJS
-- Implementing repository pattern with Mongoose
-- Handling MongoDB transactions
-- Creating database migrations
-- Setting up multi-tenant data isolation
-- Optimizing Mongoose queries
-
-## Core Workflow
-
-1. **Design Schema** - Define document structure with proper types and indexes
-2. **Create Repository** - Implement data access layer with base repository
-3. **Add Transactions** - Wrap critical operations in transactions
-4. **Write Migrations** - Version schema changes
-5. **Test** - Verify data integrity and performance
-
-## Available Steering Files
-
-| Topic              | Reference                        | Load When                                      |
-| ------------------ | -------------------------------- | ---------------------------------------------- |
-| Schema Design      | `references/schema-design.md`      | Creating schemas, indexes, virtuals, hooks     |
-| Repository Pattern | `references/repository-pattern.md` | Base repository, custom queries, pagination    |
-| Transactions       | `references/transactions.md`       | ACID operations, retry logic, session handling |
-| Migrations         | `references/migrations.md`         | Schema versioning, data migrations             |
-
-## Quick Reference
-
-### Module Setup
-
-```typescript
-// app.module.ts
-import { Module } from "@nestjs/common";
-import { MongooseModule } from "@nestjs/mongoose";
-import { ConfigModule, ConfigService } from "@nestjs/config";
-
-@Module({
-  imports: [
-    MongooseModule.forRootAsync({
-      imports: [ConfigModule],
-      useFactory: (config: ConfigService) => ({
-        uri: config.get<string>("MONGO_URL"),
-        // Connection options
-        maxPoolSize: 10,
-        serverSelectionTimeoutMS: 5000,
-        socketTimeoutMS: 45000,
-      }),
-      inject: [ConfigService],
-    }),
-  ],
-})
-export class AppModule {}
-```
-
-### Schema Definition
-
-```typescript
-// user.schema.ts
-import { Prop, Schema, SchemaFactory } from "@nestjs/mongoose";
-import { Document, Types } from "mongoose";
-
-export type UserDocument = User & Document;
-
-@Schema({
-  timestamps: true,
-  collection: "users",
-})
-export class User {
-  @Prop({ required: true, unique: true, index: true })
-  username: string;
-
-  @Prop({ required: true, select: false })
-  password: string;
-
-  @Prop({ required: true, index: true })
-  organizationId: string;
-
-  @Prop({ type: String, enum: ["SUPER_ADMIN", "ADMIN", "STAFF"] })
-  role: string;
-
-  @Prop({ default: true })
-  enabled: boolean;
-}
-
-export const UserSchema = SchemaFactory.createForClass(User);
-
-// Add indexes
-UserSchema.index({ organizationId: 1, role: 1 });
-UserSchema.index({ username: "text", name: "text" });
-```
-
-### Feature Module
-
-```typescript
-// users.module.ts
-import { Module } from "@nestjs/common";
-import { MongooseModule } from "@nestjs/mongoose";
-import { User, UserSchema } from "./schemas/user.schema";
-import { UsersController } from "./users.controller";
-import { UsersService } from "./users.service";
-import { UsersRepository } from "./users.repository";
-
-@Module({
-  imports: [
-    MongooseModule.forFeature([{ name: User.name, schema: UserSchema }]),
-  ],
-  controllers: [UsersController],
-  providers: [UsersService, UsersRepository],
-  exports: [UsersService],
-})
-export class UsersModule {}
-```
-
-### Repository Pattern
-
-```typescript
-// users.repository.ts
-import { Injectable, Logger } from "@nestjs/common";
-import { InjectModel } from "@nestjs/mongoose";
-import { Model, ClientSession } from "mongoose";
-import { User, UserDocument } from "./schemas/user.schema";
-
-@Injectable()
-export class UsersRepository {
-  private readonly logger = new Logger(UsersRepository.name);
-
-  constructor(
-    @InjectModel(User.name)
-    private readonly model: Model<UserDocument>,
-  ) {}
-
-  async create(
-    data: Partial<User>,
-    session?: ClientSession,
-  ): Promise<UserDocument> {
-    const user = new this.model(data);
-    return user.save({ session });
-  }
-
-  async findById(
-    id: string,
-    session?: ClientSession,
-  ): Promise<UserDocument | null> {
-    return this.model.findById(id).session(session).exec();
-  }
-
-  async findByUsername(username: string): Promise<UserDocument | null> {
-    return this.model.findOne({ username }).select("+password").exec();
-  }
-}
-```
-
-## Constraints
-
-### MUST DO
-
-- Use `@nestjs/mongoose` decorators for schemas
-- Implement repository pattern for data access
-- Add indexes for frequently queried fields
-- Use transactions for multi-document operations
-- Handle connection errors gracefully
-- Use `lean()` for read-only queries
-
-### MUST NOT DO
-
-- Access Model directly in services (use repository)
-- Skip indexes on large collections
-- Ignore transaction rollback on errors
-- Store sensitive data without encryption
-- Use `any` type for document fields
-
-## Schema Design Principles
-
-| Principle          | Description                               |
-| ------------------ | ----------------------------------------- |
-| Embed vs Reference | Embed for 1:few, reference for 1:many     |
-| Denormalization    | Duplicate data for read performance       |
-| Indexing           | Index query patterns, not just fields     |
-| Validation         | Use Mongoose validators + class-validator |
-| Timestamps         | Always enable `timestamps: true`          |
-
-## Related Powers
-
-- **NestJS Expert** - Core NestJS patterns
-- **Database Optimizer** - Query optimization
-- **Architecture Designer** - Data modeling decisions