migrate-virtual-fields

Included with Lifetime

$97 forever

Migrate Keystone virtual fields to OpenSaaS Stack format. Invoke as a forked subagent when virtual fields are detected, passing the config file path and field details as arguments.

General

What this skill does


Migrate the virtual fields described below to OpenSaaS Stack format. OpenSaaS Stack has no GraphQL — virtual fields use `hooks.resolveOutput` with a `type` declaration instead of `graphql.field()`.

$ARGUMENTS

## Migration Pattern

For every virtual field, apply this transformation:

**Before (Keystone):**

```typescript
import { graphql } from '@keystone-6/core'

fieldName: virtual({
  field: graphql.field({
    type: graphql.String, // or graphql.Int, graphql.Boolean, etc.
    resolve: (item, args, context) => someValue,
  }),
})
```

**After (OpenSaaS Stack):**

```typescript
fieldName: virtual({
  type: 'string', // see type mapping below
  hooks: {
    resolveOutput: ({ item, context }) => someValue,
  },
})
```

## Type Mapping

| Keystone `graphql.*`            | OpenSaaS `type`                            |
| ------------------------------- | ------------------------------------------ |
| `graphql.String`                | `'string'`                                 |
| `graphql.Int` / `graphql.Float` | `'number'`                                 |
| `graphql.Boolean`               | `'boolean'`                                |
| `graphql.list(graphql.String)`  | `'string[]'`                               |
| Custom object type              | `{ value: MyClass, from: 'package-name' }` |

For custom/imported types (e.g. Decimal):

```typescript
import Decimal from 'decimal.js'

totalPrice: virtual({
  type: { value: Decimal, from: 'decimal.js' },
  hooks: {
    resolveOutput: ({ item }) => new Decimal(item.price).times(item.quantity),
  },
})
```

## Context Queries Inside resolveOutput

If the original `resolve` used `context.query.*` or `context.db.*`, replace with `context.db.*`:

```typescript
// Before
resolve: async (item, _, context) => {
  return context.query.Post.count({ where: { author: { id: { equals: item.id } } } })
}

// After
resolveOutput: async ({ item, context }) => {
  return context.db.post.count({ where: { authorId: { equals: item.id } } })
}
```

## Steps

1. Read the config file to find all `virtual()` field definitions
2. For each virtual field:
   a. Identify the `graphql.*` type → map to the OpenSaaS `type` value
   b. Extract the `resolve` function body
   c. Rewrite as `hooks: { resolveOutput: ({ item, context }) => ... }`
   d. Replace any `context.query.*` calls with `context.db.*` equivalents
   e. Note: field arguments (`args`) are NOT supported — if the original used args, bake in a default or split into multiple fields
3. After all virtual fields are updated, remove any `graphql` imports from `@keystone-6/core` that are no longer used
4. Report: list each field that was changed and what the new definition looks like

Files: 1

Size: 2.9 KB

Complexity: 11/100

Category: General

Source: https://github.com/opensaasau/stack/tree/main/claude-plugins/opensaas-migration/skills/migrate-virtual-fields

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts