Third-Party Integrations
Relevant source files
The following files were used as context for generating this wiki page:
- plugins/spec-kit-skill/skills/spec-kit-skill/SKILL.md
- skill/notion-knowledge-capture/notion-knowledge-capture/SKILL.md
- apps/client/src/prompts/system_prompt.ts
- Comprehensive.md
- tests/e2e/snapshots/chat_mode.spec.ts_chat-mode-selector---ask-mode-1.txt
- skill/notion-knowledge-capture/notion-knowledge-capture/reference/team-wiki-database.md
Third-party integrations in the bl1nk platform provide extended capabilities by connecting the AI editor to external development tools, cloud services, and knowledge management platforms. These integrations allow users to manage infrastructure, synchronize documentation, and automate development workflows directly from the chat interface.
The integration system is designed to be modular, often triggered by specific user prompts or the presence of integration-specific configuration files in the project directory. For instance, integrations like Supabase are handled through specialized UI components and conditional logic within the AI's system prompt to ensure that authentication and database requirements are met before development proceeds.
Sources: apps/client/src/prompts/system_prompt.ts, tests/e2e/snapshots/chat_mode.spec.ts_chat-mode-selector---ask-mode-1.txt, Comprehensive.md
Core Integration Architecture
The platform uses a "Skill" based architecture for third-party integrations. Each integration typically consists of a skill definition that outlines triggers, available commands, and the data flow between the AI agent and the third-party service.
Integration Flow logic
When a user requests a feature requiring an external service (e.g., database, auth, or hosting), the system follows a specific detection and setup flow:
The AI agent is instructed to stop and request integration setup if a user asks for features like Supabase before the provider is added to the application.
Sources: tests/e2e/snapshots/chat_mode.spec.ts_chat-mode-selector---ask-mode-1.txt, apps/client/src/prompts/system_prompt.ts:460-475
Supported Providers and Tools
The platform integrates with several primary categories of third-party tools, including cloud infrastructure, version control utilities, and knowledge bases.
| Provider | Type | Primary Purpose |
|---|---|---|
| GitHub Spec-Kit | Workflow/CLI | Constitution-driven spec-driven development. |
| Supabase | Backend/BaaS | Database, authentication, and server-side functions. |
| Notion | Knowledge Base | Capturing chat context into structured documentation. |
| Vercel | Hosting/PaaS | Deployment and preview environments. |
| AWS Bedrock | AI/LLM | LLM provider integration for skill generation. |
Sources: plugins/spec-kit-skill/skills/spec-kit-skill/SKILL.md, Comprehensive.md:21-25, tests/e2e/snapshots/chat_mode.spec.ts_chat-mode-selector---ask-mode-1.txt
Notion Knowledge Capture
The Notion integration transforms conversation context into structured wiki pages or database entries. It focuses on documentation discoverability and organization.
Knowledge Capture Process
The integration follows a six-step workflow to ensure information is not "orphaned" within the Notion workspace:
- Extract Content: Identifying key insights from chat.
- Determine Type: Classifying as Concept, How-to, Decision, or FAQ.
- Structure: Applying templates based on the identified type.
- Determine Destination: Searching for the correct wiki or project page.
- Create Page: Executing the
Notion:notion-create-pagestool. - Make Discoverable: Updating hub pages or parent project sections with links.
Sources: skill/notion-knowledge-capture/notion-knowledge-capture/SKILL.md:14-68
Notion Database Schema Example
Integrations often target specific Notion databases with predefined schemas for consistency.
| Property | Type | Purpose |
|---|---|---|
| Title | title | The name of the captured page. |
| Section | select | Wiki organization (e.g., Tools, Reference). |
| Tags | multi_select | Topic-based categorization. |
| Owner | people | The maintainer of the captured knowledge. |
Sources: skill/notion-knowledge-capture/notion-knowledge-capture/reference/team-wiki-database.md:5-15
GitHub Spec-Kit Integration
The Spec-Kit integration facilitates constitution-driven development by wrapping the GitHub Spec-Kit CLI. It manages a 7-phase workflow stored within a .specify/ directory.
CLI and Environment Setup
The integration requires specific environment tools to function, primarily the uv package manager and Python 3.11+.
# Verification of CLI installation
command -v specify || echo "Not installed"
# Installation via uv
uv tool install specify-cli --from git+https://github.com/github/spec-kit.git
Sources: plugins/spec-kit-skill/skills/spec-kit-skill/SKILL.md:25-35
Spec-Kit Lifecycle
The integration automates transitions between development phases, creating files in the .specify/specs/NNN-feature-name/ directory.
Infrastructure and Secrets Management
Integrations that require cloud resources (AWS, Vercel, etc.) rely on GitHub Secrets for secure credential storage during CI/CD operations.
Required Integration Secrets
| Secret Category | Key Names |
|---|---|
| Cloud Services | AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION |
| Monitoring | CODECOV_TOKEN, SNYK_TOKEN, SONAR_TOKEN |
| Notifications | SLACK_WEBHOOK_URL |
| Container Registry | GHCR_TOKEN |
Sources: Comprehensive.md:146-166
Summary
Third-party integrations are a critical extension of the bl1nk platform, enabling it to act as a full-stack development orchestrator. By combining specialized skills (like Notion Knowledge Capture) with infrastructure providers (Supabase, AWS) and workflow tools (GitHub Spec-Kit), the system maintains a structured development lifecycle from initial principles to production deployment.