What problem does it solve? Building a full-stack Databricks application requires coordinating a FastAPI backend, a React frontend, auto-generated OpenAPI clients, and deployment tooling, which is error-prone without a structured workflow. ## Core Features & Use Cases - Structured six-phase workflow: Guides initialization, backend modeling, frontend development, testing, deployment, and documentation with time estimates and success criteria. - Backend and frontend code templates: Provides the three-model Pydantic pattern (EntityIn, EntityOut, EntityListOut), CRUD route conventions with operation_id, and React list/detail page templates with Suspense boundaries. - Best practices and debugging checklists: Documents anti-patterns, type-safety fixes, and common pitfalls like OpenAPI regeneration timing and shadcn component installation. - Use Case: A user asks for a Databricks app to track vendor invoices; the skill walks through APX initialization, creates invoice models and routes with mock data, generates list and detail pages, type-checks everything, and deploys via Databricks Asset Bundles. ## Quick Start Ask the agent to build a Databricks app using the APX framework for your chosen data entity, and it will initialize the project and scaffold the backend and frontend.
