@cubis/foundry 0.3.10 → 0.3.12

package/Ai Agent Workflow/powers/vercel-routing/SKILL.md

@@ -0,0 +1,79 @@
+---
+name: vercel-routing
+description: "Vercel edge routing: middleware patterns, redirects/rewrites, Edge Config for real-time config without redeploys, Edge Config integrations, and Node.js migration paths."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, routing, middleware, redirects, rewrites, edge config, edge config integrations, edge to node, a/b routing, geo routing, edge middleware
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, vercel-functions, vercel-caching, vercel-flags
+  consolidates: vercel-routing-middleware, vercel-redirects-rewrites, vercel-edge-config, vercel-edge-config-integrations, vercel-edge-to-node-migration
+---
+
+# Vercel Routing
+
+## Purpose
+
+Configure Vercel's edge routing layer with middleware patterns, redirect/rewrite rules, real-time Edge Config for runtime configuration, and migration paths away from the edge runtime.
+
+## When To Use
+
+- Writing Vercel Middleware for auth, geo-routing, A/B testing, or bot checks.
+- Configuring redirects and rewrites in `vercel.json` or Next.js config.
+- Using Edge Config for real-time feature toggling or config without redeploys.
+- Integrating Edge Config with third-party providers (LaunchDarkly, etc.).
+- Migrating edge-incompatible middleware to Node.js functions.
+
+## Domain Areas
+
+### Middleware
+
+- Author `middleware.ts` with `NextRequest`/`NextResponse` or Web APIs.
+- Apply auth checks, geo-redirects, A/B bucket assignment.
+- Use `matcher` config to scope execution precisely.
+- Mind cold start and bundle size constraints (1MB limit).
+
+### Redirects & Rewrites
+
+- Configure in `vercel.json` under `redirects` / `rewrites`.
+- Permanent (308) vs temporary (307) redirects.
+- Capture groups and dynamic path rewriting.
+- Header-based and query-based conditional rewrites.
+
+### Edge Config
+
+- Create and populate Edge Config stores via dashboard or CLI.
+- Read in middleware with `@vercel/edge-config` SDK.
+- Zero-redeploy config changes for feature flags and kill switches.
+
+### Edge Config Integrations
+
+- Connect Edge Config to third-party providers.
+- Sync external flag state into Edge Config automatically.
+
+### Edge-to-Node Migration
+
+- Identify middleware using Node.js-incompatible APIs.
+- Refactor to Node.js serverless functions or API routes.
+- Use `runtime: 'nodejs'` config override.
+
+## Operating Checklist
+
+1. Audit middleware bundle size and strip unnecessary dependencies.
+2. Validate matcher patterns cover only intended routes.
+3. Test redirect rules for cyclic redirect risk.
+4. Populate Edge Config with safe defaults before enabling reads.
+5. Document Edge Config keys and owners; restrict write access.
+6. Plan edge-to-node migration with regression test coverage.
+
+## Output Contract
+
+- Middleware implementation with matcher config
+- Redirect/rewrite rule set with conflict analysis
+- Edge Config schema, population scripts, and read integration
+- Edge-to-node migration plan with test strategy
+- Performance impact assessment (middleware execution time)

package/Ai Agent Workflow/powers/vercel-storage/POWER.md

