@cubis/foundry 0.3.30 → 0.3.32

package/Ai Agent Workflow/skills/testing-patterns/SKILL.md

@@ -1,178 +0,0 @@
----
-name: testing-patterns
-description: Testing patterns and principles. Unit, integration, mocking strategies.
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
----
-
-# Testing Patterns
-
-> Principles for reliable test suites.
-
----
-
-## 1. Testing Pyramid
-
-```
-        /\          E2E (Few)
-       /  \         Critical flows
-      /----\
-     /      \       Integration (Some)
-    /--------\      API, DB queries
-   /          \
-  /------------\    Unit (Many)
-                    Functions, classes
-```
-
----
-
-## 2. AAA Pattern
-
-| Step | Purpose |
-|------|---------|
-| **Arrange** | Set up test data |
-| **Act** | Execute code under test |
-| **Assert** | Verify outcome |
-
----
-
-## 3. Test Type Selection
-
-### When to Use Each
-
-| Type | Best For | Speed |
-|------|----------|-------|
-| **Unit** | Pure functions, logic | Fast (<50ms) |
-| **Integration** | API, DB, services | Medium |
-| **E2E** | Critical user flows | Slow |
-
----
-
-## 4. Unit Test Principles
-
-### Good Unit Tests
-
-| Principle | Meaning |
-|-----------|---------|
-| Fast | < 100ms each |
-| Isolated | No external deps |
-| Repeatable | Same result always |
-| Self-checking | No manual verification |
-| Timely | Written with code |
-
-### What to Unit Test
-
-| Test | Don't Test |
-|------|------------|
-| Business logic | Framework code |
-| Edge cases | Third-party libs |
-| Error handling | Simple getters |
-
----
-
-## 5. Integration Test Principles
-
-### What to Test
-
-| Area | Focus |
-|------|-------|
-| API endpoints | Request/response |
-| Database | Queries, transactions |
-| External services | Contracts |
-
-### Setup/Teardown
-
-| Phase | Action |
-|-------|--------|
-| Before All | Connect resources |
-| Before Each | Reset state |
-| After Each | Clean up |
-| After All | Disconnect |
-
----
-
-## 6. Mocking Principles
-
-### When to Mock
-
-| Mock | Don't Mock |
-|------|------------|
-| External APIs | The code under test |
-| Database (unit) | Simple dependencies |
-| Time/random | Pure functions |
-| Network | In-memory stores |
-
-### Mock Types
-
-| Type | Use |
-|------|-----|
-| Stub | Return fixed values |
-| Spy | Track calls |
-| Mock | Set expectations |
-| Fake | Simplified implementation |
-
----
-
-## 7. Test Organization
-
-### Naming
-
-| Pattern | Example |
-|---------|---------|
-| Should behavior | "should return error when..." |
-| When condition | "when user not found..." |
-| Given-when-then | "given X, when Y, then Z" |
-
-### Grouping
-
-| Level | Use |
-|-------|-----|
-| describe | Group related tests |
-| it/test | Individual case |
-| beforeEach | Common setup |
-
----
-
-## 8. Test Data
-
-### Strategies
-
-| Approach | Use |
-|----------|-----|
-| Factories | Generate test data |
-| Fixtures | Predefined datasets |
-| Builders | Fluent object creation |
-
-### Principles
-
-- Use realistic data
-- Randomize non-essential values (faker)
-- Share common fixtures
-- Keep data minimal
-
----
-
-## 9. Best Practices
-
-| Practice | Why |
-|----------|-----|
-| One assert per test | Clear failure reason |
-| Independent tests | No order dependency |
-| Fast tests | Run frequently |
-| Descriptive names | Self-documenting |
-| Clean up | Avoid side effects |
-
----
-
-## 10. Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Test implementation | Test behavior |
-| Duplicate test code | Use factories |
-| Complex test setup | Simplify or split |
-| Ignore flaky tests | Fix root cause |
-| Skip cleanup | Reset state |
-
----
-
-> **Remember:** Tests are documentation. If someone can't understand what the code does from the tests, rewrite them.

