Apply shared conventions when working across apps in an Agent-Native workspace. The skill explains where shared and app-specific code, files, credentials, scratch notes, and runtime resources belong, and how to find documentation and source that match the framework version in use.
Shared conventions for a multi-app Agent-Native workspace: finding version-matched framework docs and source, shared vs app-owned code, file and blob storage, env and secrets, agent scratch files, and Dispatch Resources. Use when working across workspace apps, storing files or credentials, or looking up framework APIs.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
The long-form detail behind the workspace AGENTS.md core rules. Read this
before adding shared code, storing files or secrets, creating workspace
resources, or looking up framework APIs.
Read agent-native-docs for the lookup workflow (framework-search first, then
the focused docs-search / source-search readers, and the rg fallback).
The workspace-specific slugs it does not list are workspace and
multi-app-workspace. Feature flags and other specialized workflows are
optional; read their skill only when the app uses them. Use package docs for framework APIs,
the package corpus for reusable framework/template patterns, and this
AGENTS.md plus .agents/skills/ for workspace-specific conventions.
Before building common workspace or agent UI, read agent-native-toolkit to
inventory existing public kits and installed package seams. Read
customizing-agent-native before adapting shared UI. Use the supported
ladder: configure → compose → eject the smallest unit → propose a shared seam.
Preview before --apply, commit agent-native.ejections.json, and never edit
node_modules or eject protected runtime contracts.
generateText() / streamText(), or
other inline LLM APIs directly. Use sendToAgentChat() for local app-agent
work, including hidden context and submit: false prefill/review flows.
Keep actions deterministic and focused. If a workflow is framed as research,
analysis, generation, recommendation, or synthesis, let the agent
orchestrate provider/data actions in the open AgentSidebar instead of hiding
the work in one opaque action or a separate follow-up textbox.
Only use useAgentChatContext, setAgentChatContextItem,
listAgentChatContext, removeAgentChatContextItem, and
clearAgentChatContext when UI needs two-way sync with staged context chips.
Read .agents/skills/delegate-to-agent/SKILL.md before building agent-driven
UI or "AI" features.packages/shared only when multiple apps need it.apps/<app>.data: URLs, images, video/audio, PDFs,
ZIPs, screenshots, thumbnails, session replay chunks) in configured file/blob
storage and persist only URLs, ids, or handles..env; use
apps/<app>/.env only for app-specific overrides. For public app behavior,
prefer the default in agent-native.config.ts and use the deterministic
AGENT_NATIVE_CONFIG_<UPPER_SNAKE_PATH> alias only when a non-secret value
needs a deployment override. Never hardcode API keys,
tokens, webhook URLs, signing secrets, private Builder/internal data, customer
data, or credential-looking literals in source, docs, prompts, fixtures,
application state, action responses, or generated app content. Use
secrets/OAuth/runtime configuration and obvious placeholders in examples./* page function, and that function ships whatever
the app's server bundle depends on — including a dependency only a background
job uses. Before an app takes on a heavy runtime (headless browser, ffmpeg,
media processing, ML), read .agents/skills/performance/SKILL.md §9 and keep
that work in a background function or job. A dependency belonging to one app
does not belong in packages/shared.agent_scratch resources for temporary working
notes, scripts, task plans, or intermediate outputs, but should promote them
to normal workspace visibility only when the user explicitly asks to keep or
manage the file.AGENTS.md or instructions/<slug>.md for always-on guardrails,
skills/<slug>/SKILL.md for workspace skills, context/<slug>.md for
personas/positioning/messaging/company facts/brand guidelines, and
agents/<slug>.md for custom agent profiles. Scope them to All apps when
every workspace app should inherit them. All-app resources are inherited at
runtime; do not copy or sync them into individual apps.apps/.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Generate, refine, export, and place brand images or videos from an Assets library into another app. The skill covers choosing a library, handling image batches and video runs, and updating selected assets after feedback.
Prepare a customer account health, renewal, or contract usage readout. Verify the account identity, use approved metric definitions, compare contracted capacity with actual usage, and trace findings to sources, time windows, and known gaps.
Create focused app actions that agents can call as tools and frontend code can use through client hooks. Use them to add provider integrations or fetch UI data, with validated inputs and structured results.
Use this checklist when adding a feature or integration to an agent-native app. It covers the user interface, agent-callable actions, instructions, and app-state sync so both the user and agent can work with the capability consistently.
Investigate complex questions by combining data from multiple sources, then summarize patterns, metrics, and evidence in a clear report. Save requested analyses as dashboards with instructions for future refreshes.
Use the Analytics admin surfaces to inspect and change workspace feature flags, review dashboard ownership and usage activity, or browse and edit databases connected from other agent-native apps. The skill guides administrators to the relevant view and actions.