migrate-imports
Find and replace all @keystone-6 import paths across every file in the project. Invoke as a forked subagent, passing the project root path.
What this skill does
Find and replace all KeystoneJS import paths with their OpenSaaS Stack equivalents across the project described below. This is a mechanical find-and-replace across every TypeScript/JavaScript file.
$ARGUMENTS
## Import Mapping
| Keystone import (remove/replace) | OpenSaaS import |
| ---------------------------------------- | ------------------------------------------ |
| `@keystone-6/core` | `@opensaas/stack-core` |
| `@keystone-6/core/fields` | `@opensaas/stack-core/fields` |
| `@keystone-6/auth` | `@opensaas/stack-auth` |
| `@keystone-6/fields-document` | `@opensaas/stack-tiptap/fields` (see note) |
| `.keystone/types` or `'.keystone/types'` | `@opensaas/stack-core` |
| `@keystone-6/core/session` | Remove entirely (handled by authPlugin) |
**Note on `@keystone-6/fields-document`**: Replace with `@opensaas/stack-tiptap/fields` and change `document()` → `richText()`. If document field migration is complex, note it for the user and leave a `// TODO: migrate document field` comment.
**Note on `.keystone/types`**: Common imports to update:
```typescript
// Before
import type { Session } from '.keystone/types'
import type { KeystoneContext } from '.keystone/types'
import type { Lists } from '.keystone/types'
// After
import type { AccessControl } from '@opensaas/stack-core'
// KeystoneContext and Lists are no longer needed — use context from getContext()
```
## Config File Rename
If the project has `keystone.ts` or `keystone.config.ts`, it should be renamed to `opensaas.config.ts`. Check if it has already been renamed before doing so.
## Steps
1. Use Glob to find all `.ts` and `.tsx` files in the project (exclude `node_modules`, `.next`, `dist`)
2. Use Grep to identify which files contain `@keystone-6` or `.keystone/types` imports
3. For each affected file:
a. Read the file
b. Apply the import replacements from the table above
c. For `.keystone/types` imports, update the specific type names (Session → AccessControl, etc.)
d. Edit the file with the changes
4. Check if `keystone.ts` or `keystone.config.ts` exists and rename to `opensaas.config.ts` if needed (and if not already done)
5. Report: list every file changed and what was replaced
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce 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).
relationship-science-coach
IncludedUse 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.
building-sf-integrations
IncludedSalesforce 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).
venue-templates
IncludedAccess 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.
let-fate-decide
IncludedDraws 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.
net-ops
IncludedCross-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.