scaffold-extension

To scaffold an Airtable extension project, run the scaffold script to automate project directory creation, git initialization with Airtable identity, and environment templating. This process creates a reproducible starter for extension development across local environments and GitHub integration.

Setting up an Airtable extension development environment requires a local ~/work directory with a templates folder and an executable ~/work/new-extension.sh script. You also need GitNexus configured and gh authentication for GitHub repository integration.

Yes, you can automatically create a private GitHub repository during Airtable extension scaffolding. The setup optionally creates a private GitHub repository and wires up the remote origin using your configured gh authentication.

GitNexus integration works by running index scanning during the Airtable extension scaffolding process. This provides code context for Claude Code, enabling better development assistance within the newly created extension project.

Yes, the Airtable extension scaffolding process protects local secrets by copying template .gitignore and .env.example files. It creates a local .env file for development use while ensuring sensitive environment variables are excluded from git tracking.

The best way to ensure reproducible Airtable extension setups is using an automated scaffolding script with environment templating. This standardizes git initialization, secrets protection, and GitNexus indexing, providing a consistent starter for extension development across local environments.