@agent-native/core 0.149.1 → 0.149.3

package/src/templates/workspace-core/.agents/skills/writing-agent-instructions/SKILL.md

@@ -43,9 +43,9 @@ A template `AGENTS.md` is injected into the runtime agent's system prompt and
 hard-sliced at `COMPACT_PROMPT_RESOURCE_MAX_CHARS` (6,000). Past that, the agent
 sees a truncation marker instead of your text, so the tail stops being
 always-on guidance and becomes something it has to go fetch. `pnpm
-the repository's `guard:agent-chat-context` check fails the build when a first-party
-file overflows; generated apps do not ship that repository-only guard. Keep files
-under ~5,500 so ordinary edits don't tip them over.
+guard:agent-chat-context` — the repository's own check — fails the build when a
+first-party file overflows; generated apps do not ship that repository-only
+guard. Keep files under ~5,500 so ordinary edits don't tip them over.
 
 Two consequences worth designing around:
 

package/src/templates/workspace-core/AGENTS.md

@@ -31,25 +31,18 @@ agent should know.
 
 - All AI/LLM behavior goes through the app's agent chat. UI and server code must
   not call model providers or AI SDK `generateText()` / `streamText()` directly;
-  use `sendToAgentChat()`. Keep actions deterministic and focused. If a
-  workflow is framed as research, analysis, generation, recommendation, or
-  synthesis, use `sendToAgentChat({ openSidebar: true })` to open the
-  AgentSidebar and let the agent orchestrate its provider/data actions. Keep
-  follow-ups in the same thread, not a second freeform textbox. Read
-  `.agents/skills/delegate-to-agent/SKILL.md` before building agent-driven UI or
-  "AI" features.
+  use `sendToAgentChat()`. Keep actions deterministic and focused. Research,
+  analysis, generation, recommendation, and synthesis open the AgentSidebar with
+  `sendToAgentChat({ openSidebar: true })` and stay in the same thread — never a
+  second freeform textbox. Read `delegate-to-agent` first.
 - Keep domain workflows on named routes and preserve the scaffold's full-page
-  chat route. Use the right `AgentSidebar` for contextual AI and open it when a
-  domain button hands work to the agent.
+  chat route.
 - Keep the first viewport focused: one primary action, progressive disclosure,
   concise copy, and domain-specific navigation. Never use sparkle, wand,
   magic, or robot icons as AI affordances.
 - Data loads use layout-matching `Skeleton` geometry, never a
   generic "Loading..." label. Reserve `Spinner` for brief mutations, uploads,
   and progress actions.
-- Use a sans-first SaaS hierarchy with one restrained visual cue; reserve serif
-  type for content previews. Give the AgentSidebar a subtle surface/divider
-  boundary, and stack original/generated review vertically by default.
 - Before visual work, read `frontend-design` and the workspace/app `DESIGN.md`.
   Keep shared chrome semantic and neutral, then choose an app-specific visual
   direction and palette family instead of copying a sibling app by default.
@@ -90,10 +83,8 @@ first-party template patterns ship with `@agent-native/core`. From an app
 directory, use `pnpm action docs-search --query "<topic>"` and
 `pnpm action source-search --query "<pattern>"`. Read `workspace-conventions`
 for slugs, the `--list` / `--slug` / `--path` options, and the `rg` fallback.
-
-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.
+Use package docs for framework APIs, the corpus for reusable patterns, and this
+file plus `.agents/skills/` for workspace-specific conventions.
 
 ## Actions