@@ -0,0 +1,77 @@
+````markdown
+---
+inclusion: manual
+name: vercel-storage
+description: "Vercel Storage solutions: Blob for file storage, Marketplace Postgres, Marketplace Redis, and storage migration strategies between providers."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, storage, blob, postgres, redis, kv, storage migration, file upload, vercel blob, vercel postgres, vercel redis
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: database-design, database-optimizer, vercel-functions, vercel-deployments
+  consolidates: vercel-blob, vercel-marketplace-storage-postgres, vercel-marketplace-storage-redis, vercel-storage-migrations
+---
+
+# Vercel Storage
+
+## Purpose
+
+Implement and manage Vercel Storage solutions including Blob for file/object storage, Marketplace Postgres for relational data, Marketplace Redis for caching/session state, and strategies for migrating between storage providers.
+
+## When To Use
+
+- Storing user-uploaded files, assets, or binary objects with Vercel Blob.
+- Provisioning a managed Postgres database via Vercel Marketplace.
+- Using managed Redis for session storage, caching, or pub/sub.
+- Migrating existing storage workloads onto or off Vercel-managed storage.
+
+## Domain Areas
+
+### Vercel Blob
+
+- Upload, list, and delete blobs with `@vercel/blob` SDK.
+- Client-side uploads using multipart upload tokens.
+- Set Content-Type, cache-control, and access control.
+- Integrate blob URLs with CDN delivery.
+
+### Marketplace Postgres
+
+- Provision and connect via `POSTGRES_URL` environment variable.
+- Use with Prisma, Drizzle, or `pg`/`postgres` client.
+- Connection pooling with Vercel Postgres connection pool.
+- Schema migrations and backup strategy.
+
+### Marketplace Redis
+
+- Connect via `KV_URL` / `REDIS_URL` environment variable.
+- Use `@vercel/kv` SDK or `ioredis` for session state, queues, and rate limiting.
+- Understand persistence and eviction policy defaults.
+- Multi-region replication considerations.
+
+### Storage Migrations
+
+- Audit current storage usage volume and access patterns.
+- Plan zero-downtime migration with dual-write phase.
+- Validate data integrity post-migration before cutover.
+
+## Operating Checklist
+
+1. Choose storage type based on access pattern (object vs relational vs KV).
+2. Inject connection strings via environment variables (never hard-code).
+3. Set appropriate TTL/eviction policies for Redis.
+4. Validate connection pooling config for Postgres under load.
+5. Run migration dry-run and verify checksums before full cutover.
+6. Enable auto-backup or export schedule for production data.
+
+## Output Contract
+
+- Storage selection rationale and architecture
+- SDK integration code and environment variable setup
+- Connection pooling and scaling configuration
+- Migration plan with dry-run and rollback steps
+- Residual risks and data integrity validation evidence
+````

package/Ai Agent Workflow/powers/vercel-storage/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: vercel-storage
+description: "Vercel Storage solutions: Blob for file storage, Marketplace Postgres, Marketplace Redis, and storage migration strategies between providers."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, storage, blob, postgres, redis, kv, storage migration, file upload, vercel blob, vercel postgres, vercel redis
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: database-design, database-optimizer, vercel-functions, vercel-deployments
+  consolidates: vercel-blob, vercel-marketplace-storage-postgres, vercel-marketplace-storage-redis, vercel-storage-migrations
+---
+
+# Vercel Storage
+
+## Purpose
+
+Implement and manage Vercel Storage solutions including Blob for file/object storage, Marketplace Postgres for relational data, Marketplace Redis for caching/session state, and strategies for migrating between storage providers.
+
+## When To Use
+
+- Storing user-uploaded files, assets, or binary objects with Vercel Blob.
+- Provisioning a managed Postgres database via Vercel Marketplace.
+- Using managed Redis for session storage, caching, or pub/sub.
+- Migrating existing storage workloads onto or off Vercel-managed storage.
+
+## Domain Areas
+
+### Vercel Blob
+
+- Upload, list, and delete blobs with `@vercel/blob` SDK.
+- Client-side uploads using multipart upload tokens.
+- Set Content-Type, cache-control, and access control.
+- Integrate blob URLs with CDN delivery.
+
+### Marketplace Postgres
+
+- Provision and connect via `POSTGRES_URL` environment variable.
+- Use with Prisma, Drizzle, or `pg`/`postgres` client.
+- Connection pooling with Vercel Postgres connection pool.
+- Schema migrations and backup strategy.
+
+### Marketplace Redis
+
+- Connect via `KV_URL` / `REDIS_URL` environment variable.
+- Use `@vercel/kv` SDK or `ioredis` for session state, queues, and rate limiting.
+- Understand persistence and eviction policy defaults.
+- Multi-region replication considerations.
+
+### Storage Migrations
+
+- Audit current storage usage volume and access patterns.
+- Plan zero-downtime migration with dual-write phase.
+- Validate data integrity post-migration before cutover.
+
+## Operating Checklist
+
+1. Choose storage type based on access pattern (object vs relational vs KV).
+2. Inject connection strings via environment variables (never hard-code).
+3. Set appropriate TTL/eviction policies for Redis.
+4. Validate connection pooling config for Postgres under load.
+5. Run migration dry-run and verify checksums before full cutover.
+6. Enable auto-backup or export schedule for production data.
+
+## Output Contract
+
+- Storage selection rationale and architecture
+- SDK integration code and environment variable setup
+- Connection pooling and scaling configuration
+- Migration plan with dry-run and rollback steps
+- Residual risks and data integrity validation evidence

package/Ai Agent Workflow/powers/vulnerability-scanner/POWER.md

