@jskit-ai/agent-docs 0.1.149 → 0.1.151

package/skills/jskit/references/ui-operations.md

@@ -1,14 +1,16 @@
+<!-- Generated from `packages/agent-docs/site/guide/framework/ui-operations.md` by `npm run agent-docs:build`. -->
+
 # UI operations
 
 Read this for routes, pages, surfaces, placements, responsive UI, and browser
-verification.
+verification. Also read the complete [Material 3 contract](material-3.md).
 
 ## Pages, surfaces, and placements
 
 Take the surface and navigation role from the request, product context, and
 current app. They control routes, access, placement visibility, and often
-ownership. Inspect `app/shell-foundation` plus the narrow UI pattern that
-matches the requested outcome before authoring source.
+ownership. Inspect `app/shell-foundation` plus the narrow matching entry in
+the [bundled source pattern index](pattern-index.md) before authoring source.
 
 Create route files and placement declarations as normal application code.
 Use semantic placement ids and shell public helpers; use concrete outlet ids
@@ -27,7 +29,8 @@ hash, pattern receipt, or tool-owned source declaration.
 
 - Keep screens phone/task-first with drawer-independent primary actions and
   at least 48 CSS-pixel targets.
-- Use a page header and direct surfaces instead of needless nested cards.
+- Never add page headers or standalone headings unless the user explicitly asks.
+- Use direct surfaces instead of needless nested cards.
 - Render all meaningful loading, empty, error, permission, and retry states.
 - Use structure-matching Material skeletons for visible loading; never use a
   generic spinner or circular progress indicator.

package/templates/app/AGENTS.md

@@ -1,16 +1,20 @@
 # App Agent Instructions
 
-Use current project context, JSKIT public APIs, and the installed JSKIT pattern
-index as the source of truth for application work.
+Use current project context, JSKIT public APIs, and the official framework
+documentation as the source of truth for application work.
 
-Recommended references:
+Framework references:
 
-- `node_modules/@jskit-ai/agent-docs/guide/agent/index.md`
-- `node_modules/@jskit-ai/agent-docs/patterns/INDEX.md`
+- `https://mobily-enterprises.github.io/jskit-ai/guide/`
+- `https://mobily-enterprises.github.io/jskit-ai/patterns/`
 
-Before database, schema, CRUD, repository, or persistence work, read and follow
-the relevant package-owned pattern listed in
-`node_modules/@jskit-ai/agent-docs/reference/autogen/PATTERN_INDEX.md`.
+Before implementation, read the narrow relevant source pattern completely. If
+its owner package is installed, prefer that version-matched package-owned copy.
+Do not install an unrelated runtime package only to read documentation.
+
+Pages never start with a page header, title block, welcome heading, or other
+standalone heading copy. Start with the useful content and actions. If the user
+wants a heading, they will ask for or add one.
 
 Copied pattern source is ordinary application source. Do not add generator
 provenance, receipts, completion ledgers, or tooling-operation history. Keep