> ## Documentation Index
> Fetch the complete documentation index at: https://doc.codika.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Builder Reference

> Plugin structure, bundled documentation catalog, agent invocation details, and troubleshooting

## Plugin structure

The Builder System ships inside a single [Open Plugin v1](https://github.com/vercel-labs/open-plugin-spec) repo at [`codika-io/plugin`](https://github.com/codika-io/plugin). One plugin, 25 skills, 4 agents:

```
codika/
├── .plugin/plugin.json               # Vendor-neutral manifest (Open Plugin v1)
├── .claude-plugin/plugin.json        # Claude Code preferred manifest
├── skills/                           # 25 skills, namespaced `/codika:*`
│   ├── setup-codika/                 # Install and authenticate CLI
│   ├── create-organization/          # Create organizations
│   ├── create-organization-key/      # Create org API keys
│   ├── update-organization-key/      # Update org API keys
│   ├── create-project/               # Create projects
│   ├── list-projects/                # List projects
│   ├── get-project/                  # Fetch project details
│   ├── init-use-case/                # Scaffold new use cases
│   ├── verify-use-case/              # Validate use cases
│   ├── deploy-use-case/              # Deploy to platform
│   ├── rerun-deployment/             # Rerun deployment with new params
│   ├── publish-use-case/             # Promote to production
│   ├── fetch-use-case/               # Download deployed use cases
│   ├── deploy-documents/             # Upload stage documents
│   ├── deploy-data-ingestion/        # Deploy RAG pipelines
│   ├── trigger-workflow/             # Trigger workflows
│   ├── get-execution/                # Debug execution traces
│   ├── list-executions/              # List recent executions
│   ├── list-instances/               # List process instances
│   ├── get-instance/                 # Fetch instance details
│   ├── instance-activate/            # Activate/deactivate instances
│   ├── manage-integrations/          # Configure credentials
│   ├── manage-notes/                 # Manage project notes
│   ├── get-skills/                   # List platform skills
│   └── discover-codika-guides/       # Locate bundled platform docs
│       └── references/               # Bundled platform documentation
└── agents/                           # 4 agents, Task `subagent_type: "codika:*"`
    ├── use-case-builder.md           # Architect — creates new use cases
    ├── use-case-modifier.md          # Surgeon — modifies existing use cases
    ├── n8n-workflow-builder.md       # Craftsperson — builds workflow JSON
    └── use-case-tester.md            # QA — deploy-trigger-fix loops
```

## Bundled documentation catalog

The `discover-codika-guides` skill ships with the complete platform documentation. Agents read these guides at runtime to ensure they follow current patterns.

### Core guides

| Guide                         | What it covers                                                                                |
| ----------------------------- | --------------------------------------------------------------------------------------------- |
| `use-case-guide.md`           | Overall architecture, mandatory patterns, placeholder system, trigger types, config structure |
| `specific/config-patterns.md` | config.ts structure, exports, workflow array, integration UIDs, display metadata              |
| `specific/codika-nodes.md`    | Codika Init, Submit Result, Report Error, Upload File node configuration                      |

### Trigger-specific guides

| Guide                              | What it covers                                                          |
| ---------------------------------- | ----------------------------------------------------------------------- |
| `specific/http-triggers.md`        | HTTP webhook and form trigger patterns                                  |
| `specific/schedule-triggers.md`    | Cron/scheduled trigger patterns                                         |
| `specific/third-party-triggers.md` | Gmail, Slack, WhatsApp, Pipedrive, Calendly service event triggers      |
| `specific/sub-workflows.md`        | Reusable workflow logic, Execute Workflow pattern, SUBWKFL placeholders |

### Specialized guides

| Guide                              | What it covers                                                             |
| ---------------------------------- | -------------------------------------------------------------------------- |
| `specific/ai-nodes.md`             | chainLlm vs agent nodes, LangChain wiring, model configuration, \$fromAI() |
| `specific/placeholder-patterns.md` | Complete reference for all 11 placeholder types with suffix patterns       |
| `specific/process-input-schema.md` | Deployment parameters (INSTPARM), field types, context-aware serialization |
| `specific/data-ingestion.md`       | RAG/document embedding pipeline configuration                              |
| `specific/agent-skills.md`         | Creating SKILL.md files for agent discoverability                          |

### Integration guides (19)

| Category                    | Integrations                                                                                    |
| --------------------------- | ----------------------------------------------------------------------------------------------- |
| **AI providers** (FLEXCRED) | Anthropic, OpenAI, Tavily, xAI, OpenRouter, Mistral, Cohere, DeepSeek, Fal AI                   |
| **Organization** (ORGCRED)  | WhatsApp, Slack, Twilio, Folk CRM, Pipedrive                                                    |
| **User** (USERCRED)         | Google (Gmail, Sheets, Drive, Calendar), Microsoft (Teams, Outlook, OneDrive), Calendly, Notion |
| **Instance** (INSTCRED)     | Supabase                                                                                        |

### Additional resources

| Resource                         | What it covers                                                         |
| -------------------------------- | ---------------------------------------------------------------------- |
| `plan-examples/`                 | Example build plans showing how the builder agent designs architecture |
| `post-creation/common-errors.md` | Common issues after creating workflows and how to fix them             |
| `use-case/whatsapp-bots.md`      | WhatsApp bot-specific patterns and conventions                         |

## Agent-to-skill dependency map

Each agent uses a specific set of skills from the same `codika` plugin (all skills and agents are colocated):

| Agent                           | Skills used                                                                                                                     |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **codika:use-case-builder**     | `codika:init-use-case`, `codika:verify-use-case`                                                                                |
| **codika:use-case-modifier**    | `codika:verify-use-case`                                                                                                        |
| **codika:n8n-workflow-builder** | *(none — outputs JSON directly)*                                                                                                |
| **codika:use-case-tester**      | `codika:deploy-use-case`, `codika:trigger-workflow`, `codika:list-executions`, `codika:get-execution`, `codika:verify-use-case` |

All agents read platform documentation via `codika:discover-codika-guides` before starting work.

## Troubleshooting

### Authentication errors

If agents fail with "API key is required" or authentication errors, run:

```bash theme={null}
codika login
codika whoami  # verify you're authenticated
```

### Missing codika plugin

The builder agents depend on the `codika` plugin for CLI operations. If deployment or verification skills fail, ensure both plugins are installed.

### Guide not found

If an agent can't find documentation, verify the `discover-codika-guides` skill is available. The skill locates guides using glob patterns against its bundled `references/` directory.

### Validation failures after building

If `codika verify use-case` fails after the builder creates a use case:

1. Read the specific error messages — they usually point to the exact issue
2. Use `codika verify use-case <path> --fix` to auto-fix common violations
3. For persistent issues, invoke `use-case-modifier` with the error details

### Tester stuck in loop

If `use-case-tester` hits its 5-iteration limit:

* Check the escalation report for what was tried
* Common root causes: missing OAuth credentials on the platform, external API rate limits, or integration-specific configuration issues that the agent can't resolve
* Verify integrations are configured: `codika integration list`
