The dynapi-site-dev skill
A skill is a knowledge package for a coding agent: how DynapiCMS is structured, what its rules and recipes are. With the skill, the agent builds the site according to the platform’s canon (a site is made of flows, content lives in the CMS, draft → preview → publish) instead of inventing the structure itself.
Where to get it
The skill is open and lives at a single address:
https://dynapi.ru/cms/agent-skill/
SKILL.md— the entry point: platform rules and the “golden” axioms.references/— reference docs: the API (api-reference.md), flows (flows-guide.md), the Liquid dialect (liquid-guide.md), member-account sign-in (member-auth.md), error codes and quotas (conventions.md), forms (forms-flow.md), the store front (shop-wizard.md— what the «Магазин» wizard installs, its traps, and the storefront design canon), the wizard catalog (wizards.md— every installer card: what it puts on the tenant and how a re-run behaves), step-by-step recipes (workflows.md).cli/— flowctl binaries for Linux and Windows.
A human hands the agent the link and the key — the skill deliberately
contains no secrets. The endpoint URL is the same for everyone:
https://dynapi.ru/cms/graphql — the agent only needs the key.
How to connect it
The simplest way is to give the agent the link and the environment variables. Setup happens on your side.
Linux and macOS:
export DYNAPI_URL="https://dynapi.ru/cms/graphql"
export DYNAPI_APIKEY="dca_…"
Windows (PowerShell):
$env:DYNAPI_URL = "https://dynapi.ru/cms/graphql"
$env:DYNAPI_APIKEY = "dca_…"
The task for the agent — in your own words:
The DYNAPI_URL and DYNAPI_APIKEY variables are already set in the environment — use them and work through flowctl. Skill: https://dynapi.ru/cms/agent-skill/. Task: build a landing page for a studio, here is the brief.
The agent downloads SKILL.md and the reference docs it needs from
references/ as it works — there is no need to read all 4,000 lines up
front. A key kept in an environment variable never lands in the chat
history — safer than pasting it into the task text.
The old-fashioned way works too: save the skill files into the agent’s
project (for example, .agents/skills/dynapi-site-dev/) — the format is
compatible with Claude Code, Cursor, and other agents that read
SKILL.md.
What the skill instills
Key rules the agent receives with the skill:
- A site is made of flows. Every page, form, or handler is a flow bound to a route. A route with a GET binding is a page.
- Content lives in the CMS, not in templates. Templates hold only markup and styles; every visible sentence is a record in a content type, edited from the admin panel without rebuilding the site.
- Draft → preview → publish. Everything is first written as a draft, checked on the preview host, and only then rolled out to visitors.
- Errors are machine codes. Instead of walls of English text, the API
returns codes like
SITE_QUERY_IN_USE— the agent reads the code and fixes the specific thing. - Check before publishing.
flowctl validateanddryrunexercise flows locally and on the server before a visitor sees the result. - Everything through flowctl. The site inventory, files, routes, the query library, content, and media are all covered by CLI commands — hand-rolled GraphQL stays the fallback for rare operations flowctl does not cover yet.
Presets
Ready-made flows — sign-in, registration, password reset, a standard page — ship with the admin panel as “Presets” (see Presets, export, and import). The agent applies them via import mutations instead of assembling them by hand — sign-in scenarios are too sensitive to build from scratch.