Skill-Details
docyrus-platform
Conceptual architecture reference for apps on Docyrus only.
Vor Nutzung prüfen
Die automatische Prüfung bewertet Relevanz, nicht Sicherheit oder Empfehlung. Lies vor der Nutzung die Quellanweisungen.
SKILL.md
Dieser Auszug wurde bei der Prüfung gespeichert. Die externe Quelle enthält die vollständige und aktuelle Version.
---
name: docyrus-platform
description: Architecture and building-blocks reference for the Docyrus platform — what the platform is made of (apps, data sources, fields, enumerations, custom queries, automations) and how the pieces fit together. Use when you need conceptual context about how Docyrus works, what its building blocks and capabilities are, or to decide which dedicated skill to use for a task. This is the conceptual map and router; hands-on how-to lives in the dedicated design / CLI / API skills it points to (data sources, automations, agents, AI tools, templates, webforms, ACL, querying, the CLI, and the REST API).
---
# Docyrus Platform
Docyrus is an AI-native Backend Platform as a Service (BPaaS) for building B2B web/mobile apps, client portals, internal tools, AI agents, chatbots, and integrations — without building backend infrastructure from scratch. This skill is the **architecture map**: the building blocks, how they fit, and which dedicated skill owns each how-to.
## Core Building Blocks
The platform is composed of building blocks that compose into apps:
- **Apps** — Top-level containers that group data sources, automations, agents, and custom queries into a deployable unit.
- **Data Sources** — Structured collections of records with typed schemas. Four types: simple, advanced, external (connected DBs/APIs), and system (pre-built). Every data source — internal or external — is exposed through one unified CRUD endpoint.
- **Fields** — 45+ field types defining each data source's schema: text, numbers, dates, selections, relations, files, formulas, nested data, and more.
- **Enumerations** — Reusable option sets for selection fields (color, icon, ordering).
- **Custom Queries** — SQL-based analytics templates with variable interpolation, runtime filters, and multi-database targeting.
- **Automations** — Event-driven workflows: triggers (record changes, schedule, webhook, email, webform, button) → action-node chains (email, notifications, record ops, HTTP, AI, scripts).
Detailed building-block specifications: [references/core-building-blocks.md](references/core-building-blocks.md).
## Which skill for which task
This skill holds the *concepts*. For doing the work, use the dedicated skill:
| To… | Use skill |
|---|---|
| Design a data source (schema, fields, relations, enums, access) | **docyrus-data-source-design** |
| Build an automation (triggers + action-node graph) | **docyrus-automation-design** |
| Build a custom AI agent + its sub-resources | **docyrus-agent-design** |
| Author AI tools the system base agent ("Docy") calls | **docyrus-app-ai-tools** |
| Design an email template | **docyrus-email-template-design** |
| Design an HTML/PDF print/report template | **docyrus-print-pdf-template-design** |
| Build a public webform that collects submissions into records | **docyrus-webform-design** |
| Configure tenant ACL (roles, hierarchy units, role rules) | **docyrus-acl-design** |
| Discover & call third-party integrations/connectors (`docyrus connect`) | **docyrus-integrations-and-connectors** |
| Query/CRUD data, write filters/formulas, build query payloads | **docyrus-api-dev** |
| Write DSQL (logical SQL) queries, or natural-language `dsql ask` | **docyrus-dsql-query-design** |
| Drive everything from the terminal (auth, ds, studio, automation, agent, …) | **docyrus-cli-app** |
| Build a React app on Docyrus (collections, grids, forms) | **docyrus-app-dev-react**, **docyrus-data-grid-page-design**, **docyrus-record-detail-form-design** |
## Capability areas (concepts)
### Querying & Data Operations
Unified query engine: column selection, 50+ filter operators, aggregations, formulas, pivots, child queries, full-text search; full CRUD with bulk ops, comments, and attachments; plus a read-only logical SQL endpoint (DSQL) over `appSlug.dataSourceSlug` tables. Concept overview: [references/querying-and-data-operations.md](references/querying-and-data-operations.md).
→ Query payloads & formulas: **doVollständige Quelle auf GitHub lesen (öffnet externe Seite)