package/Ai Agent Workflow/skills/ux-ui-consistency/POWER.md

@@ -1,124 +0,0 @@
----
-name: "ux-ui-consistency"
-displayName: "UX/UI Consistency"
-description: "Ensure consistent UX patterns: design system component usage, screen states, error handling, and loading patterns"
-keywords:
-  [
-    "ux",
-    "ui consistency",
-    "design system",
-    "components",
-    "screen states",
-    "error handling",
-    "loading states",
-  ]
----
-
-# UX/UI Consistency
-
-## Overview
-
-This power ensures consistent user experience across all screens by enforcing design system component usage, proper screen state handling, and standardized error/loading patterns.
-
-## When to Use
-
-- Building new screens or features
-- Reviewing UI code for consistency
-- Implementing loading/error/empty states
-- Refactoring legacy UI to use design system components
-- Fixing UX inconsistencies reported by users
-
-## Quick Reference
-
-### Screen States Pattern
-
-```dart
-// ✅ Always handle all states
-ref.watch(dataProvider).when(
-  data: (data) {
-    if (data.isEmpty) {
-      return EmptyStateWidget(
-        message: 'No items found',
-        action: TextButton(
-          child: Text('Refresh'),
-          onPressed: () => ref.refresh(dataProvider),
-        ),
-      );
-    }
-    return ContentView(data);
-  },
-  loading: () => LoadingWidget(),
-  error: (error, stack) => ErrorWidget(
-    error: error,
-    onRetry: () => ref.refresh(dataProvider),
-  ),
-);
-```
-
-### Design System Component Rules
-
-```dart
-// ❌ Don't use raw Flutter widgets for common patterns
-Text('Hello')
-ElevatedButton(...)
-Container(...)
-
-// ✅ Use your project's design system components
-// Example: OneText.bodyMedium('Hello')
-// Example: OneButton.primary(...)
-// Example: OneContainer(...)
-```
-
-### Consistent Error Handling
-
-```dart
-// ✅ Show user-friendly errors
-try {
-  await submitForm();
-} catch (e) {
-  if (e is NetworkException) {
-    // Show network error via your design system's snackbar
-    showErrorSnackbar(context, 'No internet connection');
-  } else if (e is ValidationException) {
-    showWarningSnackbar(context, e.message);
-  } else {
-    showErrorSnackbar(context, 'Something went wrong');
-  }
-}
-```
-
-## UX Checklist
-
-### Screen States
-- [ ] Loading state (spinner or skeleton)
-- [ ] Error state (error view with retry)
-- [ ] Empty state (empty view with action)
-- [ ] Success state (actual content)
-
-### Interactive Feedback
-- [ ] Button shows loading during async operations
-- [ ] Form validation shows inline errors
-- [ ] Success feedback after mutations (snackbar/dialog)
-- [ ] Confirmation dialogs for destructive actions
-
-### Navigation
-- [ ] Back button behavior is consistent
-- [ ] Deep links work correctly
-- [ ] Navigation guards prevent unauthorized access
-- [ ] Loading states during navigation
-
-### Accessibility
-- [ ] Touch targets are 48x48 minimum
-- [ ] Color contrast meets WCAG AA
-- [ ] Screen reader labels present
-- [ ] Focus order is logical
-
-## Steering Files
-
-- `one_component_rules.md` - Complete design system component usage guide
-- `ux_checklist.md` - UX review checklist for all screens
-
-## Templates
-
-- `screen_states_widget` - Complete screen state handling template
-

package/Ai Agent Workflow/skills/vercel-ai-gateway/SKILL.md

