@cubis/foundry 0.3.31 → 0.3.33

package/workflows/skills/vercel-functions/SKILL.md

@@ -1,81 +1,21 @@
 ---
 name: vercel-functions
-description: "Vercel Serverless and Edge Functions: core patterns, Node.js and Python runtimes, edge runtime, Fluid Compute for long-running tasks, and function configuration."
-license: MIT
+description: "Compatibility alias skill. Deprecated: use vercel-runtime."
 metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, serverless, functions, edge function, nodejs runtime, python runtime, fluid compute, function config, api route, edge runtime
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nodejs-best-practices, fastapi-expert, vercel-routing, vercel-caching
-  consolidates: vercel-functions-core, vercel-functions-edge-runtime, vercel-functions-nodejs, vercel-functions-python, vercel-function-config, vercel-fluid-compute
+  deprecated: true
+  replaced_by: vercel-runtime
+  removal_target: v0.6.0
 ---
 
 # Vercel Functions
 
-## Purpose
+## Compatibility Alias
 
-Design and implement Vercel Serverless and Edge Functions with the correct runtime selection, configuration, and compute strategy for each use case.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-runtime` as the canonical skill.
 
-- Writing Vercel API routes or serverless function handlers.
-- Choosing between Edge Runtime and Node.js runtime.
-- Configuring Python serverless functions on Vercel.
-- Implementing long-running tasks or streaming with Fluid Compute.
-- Tuning function memory, regions, timeout, and concurrency config.
+## Migration
 
-## Domain Areas
-
-### Core Patterns
-
-- Request/response handler structure for Vercel functions.
-- Environment-aware error handling and status codes.
-- Cold start mitigation strategies.
-
-### Node.js Runtime
-
-- Use `@vercel/node` and standard Node.js APIs.
-- Streaming responses with `Response` and `ReadableStream`.
-
-### Python Runtime
-
-- Configure `requirements.txt` and handler conventions.
-- Use WSGI/ASGI adapters where needed.
-
-### Edge Runtime
-
-- Use Web Standard APIs only (no Node.js built-ins).
-- Optimize for global low-latency execution at the edge.
-- Middleware-friendly patterns.
-
-### Fluid Compute
-
-- Enable for long-running tasks exceeding standard limits.
-- Stream output progressively for large responses.
-- Configure max duration and concurrency appropriately.
-
-### Function Config (`vercel.json`)
-
-- Set `runtime`, `regions`, `maxDuration`, `memory` per function.
-- Use `rewrites` to map routes to specific functions.
-
-## Operating Checklist
-
-1. Choose runtime (Edge vs Node.js vs Python) based on latency, API, and duration needs.
-2. Set explicit `maxDuration` and `memory` for non-default requirements.
-3. Implement structured error responses with proper HTTP status codes.
-4. Test cold-start behavior and streaming in staging environment.
-5. Validate regional deployment targets match latency requirements.
-6. Run regression checks before promoting to production.
-
-## Output Contract
-
-- Runtime selection rationale and tradeoffs
-- Handler implementation with error handling and streaming
-- `vercel.json` function config section
-- Performance validation (cold start, p99 latency targets)
-- Residual risks and follow-up actions
+1. Replace direct references to `vercel-functions` with `vercel-runtime`.
+2. Apply the full workflow from `vercel-runtime` for new work.

package/workflows/skills/vercel-routing/SKILL.md

@@ -1,79 +1,21 @@
 ---
 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
+description: "Compatibility alias skill. Deprecated: use vercel-runtime."
 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
+  deprecated: true
+  replaced_by: vercel-runtime
+  removal_target: v0.6.0
 ---
 
 # Vercel Routing
 
-## Purpose
+## Compatibility Alias
 
-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.
+This skill is deprecated and kept for backward compatibility.
 
-## When To Use
+Use `vercel-runtime` as the canonical skill.
 
-- 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.
+## Migration
 
-## 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)
+1. Replace direct references to `vercel-routing` with `vercel-runtime`.
+2. Apply the full workflow from `vercel-runtime` for new work.

package/workflows/skills/vercel-runtime/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: vercel-runtime
+description: "Canonical Vercel runtime skill covering functions, routing, and caching with production guardrails."
+metadata:
+  deprecated: false
+  replaced_by: null
+  removal_target: null
+---
+
+# Vercel Runtime
+
+## Purpose
+
+Design and operate Vercel runtime behavior across serverless/edge functions, routing/middleware, and caching strategy as one coherent runtime layer.
+
+## Use This For
+
+- Function runtime selection (Node, Python, Edge, Fluid Compute)
+- Middleware, redirects/rewrites, Edge Config routing behavior
+- Cache-control, CDN behavior, ISR, Data Cache, invalidation
+
+## Decision Flow
+
+1. Confirm execution boundary (edge vs serverless vs region).
+2. Select routing strategy and middleware scope.
+3. Choose caching policy by data volatility and SLA.
+4. Validate failure behavior, fallback path, and observability.
+
+## Verification
+
+- Runtime logs confirm expected execution target.
+- Latency and cache hit ratio are measured.
+- No blocking regressions in auth/routing flows.
+
+## Related Skills
+
+- `vercel-platform`
+- `vercel-delivery`
+- `vercel-security`
+- `vercel-observability`

package/workflows/skills/vercel-security/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: vercel-security
+description: "Canonical Vercel security skill covering WAF, rate limiting, bot controls, and traffic-protection policy."
+metadata:
+  deprecated: false
+  replaced_by: null
+  removal_target: null
+---
+
+# Vercel Security
+
+## Purpose
+
+Secure Vercel deployments with enforceable edge protections: WAF policy, rate limiting, bot filtering, and abuse mitigation tied to observability signals.
+
+## Use This For
+
+- WAF and custom firewall rules
+- Rate-limit and abuse protection controls
+- Bot management and traffic filtering
+- Security hardening for public endpoints
+
+## Decision Flow
+
+1. Identify threat surface and high-risk routes.
+2. Apply least-disruptive controls first.
+3. Add strict controls for abusive patterns.
+4. Validate against false positives and critical user paths.
+
+## Verification
+
+- Attack traffic is blocked/challenged as expected.
+- Legitimate traffic remains unaffected on critical paths.
+- Security alerts and logs are correlated in observability tools.
+
+## Related Skills
+
+- `security-reviewer`
+- `secure-code-guardian`
+- `vercel-observability`

package/workflows/skills/vulnerability-scanner/SKILL.md

@@ -1,276 +1,21 @@
 ---
 name: vulnerability-scanner
-description: Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
-allowed-tools: Read, Glob, Grep, Bash
+description: "Compatibility alias skill. Deprecated: use security-reviewer."
+metadata:
+  deprecated: true
+  replaced_by: security-reviewer
+  removal_target: v0.6.0
 ---
 
 # Vulnerability Scanner
 
-> Think like an attacker, defend like an expert. 2025 threat landscape awareness.
+## Compatibility Alias
 
-## 🔧 Runtime Scripts
+This skill is deprecated and kept for backward compatibility.
 
-**Execute for automated validation:**
+Use `security-reviewer` as the canonical skill.
 
-| Script | Purpose | Usage |
-|--------|---------|-------|
-| `scripts/security_scan.py` | Validate security principles applied | `python scripts/security_scan.py <project_path>` |
+## Migration
 
-## 📋 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?"
+1. Replace direct references to `vulnerability-scanner` with `security-reviewer`.
+2. Apply the full workflow from `security-reviewer` for new work.