skills.rest
LearnCraft-Spanish
LearnCraft-SpanishOFFICIAL
Explore all skills by this author →
GitHub

quickbase-to-postgres

Migrate a QuickBase table into hexagonal architecture with audited legacy hooks.

2|Updated Sep 23, 2022
Search Tags:#migration#hexagonal architecture#tanstack query#ports and adapters#postgres#quickbase#shared domain types
One-click install
npx skills add https://github.com/LearnCraft-Spanish/learncraft-spanish --skill quickbase-to-postgres
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quickbase-to-postgres
Source: https://github.com/LearnCraft-Spanish/learncraft-spanish/tree/main/.claude/skills/quickbase-to-postgres
Command: npx skills add https://github.com/LearnCraft-Spanish/learncraft-spanish --skill quickbase-to-postgres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Moves one legacy QuickBase-backed table’s data access into the hexagonal architecture so the app stops relying on scattered src/hooks/ implementations and instead uses shared domain types and route contracts.

Core Features & Use Cases

  • Table-scoped migration: Migrates a single target table at a time, driven by a parent migration agent.
  • Legacy audit-first workflow: Locates all legacy data access for the table (hooks, hardcoded API paths, legacy types, and query usage) and reports findings before any build changes.
  • Hexagon implementation chain: Guides creation of domain/port/infrastructure/adapter/query layers using @learncraft-spanish/shared endpoint constants (no hardcoded paths).
  • Ambiguity handling: Detects tables that exist in both vocabQuizDb and studentRecordsDb (currently lessons) and explicitly asks which database to migrate from.

Quick Start

Tell the parent agent to run the QuickBase to Postgres Migration Skill for the specific table you want to move into hexagon (for example, “migrate students table”).

Frequently Asked Questions about quickbase-to-postgres

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate QuickBase tables to a hexagonal architecture with Postgres?▼

To migrate QuickBase tables to Postgres within a hexagonal architecture, this Skill audits legacy hooks and types for a single specified table, then implements ports, infrastructure, adapters, and TanStack Query hooks using shared domain types and route contracts.

What is the process for moving legacy QuickBase hooks into ports and adapters?▼

Moving legacy QuickBase hooks into ports and adapters requires an audit-first workflow that locates all existing data access and hardcoded API paths, then builds domain, port, infrastructure, and adapter layers using shared endpoint constants without hardcoding paths.

Can I migrate multiple QuickBase tables into the hexagon at the same time?▼

No, this Skill performs table-scoped migration of a single target table at a time, driven by a parent migration agent. It audits legacy data access for one table, reports findings to the parent, then implements the hexagon layers for that specific table.

How do I handle ambiguous table names when migrating from QuickBase to Postgres?▼

Handling ambiguous table names when migrating from QuickBase requires resolving the target via TABLES.md. When a table like 'lessons' exists in both vocabQuizDb and studentRecordsDb, the Skill explicitly prompts you to select which database to migrate from.

Do I need to use TanStack Query patterns when implementing hexagonal architecture for Postgres?▼

Yes, implementing hexagonal architecture for Postgres with this Skill requires using TanStack Query patterns and shared endpoint constants. It builds query hooks that depend on shared domain types and route contracts, avoiding hardcoded endpoint paths and UI logic.

What are the limitations of using ports and adapters for QuickBase database migration?▼

Limitations include single-table-only migration scope, exclusion of UI logic, and dependency on a parent migration agent for coordination. The Skill strictly handles data access layers and requires table resolution via TABLES.md when names are ambiguous across different databases.

Related Skills

Explore More Software Engineering Skills→
outfitter-devoutfitter-dev
6

migration

Audit code and generate migration plans for Outfitter Stack patterns.

Official
Advanced
RyoOsakaRyoOsaka

hook

Generate reusable React hooks for data fetching and logic with TanStack Query.

Community
Intermediate
imkdwimkdw
1

Backend Models

Design domain entities, DTOs, and mappers with static factory methods.

Community
Intermediate
jimmymalhanjimmymalhan
1

API Contract Check

Validate API endpoint implementations against a documented api.md contract.

Community
Intermediate