@@ -1,79 +0,0 @@
----
-name: vercel-ai-gateway
-description: "Complete Vercel AI Gateway integration: LLM traffic routing, authentication/BYOK, fallback chains, model-provider routing policies, usage observability, and OpenAI-compatible endpoints."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, ai, gateway, llm, byok, fallback, model routing, openai compatible, token usage, ai observability
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: prompt-engineer, monitoring-expert, secure-code-guardian, vercel-observability
-  consolidates: vercel-ai-gateway-core, vercel-ai-gateway-auth-byok, vercel-ai-gateway-fallbacks, vercel-ai-gateway-model-routing, vercel-ai-gateway-observability, vercel-ai-gateway-openai-compatible
----
-
-# Vercel AI Gateway
-
-## Purpose
-
-Route LLM traffic through Vercel AI Gateway with unified controls covering authentication, model-provider routing, resilient fallback chains, usage observability, and OpenAI-compatible endpoint compatibility.
-
-## When To Use
-
-- Routing AI/LLM requests through Vercel's managed gateway.
-- Configuring bring-your-own-key (BYOK) authentication for AI providers.
-- Implementing retries and fallback chains for resilient AI responses.
-- Designing model and provider routing policies for latency, quality, and cost.
-- Monitoring AI Gateway usage, latency, and spend.
-- Using OpenAI-compatible endpoints without provider lock-in.
-
-## Domain Areas
-
-### Core Routing
-
-- Define unified gateway endpoint and routing config.
-- Set per-model quality, latency, and cost objectives.
-
-### Authentication & BYOK
-
-- Configure provider API key management and BYOK controls.
-- Scope key access per project/environment.
-
-### Fallbacks & Resilience
-
-- Implement retry policies and fallback provider chains.
-- Define circuit-breaker thresholds.
-
-### Model Routing Policies
-
-- Route by latency, cost, capability, or custom weights.
-- Support multi-provider and multi-region strategies.
-
-### Observability
-
-- Instrument token usage, latency, and error rates per model.
-- Set spend thresholds and alerting.
-
-### OpenAI Compatibility
-
-- Use OpenAI-compatible request/response format.
-- Migrate between providers without application changes.
-
-## Operating Checklist
-
-1. Define model quality, latency, and cost objectives for each endpoint.
-2. Configure authentication and BYOK key scoping per environment.
-3. Implement routing, fallback, and retry policies explicitly.
-4. Instrument token usage, latency, and error classes for all calls.
-5. Validate OpenAI-compatible endpoint compatibility if needed.
-6. Run safety and regression checks before broad rollout.
-
-## Output Contract
-
-- Proposed routing and authentication architecture with tradeoffs
-- Required config, code, and environment changes
-- Fallback chain definition and circuit-breaker settings
-- Validation evidence (spend limits, latency targets, error budgets)
-- Residual risks and follow-up actions

package/Ai Agent Workflow/skills/vercel-ai-sdk/SKILL.md

@@ -1,59 +0,0 @@
----
-name: vercel-ai-sdk
-description: "Vercel AI SDK for building AI-powered applications: core providers/streaming patterns and React/Svelte UI hooks for chat, completion, and generative UX."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, ai sdk, useChat, useCompletion, streamText, generateText, ai ui, streaming, generative ui
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: react-expert, nextjs-developer, prompt-engineer, vercel-ai-gateway
-  consolidates: vercel-ai-sdk-core, vercel-ai-sdk-ui
----
-
-# Vercel AI SDK
-
-## Purpose
-
-Build AI-powered applications with Vercel AI SDK covering core provider integration, streaming primitives, and framework UI hooks for chat, completion, and generative interfaces.
-
-## When To Use
-
-- Integrating LLM providers (OpenAI, Anthropic, Google, etc.) via unified SDK.
-- Streaming text, objects, or tool calls from the server to the client.
-- Building chat or completion UIs with `useChat` / `useCompletion` hooks.
-- Implementing generative UI and multi-step agent flows.
-
-## Domain Areas
-
-### Core (Provider & Streaming)
-
-- Configure providers with `createOpenAI`, `createAnthropic`, etc.
-- Use `streamText`, `generateText`, `streamObject`, `generateObject`.
-- Handle tool calls, multi-step flows, and error recovery.
-
-### UI Hooks (React / Svelte / Vue)
-
-- `useChat`: managed chat history, streaming, form submission.
-- `useCompletion`: single-prompt streaming completions.
-- `useAssistant`: OpenAI Assistants API integration.
-- Attach metadata, handle events, and control abort signals.
-
-## Operating Checklist
-
-1. Select and configure the appropriate provider.
-2. Choose streaming vs. non-streaming based on UX requirements.
-3. Implement error handling and loading states in UI hooks.
-4. Validate type safety of generated objects with schema validation.
-5. Test streaming under latency and partial-response conditions.
-
-## Output Contract
-
-- Provider configuration and env var requirements
-- Stream handler and UI hook implementation
-- Tool call schemas and multi-step flow definitions
-- Error and abort handling patterns
-- Validation evidence and rollback notes