@@ -1,13 +1,279 @@
+````markdown
 ---
+inclusion: manual
 name: vulnerability-scanner
 description: Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
+allowed-tools: Read, Glob, Grep, Bash
 ---
 
-# vulnerability-scanner
+# Vulnerability Scanner
 
-This is a compatibility power wrapper for the `vulnerability-scanner` skill.
+> Think like an attacker, defend like an expert. 2025 threat landscape awareness.
 
-Primary source:
-- `Ai Agent Workflow/skills/vulnerability-scanner/SKILL.md`
+## 🔧 Runtime Scripts
 
-Use this folder for power-specific extensions when needed.
+**Execute for automated validation:**
+
+| Script | Purpose | Usage |
+|--------|---------|-------|
+| `scripts/security_scan.py` | Validate security principles applied | `python scripts/security_scan.py <project_path>` |
+
+## 📋 Reference Files
+
+| File | Purpose |
+|------|---------|
+| [checklists.md](checklists.md) | OWASP Top 10, Auth, API, Data protection checklists |
+
+---
+
+## 1. Security Expert Mindset
+
+### Core Principles
+
+| Principle | Application |
+|-----------|-------------|
+| **Assume Breach** | Design as if attacker already inside |
+| **Zero Trust** | Never trust, always verify |
+| **Defense in Depth** | Multiple layers, no single point |
+| **Least Privilege** | Minimum required access only |
+| **Fail Secure** | On error, deny access |
+
+### Threat Modeling Questions
+
+Before scanning, ask:
+1. What are we protecting? (Assets)
+2. Who would attack? (Threat actors)
+3. How would they attack? (Attack vectors)
+4. What's the impact? (Business risk)
+
+---
+
+## 2. OWASP Top 10:2025
+
+### Risk Categories
+
+| Rank | Category | Think About |
+|------|----------|-------------|
+| **A01** | Broken Access Control | Who can access what? IDOR, SSRF |
+| **A02** | Security Misconfiguration | Defaults, headers, exposed services |
+| **A03** | Software Supply Chain 🆕 | Dependencies, CI/CD, build integrity |
+| **A04** | Cryptographic Failures | Weak crypto, exposed secrets |
+| **A05** | Injection | User input → system commands |
+| **A06** | Insecure Design | Flawed architecture |
+| **A07** | Authentication Failures | Session, credential management |
+| **A08** | Integrity Failures | Unsigned updates, tampered data |
+| **A09** | Logging & Alerting | Blind spots, no monitoring |
+| **A10** | Exceptional Conditions 🆕 | Error handling, fail-open states |
+
+### 2025 Key Changes
+
+```
+2021 → 2025 Shifts:
+├── SSRF merged into A01 (Access Control)
+├── A02 elevated (Cloud/Container configs)
+├── A03 NEW: Supply Chain (major focus)
+├── A10 NEW: Exceptional Conditions
+└── Focus shift: Root causes > Symptoms
+```
+
+---
+
+## 3. Supply Chain Security (A03)
+
+### Attack Surface
+
+| Vector | Risk | Question to Ask |
+|--------|------|-----------------|
+| **Dependencies** | Malicious packages | Do we audit new deps? |
+| **Lock files** | Integrity attacks | Are they committed? |
+| **Build pipeline** | CI/CD compromise | Who can modify? |
+| **Registry** | Typosquatting | Verified sources? |
+
+### Defense Principles
+
+- Verify package integrity (checksums)
+- Pin versions, audit updates
+- Use private registries for critical deps
+- Sign and verify artifacts
+
+---
+
+## 4. Attack Surface Mapping
+
+### What to Map
+
+| Category | Elements |
+|----------|----------|
+| **Entry Points** | APIs, forms, file uploads |
+| **Data Flows** | Input → Process → Output |
+| **Trust Boundaries** | Where auth/authz checked |
+| **Assets** | Secrets, PII, business data |
+
+### Prioritization Matrix
+
+```
+Risk = Likelihood × Impact
+
+High Impact + High Likelihood → CRITICAL
+High Impact + Low Likelihood  → HIGH
+Low Impact + High Likelihood  → MEDIUM
+Low Impact + Low Likelihood   → LOW
+```
+
+---
+
+## 5. Risk Prioritization
+
+### CVSS + Context
+
+| Factor | Weight | Question |
+|--------|--------|----------|
+| **CVSS Score** | Base severity | How severe is the vuln? |
+| **EPSS Score** | Exploit likelihood | Is it being exploited? |
+| **Asset Value** | Business context | What's at risk? |
+| **Exposure** | Attack surface | Internet-facing? |
+
+### Prioritization Decision Tree
+
+```
+Is it actively exploited (EPSS >0.5)?
+├── YES → CRITICAL: Immediate action
+└── NO → Check CVSS
+         ├── CVSS ≥9.0 → HIGH
+         ├── CVSS 7.0-8.9 → Consider asset value
+         └── CVSS <7.0 → Schedule for later
+```
+
+---
+
+## 6. Exceptional Conditions (A10 - New)
+
+### Fail-Open vs Fail-Closed
+
+| Scenario | Fail-Open (BAD) | Fail-Closed (GOOD) |
+|----------|-----------------|---------------------|
+| Auth error | Allow access | Deny access |
+| Parsing fails | Accept input | Reject input |
+| Timeout | Retry forever | Limit + abort |
+
+### What to Check
+
+- Exception handlers that catch-all and ignore
+- Missing error handling on security operations
+- Race conditions in auth/authz
+- Resource exhaustion scenarios
+
+---
+
+## 7. Scanning Methodology
+
+### Phase-Based Approach
+
+```
+1. RECONNAISSANCE
+   └── Understand the target
+       ├── Technology stack
+       ├── Entry points
+       └── Data flows
+
+2. DISCOVERY
+   └── Identify potential issues
+       ├── Configuration review
+       ├── Dependency analysis
+       └── Code pattern search
+
+3. ANALYSIS
+   └── Validate and prioritize
+       ├── False positive elimination
+       ├── Risk scoring
+       └── Attack chain mapping
+
+4. REPORTING
+   └── Actionable findings
+       ├── Clear reproduction steps
+       ├── Business impact
+       └── Remediation guidance
+```
+
+---
+
+## 8. Code Pattern Analysis
+
+### High-Risk Patterns
+
+| Pattern | Risk | Look For |
+|---------|------|----------|
+| **String concat in queries** | Injection | `"SELECT * FROM " + user_input` |
+| **Dynamic code execution** | RCE | `eval()`, `exec()`, `Function()` |
+| **Unsafe deserialization** | RCE | `pickle.loads()`, `unserialize()` |
+| **Path manipulation** | Traversal | User input in file paths |
+| **Disabled security** | Various | `verify=False`, `--insecure` |
+
+### Secret Patterns
+
+| Type | Indicators |
+|------|-----------|
+| API Keys | `api_key`, `apikey`, high entropy |
+| Tokens | `token`, `bearer`, `jwt` |
+| Credentials | `password`, `secret`, `key` |
+| Cloud | `AWS_`, `AZURE_`, `GCP_` prefixes |
+
+---
+
+## 9. Cloud Security Considerations
+
+### Shared Responsibility
+
+| Layer | You Own | Provider Owns |
+|-------|---------|---------------|
+| Data | ✅ | ❌ |
+| Application | ✅ | ❌ |
+| OS/Runtime | Depends | Depends |
+| Infrastructure | ❌ | ✅ |
+
+### Cloud-Specific Checks
+
+- IAM: Least privilege applied?
+- Storage: Public buckets?
+- Network: Security groups tightened?
+- Secrets: Using secrets manager?
+
+---
+
+## 10. Anti-Patterns
+
+| ❌ Don't | ✅ Do |
+|----------|-------|
+| Scan without understanding | Map attack surface first |
+| Alert on every CVE | Prioritize by exploitability + asset |
+| Ignore false positives | Maintain verified baseline |
+| Fix symptoms only | Address root causes |
+| Scan once before deploy | Continuous scanning |
+| Trust third-party deps blindly | Verify integrity, audit code |
+
+---
+
+## 11. Reporting Principles
+
+### Finding Structure
+
+Each finding should answer:
+1. **What?** - Clear vulnerability description
+2. **Where?** - Exact location (file, line, endpoint)
+3. **Why?** - Root cause explanation
+4. **Impact?** - Business consequence
+5. **How to fix?** - Specific remediation
+
+### Severity Classification
+
+| Severity | Criteria |
+|----------|----------|
+| **Critical** | RCE, auth bypass, mass data exposure |
+| **High** | Data exposure, privilege escalation |
+| **Medium** | Limited scope, requires conditions |
+| **Low** | Informational, best practice |
+
+---
+
+> **Remember:** Vulnerability scanning finds issues. Expert thinking prioritizes what matters. Always ask: "What would an attacker do with this?"
+````