noecosystem-design 0.1.1 → 0.1.2

package/README.md

@@ -10,9 +10,10 @@ registry metadata, reference apps, documentation, and verification contracts.
 # Give a coding agent the NOE source context.
 npm install noecosystem-design
 
-# The agent starts with these two files after installation:
+# The agent starts with these files after installation:
 cat node_modules/noecosystem-design/AGENTS.md
 cat node_modules/noecosystem-design/llms.txt
+cat node_modules/noecosystem-design/docs/design-system/gpt-agent-prompt.md
 
 # For a writable, verifiable workspace, use a repository checkout.
 git clone https://github.com/NOrchestration/noe-design-system.git
@@ -26,13 +27,11 @@ Read [`AGENTS.md`](AGENTS.md) before changing code. Use [`llms.txt`](llms.txt) a
 retrieval map, then read the affected package and component records. The canonical
 catalog is [`packages/registry/manifest.json`](packages/registry/manifest.json).
 
-Give an agent this task instruction after installation:
-
-> Read `node_modules/noecosystem-design/AGENTS.md` and `llms.txt` first. Find the
-> requested capability in `packages/registry/manifest.json`, reuse the documented
-> NOE pattern where appropriate, and report the files consulted plus executed
-> verification. Do not treat the package as a runtime import or the external registry
-> URL as deployed.
+For a GPT coding agent, copy
+[`docs/design-system/gpt-agent-prompt.md`](docs/design-system/gpt-agent-prompt.md),
+replace `<TARGET_REPOSITORY>` and `<DESCRIBE THE REQUESTED OUTCOME...>`, and send it
+as one task prompt. The template carries static NOE context once; put only the
+requested outcome, scope, and non-negotiable constraints in its `Task` section.
 
 ## What `noecosystem-design` is — and is not
 
@@ -87,4 +86,6 @@ packages/registry       Canonical component catalog and install metadata
 
 See [`docs/design-system/README.md`](docs/design-system/README.md) for the focused
 documentation index and [`docs/design-system/agent-guide.md`](docs/design-system/agent-guide.md)
-for the complete coding-agent workflow.
+for the coding-agent workflow. The ready-to-paste
+[`docs/design-system/gpt-agent-prompt.md`](docs/design-system/gpt-agent-prompt.md)
+is the recommended task wrapper for GPT.

package/docs/design-system/README.md

@@ -11,6 +11,7 @@ The documentation describes the implementation in this repository and marks exte
 - `i18n.md`, `rtl.md`: locale, direction and bidi architecture.
 - `accessibility.md`: WCAG-oriented requirements.
 - `testing.md`, `visual-qa.md`: test and evidence strategy.
+- `gpt-agent-prompt.md`: ready-to-paste GPT task wrapper with outcome, autonomy, output, and stop rules.
 - `registry.md`, `mcp.md`, `agent-guide.md`: coding-agent discovery and package/registry boundaries.
 - `ci-cd.md`, `security.md`: automation and governance.
 - `contributing.md`: change workflow.

package/docs/design-system/agent-guide.md

@@ -1,5 +1,13 @@
 # Coding-agent guide
 
+## Start a GPT task
+
+Copy [`gpt-agent-prompt.md`](gpt-agent-prompt.md), replace its target repository and
+`Task` placeholder, and send it as one prompt. Put the requested outcome, scope, and
+non-negotiable constraints in `Task`; do not re-paste this guide or `AGENTS.md`.
+The prompt already defines the agent's success criteria, autonomy boundary, response
+format, and stop rules.
+
 ## Scope and distribution
 
 `noecosystem-design` is an npm-distributed source snapshot for discovery, review, and
@@ -18,27 +26,19 @@ The first-party `@noe` registry has local generation and consumer-test evidence.
 documented external endpoint must be treated as unavailable until deployment and
 official-MCP installation evidence exist; see `registry.md` and ADR 0007.
 
-## Required intake
-
-1. Read `README.md`, `AGENTS.md`, and the relevant focused document from `llms.txt`.
-2. Search `packages/registry/manifest.json` by capability, alias, and component name.
-3. Read the candidate item's `useWhen`, `doNotUseWhen`, `alternatives`, dependency,
-   accessibility, and internationalization fields before opening implementation files.
-4. Inspect the owning `packages/<package>/src` source and its Storybook story.
-5. If no capability fits, follow the component lookup order in `AGENTS.md` and record
-   why reuse was not appropriate.
-
-## Implementation protocol
-
-1. Prefer an existing NOE component or product pattern; never create a competing
-   primitive for Button, Dialog, DataTable, ToolCall, or Approval.
-2. Use semantic tokens, logical CSS properties, and the canonical i18n layer. Keep
-   unpredictable prose `dir=auto`; isolate URLs, IDs, code, paths, and commands LTR.
-3. Preserve semantic DOM order. Pass direction explicitly to portals; do not use
-   global `row-reverse` or global icon mirroring as an RTL fix.
-4. Keep ordinary tool output progressively disclosed and do not expose raw tool JSON
-   by default.
-5. Update source, stories, component tests, registry metadata, and docs together.
+## Retrieval and implementation
+
+Read `README.md`, `AGENTS.md`, and the focused documentation selected by `llms.txt`.
+Search `packages/registry/manifest.json` by capability, alias, and component name.
+For a candidate, read its `useWhen`, `doNotUseWhen`, `alternatives`, dependency,
+accessibility, and internationalization contracts before inspecting its source and
+Storybook story. If nothing fits, use the component lookup order in `AGENTS.md` and
+record the reason reuse was unsuitable.
+
+`AGENTS.md` defines the implementation constraints: reuse canonical components;
+preserve semantic tokens, i18n, RTL/bidi, portal direction, and progressive disclosure;
+and update the relevant source, stories, tests, registry metadata, and documentation
+together. Do not duplicate those instructions in a task prompt.
 
 ## Evidence before completion
 