package/Ai Agent Workflow/skills/vercel-caching/SKILL.md

@@ -1,83 +0,0 @@
----
-name: vercel-caching
-description: "Vercel caching strategies: CDN cache, cache-control headers, runtime cache, ISR, Next.js Data Cache, request collapsing, remote caching (Turborepo), and CDN purging."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, cdn cache, caching, isr, incremental static regeneration, data cache, request collapsing, remote caching, turborepo cache, cache purge, stale-while-revalidate, cache-control
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nextjs-developer, vercel-functions, vercel-routing, web-perf
-  consolidates: vercel-cdn-cache, vercel-cdn-purging, vercel-cache-control-headers, vercel-runtime-cache, vercel-isr, vercel-data-cache-nextjs, vercel-request-collapsing, vercel-remote-caching
----
-
-# Vercel Caching
-
-## Purpose
-
-Implement and tune Vercel's full caching stack to maximize performance and reduce origin load, including CDN edge caching, ISR, Next.js Data Cache, request collapsing, and Turborepo remote caching.
-
-## When To Use
-
-- Setting cache-control headers and CDN TTL for static/dynamic assets.
-- Configuring ISR revalidation periods and on-demand revalidation.
-- Using Next.js Data Cache (`fetch` caching, `unstable_cache`).
-- Purging CDN cache after deploys or content updates.
-- Enabling request collapsing to prevent cache stampedes.
-- Setting up Turborepo remote caching for faster CI.
-
-## Domain Areas
-
-### CDN Cache & Cache-Control
-
-- Set `Cache-Control: s-maxage`, `stale-while-revalidate` headers.
-- Configure edge cache TTL per route in `vercel.json`.
-- Understand Vercel's cache key construction.
-
-### CDN Purging
-
-- On-demand cache invalidation via Vercel dashboard or REST API.
-- Tag-based purge strategies for content updates.
-
-### ISR (Incremental Static Regeneration)
-
-- Configure `revalidate` in Next.js page/route handlers.
-- On-demand revalidation with `revalidatePath` / `revalidateTag`.
-- ISR fallback behavior and error handling.
-
-### Next.js Data Cache
-
-- `fetch` cache with `cache`, `next.revalidate`, `next.tags` options.
-- `unstable_cache` for non-fetch data sources.
-- Cache invalidation with `revalidateTag`.
-
-### Request Collapsing
-
-- Enable to coalesce concurrent cache-miss requests.
-- Validate behavior under load with simulated stampedes.
-
-### Remote Caching (Turborepo)
-
-- Configure Vercel Remote Cache for Turborepo.
-- Authenticate with `TURBO_TOKEN` and `TURBO_TEAM`.
-- Monitor cache hit rates and artifact sizes.
-
-## Operating Checklist
-
-1. Audit current cache-control headers and TTL values.
-2. Define caching strategy per route type (static, dynamic, API).
-3. Implement ISR or Data Cache with explicit revalidation tags.
-4. Set up cache purge automation for content updates.
-5. Enable and validate request collapsing in staging under load.
-6. Configure Turborepo remote caching and verify hit rates in CI.
-
-## Output Contract
-
-- Cache-control header strategy per route type
-- ISR/Data Cache configuration with revalidation tags
-- CDN purge automation plan and trigger events
-- Turborepo remote cache setup instructions
-- Performance validation (cache hit ratios, TTFB targets)

