apx

Organize backend APIs, React UI, and local dev workflows for Databricks Apps.

1|Updated Feb 18, 2026

Search Tags:#debugging #react #fastapi #openapi #shadcn/ui #apx #databricks apps

Ready to run

npx skills add https://github.com/neo4j-partners/databricks-retail-assistant --skill apx-neo4j-partners

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: apx
Source: https://github.com/neo4j-partners/databricks-retail-assistant/tree/main/demo-client/.agents/skills/apx
Command: npx skills add https://github.com/neo4j-partners/databricks-retail-assistant --skill apx-neo4j-partners

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

apx removes the guesswork from building and maintaining full-stack Databricks Apps by giving you a consistent workflow for backend APIs, React frontends, local development, and deployment.

Core Features & Use Cases

API and route discovery: Quickly inspect available endpoints and generated hooks before editing backend or frontend code.
Pattern-driven development: Follow the provided backend and frontend conventions for Pydantic models, FastAPI routers, Suspense-based data loading, and shadcn/ui components.
Dev server and debugging workflow: Manage local servers, check logs, refresh OpenAPI, and validate changes with the recommended checks.
Use case: Ideal when adding a new FastAPI route, wiring a React page to a generated query hook, or troubleshooting a Databricks App during development or deployment.

Quick Start

Use the apx skill to identify the routes and patterns you need, then apply the recommended workflow to make and verify your Databricks App change.

Frequently Asked Questions about apx

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

FAQPage Schema

How do I build a full-stack Databricks App with React and FastAPI?▼

Build a full-stack Databricks App by using apx to organize backend API routes, wire React UI components with generated hooks, and manage local dev workflows. It enforces project patterns for Pydantic models, FastAPI routers, and Suspense-based data fetching.

What is the recommended workflow for adding a new FastAPI route to a Databricks App?▼

Adding a FastAPI route requires following pattern-driven development: define Pydantic models, create FastAPI routers, regenerate OpenAPI schemas, and wire the React frontend to the newly generated query hooks using Suspense-based data loading.

Does apx work with shadcn/ui components and Suspense for data fetching?▼

Yes, apx works with shadcn/ui components and Suspense-based data fetching. It provides conventions for wiring React pages to generated query hooks and applying shadcn/ui components within your Databricks App frontend architecture.

How do I debug a Databricks App during local development and deployment?▼

Debug a Databricks App by managing local dev servers, checking logs, refreshing OpenAPI specifications, and validating changes using the recommended checks provided by the apx workflow before deployment.

Can I inspect available endpoints and generated hooks before editing my FastAPI backend?▼

Yes, you can inspect available endpoints and generated hooks before editing. apx provides API and route discovery features so you can quickly review existing FastAPI routes and React query hooks prior to backend or frontend modifications.

What's the best way to manage OpenAPI regeneration when updating FastAPI routes?▼

The best way to manage OpenAPI regeneration is through the apx dev server workflow, which handles refreshing OpenAPI schemas and validating changes after you update FastAPI routers or Pydantic models in your Databricks App.