Concepts
How Veryfront framework primitives, conventions, and runtime fit together.
Concepts explain how Veryfront Code is organized and where each primitive
belongs. Start here when ownership, lifecycle, or framework boundaries are not
clear.
Documentation Index
Fetch the complete documentation index at: /docs/llms.txt
Use this file to discover all available pages before exploring further.
How Veryfront framework primitives, conventions, and runtime fit together.
| Concept | Explains |
|---|---|
| Veryfront Code | How the main framework surfaces fit together. |
| Framework primitives | Overview of framework primitives. |
| App | The user-facing route and rendering boundary. |
| Agent | The model reasoning loop and output boundary. |
| Tool | The contract for one callable capability. |
| Skill | How skills package reusable agent instructions. |
| Prompt | Reusable instruction templates for MCP. |
| Resource | Read-only context exposed through MCP. |
| Eval | Repeatable quality checks for agents. |
| Task | Background work before it becomes a run. |
| Workflow | Multi-step work with visible process state. |
| Run | Durable records for background execution. |
| Schedule | Triggers that create runs. |
| Integration | External service access, auth, and remote tools. |
| Salesforce integration | Why Salesforce is routed through Veryfront’s tool policy. |
| MCP server | Tools, prompts, and resources exposed to assistants. |
| Sandbox | Isolated command and file execution. |
| Framework conventions | File layout, auto-discovery, shared code, content, config. |
| Framework extensions | Replaceable runtime infrastructure. |