package/Ai Agent Workflow/skills/vercel-cli/SKILL.md

@@ -1,85 +0,0 @@
----
-name: vercel-cli
-description: "Vercel CLI mastery: core commands, flags, MCP integration, microfrontend management, and project/domain/environment variable operations from the command line."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel cli, vercel command, npx vercel, vercel dev, vercel deploy, vercel env, vercel domains cli, vercel pull, vercel link, vercel mcp, vercel microfrontends cli
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: devops-engineer, wrangler, vercel-deployments, vercel-domains
-  consolidates: vercel-cli-core, vercel-cli-flags, vercel-cli-mcp, vercel-cli-microfrontends, vercel-cli-project-domain-env
----
-
-# Vercel CLI
-
-## Purpose
-
-Use the Vercel CLI for local development, deployments, environment management, domain operations, microfrontend orchestration, and MCP-based automation workflows.
-
-## When To Use
-
-- Running `vercel dev` for local development with edge function support.
-- Deploying with `vercel --prod` or `vercel deploy` from CI/CD.
-- Managing environment variables with `vercel env add/pull/rm`.
-- Managing domains and DNS with `vercel domains`.
-- Linking, inspecting, and managing project config with `vercel link`.
-- Using the Vercel MCP for agent-based CLI automation.
-- Managing microfrontend apps from the CLI.
-
-## Domain Areas
-
-### Core Commands
-
-| Command                    | Purpose                                    |
-| -------------------------- | ------------------------------------------ |
-| `vercel` / `vercel deploy` | Deploy current directory                   |
-| `vercel --prod`            | Deploy to production                       |
-| `vercel dev`               | Local dev server with edge emulation       |
-| `vercel build`             | Build locally (mirrors Vercel cloud build) |
-| `vercel inspect <url>`     | Inspect deployment details                 |
-| `vercel rollback`          | Instant rollback to previous deployment    |
-| `vercel link`              | Link local directory to Vercel project     |
-| `vercel pull`              | Pull project settings and env vars locally |
-
-### Flags
-
-- `--env`, `--build-env`, `--token`, `--scope`, `--yes`, `--no-wait`.
-- `--regions` for targeted regional deployment.
-- `--archive=tgz` for artifact-based deployments.
-
-### Project / Domain / Env
-
-- `vercel env add/pull/rm` — manage environment variables.
-- `vercel domains add/rm/inspect` — domain management.
-- `vercel alias set <url> <alias>` — assign deployment aliases.
-
-### MCP Integration
-
-- Use Vercel MCP server for agent-driven CLI automation.
-- Query deployment state, logs, and project config programmatically.
-
-### Microfrontends
-
-- `vercel microfrontends` commands for app group management.
-- Register and route microfrontend applications from CLI.
-
-## Operating Checklist
-
-1. Authenticate with `vercel login` and verify scope with `vercel whoami`.
-2. Link project with `vercel link` before running local commands.
-3. Pull env vars with `vercel env pull .env.local` for local dev.
-4. Use `vercel build` to validate build output before deploying.
-5. Automate deployments in CI with `--token` and `--yes` flags.
-6. Use `vercel rollback` as the immediate incident response action.
-
-## Output Contract
-
-- CLI authentication and project linking steps
-- Environment variable management workflow
-- CI/CD pipeline CLI integration commands
-- Relevant flags and flags rationale
-- Rollback procedure and verification steps