astrale-domain
Create, modify, test, migrate, or debug Astrale Domains: Schema, Policies, Action/Workflow runtime, integrations, Views, Datasets, and deployment. For a new Domain follow the phased workflow; for focused work load only the relevant references.
How do I install this agent skill?
npx skills add https://github.com/astrale-os/cli --skill astrale-domainIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides a comprehensive set of documentation and instructions for managing the lifecycle of services on the Astrale platform. It includes guides for schema design, policy enforcement, deployment, and debugging, using standard development tools and practices. No security risks were identified.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
Astrale Domain
Load only the references the task needs.
Kernel boundary
- Domain source imports Core and DSL authoring values only through the matching
@astrale-os/sdk/*subpath: never@astrale-os/kernel-coreor@astrale-os/kernel-dsl, never a flat SDK root barrel. - Authorization is the Kernel's: Schema Policies, the callable
authmode, and the Kernel Roles and scopes the release requests. Handlers run only admitted calls and never re-decide them. - Writes go through the Domain's callables as
executor; Classcreate/update/deleteslots stay absent (references/policies.md). - The installed SDK's public exports and the current Domain source are authoritative for API syntax, over memory. The SDK's Domain linter and executable evidence are the guardrails.
Intent router
| Task | Read |
|---|---|
| Scaffold, TypeScript, Environments, local test setup | references/development.md |
| Deploy, install, publish or yank a version, roll back, rotate a deployment's secret, own a development instance | references/deployment.md |
| Schema: vocabulary, Properties, Class/Edge choices, inheritance, keys, Edge lifetimes, Methods; always for Schema work | references/schema.md |
| An Action handler; Action vs Workflow vs no callable; calling another callable or Domain | references/actions.md |
Read the graph: a Query, relations, .reachable(), pages, counts, limits, V6 → v7 | references/queries.md |
| Write the graph: a Mutation, guards, refusals, transitions | references/mutations.md |
Whose authority a call uses (executor/caller, .self/.caller), Identities, composition | references/authority.md |
Files: blob Properties, file() input fields, upload receipts, astrale call --file | references/files.md |
| Several effects, a wait, a signal; write, test, call, deploy or migrate a Workflow | references/workflows.md |
| An external API, an Integration/Provider, webhooks, side-effect and retry design | references/integrations.md |
| Reuse or depend on another Domain instead of modelling its vocabulary | references/domains.md |
| People who sign in: link a business record to their Shell account, create or invite accounts, declare Domain Roles and Teams, grant Roles, instance administrators | references/users.md |
| Secure a callable, View, client call or public endpoint; auth modes, Policies, Class rules, scopes | references/policies.md |
| Which Kernel Role an operation needs; which Roles a Domain declares or a person holds; bundles, granting | references/roles.md |
| The Domain's icon: sizes, artboards, layers, dark variant, accepted SVG | references/icons.md |
Views, mounted UI, View access and resolution (and astrale-frontend-design for layout, interaction, copy) | references/views.md |
| Schema revision, data transition, backfill, breaking change (Root maintenance session), install follow-up, refused data, uninstall with data | references/migration.md |
| Round trips, Query shape and cost, call-pattern latency | references/performance.md |
Demo data: the Datasets under tests/ the Studio draws and proves Policies on | references/datasets.md |
| Tests, fixtures, demo flows, smoke scenarios | references/testing.md |
| A failing live Domain, issuer/discovery confusion, invocation routing, runtime drift | references/debugging.md |
Code or an instance still on a previous model (a deprecated SDK API, legacy requirements, a Shell before Roles); an upgrade across a breaking change | references/legacy/LEDGER.md: the row naming that model, then its guide; for a deprecated SDK API, also the installed SDK's docs/legacy/ (node_modules/@astrale-os/sdk/docs/legacy/). Never start new work from a legacy guide |
New Domain
Follow the applicable phases in order; load a reference when its phase begins.
- Foundation: inspect the workspace. Without a public scaffold, read
references/development.md(references/domains.mdonly to decide whether to reuse a native Domain). A workspace already declaring the SDK, deployment adapter, Domain definition and Runtime keeps that plumbing. - Schema:
references/schema.md; for people who sign in, Roles and Teams,references/users.mdbefore inventing identity or onboarding vocabulary. - Callables:
references/actions.md,references/authority.md,references/policies.md,references/roles.md, thenreferences/queries.mdandreferences/mutations.md;references/workflows.mdfor several effects or a wait;references/integrations.mdfor an external system. - Views: when the Domain owns a browser surface,
references/views.md. Views are Schema declarations owned by their Domain; a Node screen is an internal route of its frontend. - Demo data: for a meaningful sample graph, a small Dataset under
tests/, referenced fromastrale.config.ts(references/datasets.md). None for an API-only Domain or a focused edit. - Completion:
references/testing.md. Exercise each delivered public callable with representative success and refusal inputs; run tests, typecheck, lint and build. Verify packaging when delivering a package, and live behavior when claiming deployment or integration success.
references/migration.md, references/performance.md and references/debugging.md only when the
Domain's lifecycle or the current problem calls for them.
Always
- Inspect the current repo or scaffold before trusting API syntax from memory.
- Live behavior: prove the deployed, installed and running path (
references/debugging.md) before treating a source edit as effective. - A Schema change affecting existing Datasets keeps them valid and representative in the same
change (
references/datasets.md). - A problem that blocks, costs significant time or forces an unsatisfactory workaround and points
to Astrale rather than the Domain: report it with
astrale issue(astrale-cliskill).
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/astrale-os/cli/astrale-domain">View astrale-domain on skillZs</a>