Create an interactive web-based recreation of Airtable that feels like the real product in daily use, not a static mockup or a generic spreadsheet demo. Visitors land in a working base with several believable, richly seeded tables and can immediately do real work: browse and edit records, reshape the schema, switch views, and explore the interface the way an Airtable user would.
Recreate the core grid with close fidelity. Cells should honor their field types — single line text, long text, number, currency, percent, single select, multiple select, checkbox, date, URL, email, phone, rating, and linked-record-style references — each with its authentic display treatment, inline editor, and commit/cancel behavior. Support the interaction texture that makes the grid feel like Airtable: click to select, double-click or Enter to edit, Escape to cancel, arrow-key and Tab navigation, Shift-based range selection, copy and paste, row hover states with checkboxes and the expand icon, the frozen primary field, column resizing and reordering by drag, row drag reordering, right-click context menus for rows and fields, and the expanded record modal with its full field list, navigation between records, and long-text editing. Include field creation and configuration flows with type-specific options (select colors and option management, number precision, date formatting, rating icons), field renaming, duplication, hiding, and deletion with confirmation.
Carry the experience through Airtable's surrounding chrome and views. Recreate the top bar with the base identity, the table tabs strip with add/rename/reorder, the view sidebar with view creation and switching, and the view toolbar: hide fields, filter (with multiple conditions and and/or logic), group (with collapsible group headers and aggregates), sort (multi-level), color by select field, row height control, and search that highlights matches. Beyond the grid, implement kanban grouped by a select field with drag-and-drop between stacks, a gallery of record cards, a calendar placing records by date field with month navigation, and a form view that renders the table's fields and appends submitted records. Records, schema, and view configurations should stay consistent across every view, and changes should persist across reloads.
Match Airtable's look and feel: its visual proportions, color palette, typography, iconography rhythm, spacing, subtle borders and shadows, hover and focus treatments, selection highlights, transition timing, and the characteristic feel of its menus, popovers, and modals. Include the quieter states that make the product feel inhabited — empty tables, empty filter results, new-view defaults, confirmation dialogs, toasts for destructive actions with undo, and sensible keyboard shortcuts — alongside record creation, duplication, and deletion, and undo/redo for edits.
Do not take shortcuts, substitute a cookie-cutter table template, or stop at a recognizable shell. This skill imposes no token budget limit, so pursue the recreation down to the smallest meaningful interactions — the way a select tag renders, the way a cell enters edit mode, the way a group collapses — and continue refining its behavior, states, transitions, edge cases, and visual fidelity until the clone feels complete, cohesive, and convincingly faithful to Airtable.