package/docs/design-system/gpt-agent-prompt.md

@@ -0,0 +1,56 @@
+# GPT implementation prompt
+
+Use this after `npm install noecosystem-design`. Replace the values in angle
+brackets, then send the complete prompt to the coding agent. Keep the static
+context below intact; put task-specific details only in `Task`.
+
+```text
+Role
+You are the NOE design-system implementation agent working in <TARGET_REPOSITORY>.
+Use the installed noecosystem-design package as a read-only source of design-system
+context.
+
+Task
+<DESCRIBE THE REQUESTED OUTCOME, SCOPE, AND ANY NON-NEGOTIABLE CONSTRAINTS>
+
+Success criteria
+- The requested outcome works in the target repository.
+- Reuse the relevant NOE capability or established product pattern before creating
+  new UI.
+- Preserve every applicable NOE contract, including tokens, i18n, RTL/bidi,
+  accessibility, stories, tests, registry metadata, and documentation.
+- Run checks that are proportionate to the change and report only results actually
+  observed.
+
+Context
+1. Read node_modules/noecosystem-design/AGENTS.md and llms.txt first.
+2. Search node_modules/noecosystem-design/packages/registry/manifest.json for the
+   requested capability. Read the matching record and focused documentation before
+   implementation files.
+3. AGENTS.md is the authoritative static constraint set. Follow it without restating
+   it in the response.
+
+Constraints
+- noecosystem-design is a source snapshot, not a runtime dependency. Do not import
+  from it; use a writable repository checkout for implementation work.
+- Do not present the public @noe registry as deployed or installable without direct
+  deployment evidence.
+- Do safe local investigation, edits, and validation autonomously. Ask before an
+  external write, destructive action, purchase, credential change, or material scope
+  expansion.
+
+Response
+Lead with the outcome. Then give:
+- Changed: only the material files or behavior changed.
+- Evidence: commands run and their observed results.
+- Blockers or risks: only if they materially affect completion.
+
+Stop rules
+Ask one focused question only when a material decision cannot be safely inferred.
+Otherwise, finish when the success criteria are met. If evidence is unavailable,
+state the exact gap instead of implying completion.
+```
+
+The prompt intentionally states the goal, constraints, autonomy boundary, expected
+output, and stop conditions once. Do not append a second copy of `AGENTS.md`; direct
+the agent to the installed file instead.

package/llms.txt

@@ -15,18 +15,21 @@
 
 ## Retrieval order
 
-1. `README.md` — package scope, start path, commands, and distribution boundaries.
-2. `AGENTS.md` — mandatory design-system constraints and definition of done.
-3. `packages/registry/manifest.json` — capability search, ownership, use/do-not-use
+1. `docs/design-system/gpt-agent-prompt.md` — ready-to-paste task wrapper for GPT;
+   replace only its target repository and task fields.
+2. `README.md` — package scope, start path, commands, and distribution boundaries.
+3. `AGENTS.md` — mandatory design-system constraints and definition of done.
+4. `packages/registry/manifest.json` — capability search, ownership, use/do-not-use
    rules, accessibility, i18n, dependencies, and story references.
-4. `packages/registry/r/<item>.json` — installable-item metadata and source closure.
-5. The owning package source under `packages/` and its Storybook story under
+5. `packages/registry/r/<item>.json` — installable-item metadata and source closure.
+6. The owning package source under `packages/` and its Storybook story under
    `apps/storybook/stories/`.
 
 ## Focused documentation
 
 - Architecture and package boundaries: `docs/design-system/architecture.md`
-- Agent workflow: `docs/design-system/agent-guide.md`
+- GPT task wrapper: `docs/design-system/gpt-agent-prompt.md`
+- Agent workflow and retrieval: `docs/design-system/agent-guide.md`
 - Components and catalog terms: `docs/design-system/components.md`
 - Tokens and foundations: `docs/design-system/foundations.md`, `docs/design-system/tokens.md`
 - Locale, RTL, and bidi: `docs/design-system/i18n.md`, `docs/design-system/rtl.md`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "noecosystem-design",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "private": false,
   "description": "Agent-readable NOE design-system source, registry metadata, and verification contracts.",
   "keywords": [