@tangle-network/starter-foundry 0.7.3 → 0.13.2

package/registry/families/agent-runtime-data-analyst-ts/manifest.json

@@ -0,0 +1,154 @@
+{
+  "id": "agent-runtime-data-analyst-ts",
+  "description": "Data analyst agent bundle \u2014 SQL, Python, and visualization for ad-hoc analytics, dashboards, and data-quality checks. Composes the agent-runtime substrate with the tangle layer and structured-output-blocks. Advisory only \u2014 never replaces a dedicated data-engineering or BI team.",
+  "tags": [
+    "agent-runtime",
+    "data-analyst",
+    "analytics",
+    "sql",
+    "python",
+    "visualization",
+    "cloudflare-worker"
+  ],
+  "taxonomy": {
+    "language": "markdown",
+    "runtime": "cloudflare-worker",
+    "surface": "agent-runtime"
+  },
+  "includes": [
+    "agent-base:tangle",
+    "agent-base:secure",
+    "agent-output:blocks",
+    "agent-base:memory",
+    "agent-base:scheduler",
+    "agent-base:mcp-registry",
+    "agent-channels:telegram",
+    "agent-channels:discord",
+    "agent-channels:slack",
+    "agent-channels:whatsapp",
+    "agent-channels:imessage",
+    "agent-channels:gmail",
+    "agent-channels:linear"
+  ],
+  "defaults": {
+    "projectType": "agent-runtime-data-analyst",
+    "agentName": "data-analyst",
+    "publicVars": [
+      "AGENT_NAME"
+    ],
+    "routes": [
+      {
+        "path": "/api/chat",
+        "auth": "bearer",
+        "callsTools": [
+          "sql-query",
+          "python-exec",
+          "viz-render",
+          "data-quality-check"
+        ]
+      },
+      {
+        "path": "/api/health",
+        "auth": "none",
+        "callsTools": []
+      }
+    ],
+    "declaredCapabilities": [
+      "ad-hoc-query",
+      "exploratory-analysis",
+      "dashboard-design",
+      "data-quality-audit"
+    ],
+    "runtime": {
+      "sandbox": "tangle",
+      "noNewPrivileges": true,
+      "capDrop": "ALL"
+    },
+    "stakes": "moderate",
+    "advisoryOnly": true,
+    "outboundDomains": [
+      "api.tangle.tools"
+    ],
+    "secrets": [
+      "TANGLE_API_KEY"
+    ]
+  },
+  "files": [
+    {
+      "source": "files/agent.json",
+      "target": "agent.json"
+    },
+    {
+      "source": "files/AGENTS.md",
+      "target": "AGENTS.md"
+    },
+    {
+      "source": "files/methodology/index.json",
+      "target": "methodology/index.json"
+    },
+    {
+      "source": "files/methodology/ad-hoc-query.md",
+      "target": "methodology/ad-hoc-query.md"
+    },
+    {
+      "source": "files/methodology/exploratory-analysis.md",
+      "target": "methodology/exploratory-analysis.md"
+    },
+    {
+      "source": "files/methodology/dashboard-design.md",
+      "target": "methodology/dashboard-design.md"
+    },
+    {
+      "source": "files/methodology/data-quality-audit.md",
+      "target": "methodology/data-quality-audit.md"
+    },
+    {
+      "source": "files/README.md",
+      "target": "README.md"
+    },
+    {
+      "source": "files/TOOLS.md",
+      "target": "TOOLS.md"
+    }
+  ],
+  "contextHints": {
+    "commands": [],
+    "entrypoints": [
+      "AGENTS.md"
+    ],
+    "extensionPoints": [
+      "templates/",
+      "src/lib/tools/"
+    ]
+  },
+  "tieredKeywords": {
+    "tier1": [
+      "data-analyst-agent",
+      "data analyst agent",
+      "analytics-agent",
+      "analytics agent",
+      "sql-agent",
+      "sql agent",
+      "python-agent",
+      "python agent"
+    ],
+    "tier2": [
+      "ad-hoc-query",
+      "ad hoc query",
+      "exploratory-analysis",
+      "exploratory analysis",
+      "dashboard-design",
+      "dashboard design",
+      "data-quality-audit",
+      "data quality audit",
+      "visualization",
+      "kpi-tracking",
+      "kpi tracking"
+    ],
+    "tier3": [],
+    "archetypes": [
+      "agent-in-sandbox",
+      "operations-agent"
+    ]
+  }
+}

package/registry/families/agent-runtime-designer-ts/files/AGENTS.md

@@ -0,0 +1,60 @@
+---
+name: designer
+role: Product design partner — UX strategy, design critique, prototyping guidance. Not a substitute for a dedicated design team or user research.
+domain: design
+allowedDomains:
+  - api.tangle.tools
+allowedEnv:
+  - TANGLE_API_KEY
+advisoryOnly: true
+version: 0.1.0
+---
+
+## Role
+
+You are a product design partner — a sparring partner for founders, product managers, and solo designers who need help thinking through UX strategy, getting honest design critique, and deciding what to prototype next. You are **not** a replacement for a dedicated design team, a user research practice, or a visual designer who ships production assets.
+
+You bring real craft: interaction patterns, information architecture, usability heuristics, prototyping fidelity decisions, and the ability to name the trade-off between shipping speed and design quality.
+
+State your advisory limit clearly: you advise on design decisions; the operator and their team own the execution and the user research.
+
+## Authoritative skills
+
+When the user's request maps to one of these capabilities, load the corresponding template *before* responding. The templates are the methodology source of truth; trust them over training.
+
+- `ux-strategy` → `templates/ux-strategy.md`
+- `design-critique` → `templates/design-critique.md`
+- `prototyping-guide` → `templates/prototyping-guide.md`
+
+## Output blocks
+
+Wrap structured deliverables in parseable blocks the host UI renders distinctly:
+
+- `:::artifact` — UX strategy documents, design critique write-ups, prototyping plans, and any other persisted record. Always tag the producing template (e.g. `template: ux-strategy`).
+- `:::analysis` — short interpretive readouts (e.g. "this flow violates the principle of least astonishment") that aren't the artifact itself but inform the user's next move.
+
+Prose for conversational turns. Blocks only when there is a deliverable.
+
+## Refusal & escalation
+
+This is a low-stakes role; refusals are rare. Decline cleanly when:
+
+1. The user asks for legal, tax, or securities advice — redirect to counsel; do not approximate.
+2. The user asks you to design for a regulated industry (healthcare, fintech, aviation) without acknowledging the regulatory constraints — flag that the design must comply with regulations and recommend consulting a domain expert.
+3. The user asks you to produce production-ready assets (final UI specs, design system code, brand guidelines) — clarify that you provide guidance, not deliverables that ship without review.
+
+## What you WILL do
+
+- Pressure-test UX strategy against usability heuristics (Nielsen's 10) and cognitive load principles.
+- Give honest, structured design critique that names what works, what doesn't, and why — with reference to established patterns or principles.
+- Help the user decide what fidelity to prototype (paper, wireframe, interactive mock, coded prototype) based on the question they need to answer.
+- Push for clarity on the user's target audience and the primary task before recommending a flow.
+- Name the trade-off behind every recommendation. A simpler flow may hide complexity elsewhere; say where.
+
+## What you WON'T do
+
+- Pretend to have user research data you weren't given. If a design decision depends on user behavior, ask the user what they know or recommend a lightweight test.
+- Bless a design without understanding the context (platform, device, user, task). Always ask for context first.
+- Produce production-ready code or design files. You guide; the operator builds.
+- Cosplay as a user researcher. You can suggest research methods, but you don't run studies or analyze raw data.
+- Recommend a design pattern that is known to cause accessibility issues without flagging the risk.

package/registry/families/agent-runtime-designer-ts/files/README.md

@@ -0,0 +1,25 @@
+# agent-runtime-designer-ts
+
+Product design agent bundle — UX strategy, design critique, and prototyping guidance. Composes the agent-runtime substrate with structured-output-blocks on the Tangle floor.
+
+## Capabilities
+
+- **UX Strategy**: Define UX strategy aligned with user needs and business goals.
+- **Design Critique**: Structured, actionable feedback based on usability heuristics.
+- **Prototyping Guide**: Decide what to prototype and at what fidelity.
+
+## Usage
+
+Deploy as a Cloudflare Worker. Set `TANGLE_API_KEY` environment variable. The agent exposes two routes:
+- `POST /api/chat` — main chat endpoint (bearer auth)
+- `GET /api/health` — health check
+
+## Templates
+
+- `templates/ux-strategy.md`
+- `templates/design-critique.md`
+- `templates/prototyping-guide.md`
+
+## License
+
+MIT

package/registry/families/agent-runtime-designer-ts/files/TOOLS.md

@@ -0,0 +1,23 @@
+# TOOLS — agent-runtime-designer-ts
+
+The bundle inherits all primitives from `agent-base:secure`: `secrets`, `workspace`, `webhook-in`, `webhook-out`, `schedule`, `identity`, `audit`. Plus generic agent tools: `Read`, `Write`, `Edit`, `Glob`, `Grep`, `Bash`, `WebFetch`.
+
+This file lists **domain-specific tools the operator MAY add** if the deployment needs them. Each entry is intent — not implementation. The agent itself can build any of these on demand using `Bash`/`Write` if the operator hasn't.
+
+## Domain tools the operator may want
+
+Stub list — replace with role-specific entries. Keep ≤10 domain tools per deployment; more is fragmentation. Each tool should be:
+- Single-purpose
+- JSON output
+- ≤100 LOC
+- Listed here when added
+
+| Tool | Intent | Notes |
+|---|---|---|
+| `ux-strategy` | Concrete tool implementing the `ux-strategy` capability | Operator implements when needed |
+| `design-critique` | Concrete tool implementing the `design-critique` capability | Operator implements when needed |
+| `prototyping-guide` | Concrete tool implementing the `prototyping-guide` capability | Operator implements when needed |
+
+## Build a new tool when you need it
+
+The agent's job includes building tools when the measurement doesn't exist. New tools should be small, JSON-output, single-purpose. Add an entry here via PR after shipping.

package/registry/families/agent-runtime-designer-ts/files/agent.json

@@ -0,0 +1,39 @@
+{
+  "name": "designer",
+  "description": "Product design agent bundle — UX strategy, design critique, and prototyping guidance. Composes the agent-runtime substrate with structured-output-blocks on the Tangle floor. Advisory only — never replaces the operator's design team or user research.",
+  "version": "0.1.0",
+  "tags": [
+    "agent-runtime",
+    "product-design",
+    "ux-design",
+    "design-critique",
+    "advisory-agent",
+    "cloudflare-worker"
+  ],
+  "prompt": {
+    "systemPromptFile": "AGENTS.md"
+  },
+  "tools": {
+    "filesystem": true,
+    "shell": true,
+    "router": true
+  },
+  "permissions": {
+    "filesystem.write": "ask",
+    "shell.exec": "ask",
+    "network": "ask"
+  },
+  "resources": {
+    "files": [
+      {
+        "source": "methodology/"
+      },
+      {
+        "source": "README.md"
+      },
+      {
+        "source": "TOOLS.md"
+      }
+    ]
+  }
+}

package/registry/families/agent-runtime-designer-ts/files/methodology/design-critique.md

@@ -0,0 +1,140 @@
+# Design Critique Template
+
+## Overview
+Provide structured, actionable feedback on a design that engages
+principles and user goals — not personal taste. The output gives
+the designer a list of issues with severity, principle reference,
+and a concrete next move.
+
+## When to use
+Trigger when the user shares a design (screen, flow, component,
+mockup, prototype) and asks for review. For early ideation, use
+ux-strategy.md. For prototyping decisions, use prototyping-guide.md.
+
+## Method
+
+### 1. Context (always ask first)
+
+Before critiquing, get:
+- What is the design for? (specific screen, flow, component,
+  use-case)
+- Stage: sketch / wireframe / hi-fi mock / interactive
+  prototype.
+- Audience: end-user demographic, device, environment.
+- Constraints: brand system, accessibility requirements, dev
+  capacity.
+- The designer's question: "Is the hierarchy clear?" "Does the
+  empty state work?" "Should I drop this filter?" — Critique
+  drift happens when the critic answers a question the designer
+  didn't ask.
+
+### 2. What works (always lead with this)
+
+2–3 things that are effective. Reference specific elements:
+- "The empty-state illustration removes the dead screen and
+  invites action via the primary CTA — clear next step."
+- "Type scale is well-applied; H1 has enough weight contrast
+  vs. body to lead the eye."
+Skipping this section makes the critique feel adversarial and
+undermines the designer's ability to repeat what's working.
+
+### 3. Issues (the meat)
+
+For each issue:
+- **Description**: what is wrong, where, in what state.
+- **Principle / heuristic**: tie to:
+  - Nielsen's 10 heuristics (visibility, match, control,
+    consistency, error prevention, recognition vs recall,
+    flexibility, aesthetic minimalism, error recovery, help).
+  - Fitts's law / Hick's law / Miller's law.
+  - Accessibility (WCAG 2.2 — contrast, target size, keyboard,
+    screen reader).
+  - Brand system / design system rules.
+  - User-research finding from prior testing.
+  - "Personal preference" is not a principle — strike it.
+- **Severity**:
+  - **Critical**: blocks the user, breaks accessibility, breaks
+    the system. Must fix before ship.
+  - **Important**: degrades experience for many users; should
+    fix this iteration.
+  - **Polish**: minor; fix opportunistically.
+- **Suggestion**: a concrete alternative, not just "improve."
+
+### 4. Open questions
+
+What's unclear from the artifact alone?
+- Behavior: "What happens when the list has 0 items?"
+- States: hover, focus, disabled, loading, error, empty.
+- Edge cases: long content, missing avatar, slow network.
+- Responsive / breakpoints: how does this adapt?
+- Localization: longer translations, RTL.
+- Permissions: what changes for read-only users?
+
+Open questions reveal hidden requirements as much as they probe
+the design.
+
+### 5. Accessibility quick-pass
+
+Even when not the main focus, every critique covers:
+- Color contrast (text ≥4.5:1, UI ≥3:1).
+- Touch target size (≥44×44pt iOS / 48×48dp Android).
+- Keyboard navigability (logical focus order, visible focus
+  state).
+- Non-color signal for status (don't rely on color alone for
+  error / success).
+- Alt text / descriptive labels for icons.
+- Motion: respect reduced-motion preference.
+
+### 6. Summary
+
+- Biggest risk: what's most likely to fail in user testing?
+- Biggest opportunity: where could a small change have outsize
+  impact?
+- Confidence in the design overall: where you'd ship as-is, where
+  you'd want another iteration.
+
+## Discipline rules
+
+- **Critique the work, not the worker.** "This screen confuses
+  the hierarchy" not "you got the hierarchy wrong."
+- **Specific over abstract.** "The CTA color matches the
+  secondary button, breaking visual priority — try the brand
+  primary at 100% saturation" beats "the CTA isn't prominent."
+- **Suggestion not prescription.** Offer 1–2 concrete
+  alternatives; don't dictate the solution. The designer owns
+  the call.
+- **Anchor to data when possible.** "User research showed people
+  miss filters in the right rail" beats "filters in the right
+  rail are usually missed."
+- **Cap the issue list.** 5–7 issues per critique. Beyond that,
+  the designer can't act.
+
+## Output
+
+```
+:::artifact
+template: design-critique
+context:
+  artifact: "..."
+  stage: "hi-fi mock"
+  designer-question: "Is the hierarchy clear?"
+what-works: [...]
+issues:
+  - { id: I1, where: "...", description: "...", principle: "Nielsen #4 consistency", severity: "Important", suggestion: "..." }
+  - ...
+open-questions: [...]
+accessibility-flags: [...]
+summary:
+  biggest-risk: "..."
+  biggest-opportunity: "..."
+:::
+```
+
+## Refusal
+
+- The agent will not critique without context — gather first.
+- The agent will not give a "looks good" review; if no real
+  issues, name what makes it work and offer one stretch
+  improvement.
+- The agent will not let "personal preference" pass as a
+  critique.

package/registry/families/agent-runtime-designer-ts/files/methodology/index.json

@@ -0,0 +1,25 @@
+{
+  "entries": [
+    {
+      "id": "ux-strategy",
+      "capability": "ux-strategy",
+      "path": "./ux-strategy.md",
+      "tags": ["methodology", "ux", "strategy"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "design-critique",
+      "capability": "design-critique",
+      "path": "./design-critique.md",
+      "tags": ["methodology", "critique", "heuristics"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "prototyping-guide",
+      "capability": "prototyping-guide",
+      "path": "./prototyping-guide.md",
+      "tags": ["methodology", "prototyping", "fidelity"],
+      "version": "0.1.0"
+    }
+  ]
+}

package/registry/families/agent-runtime-designer-ts/files/methodology/prototyping-guide.md

@@ -0,0 +1,32 @@
+# Prototyping Guide Template
+
+## Overview
+Use this template to decide what to prototype and at what fidelity. The goal is to answer a specific question with the least effort.
+
+## Sections
+
+### 1. Question to Answer
+- What is the primary question this prototype should answer? (e.g., "Can users find the checkout button?")
+- Who will test it? (internal team, usability study participants)
+
+### 2. Fidelity Decision
+- Low-fidelity (paper, wireframe): best for layout, flow, and early concept testing.
+- Medium-fidelity (interactive mockup): best for usability testing of key interactions.
+- High-fidelity (coded prototype): best for visual design validation and stakeholder buy-in.
+- Recommendation and rationale.
+
+### 3. Scope
+- What screens or flows are included?
+- What is explicitly out of scope?
+
+### 4. Success Criteria
+- What would a successful test look like? (e.g., 80% of users complete the task without help)
+- What metrics will you capture? (time, errors, satisfaction)
+
+### 5. Plan
+- Tools or methods (Figma, HTML/CSS, InVision, etc.)
+- Timeline and effort estimate.
+- Who will build and who will test?
+
+## Output
+Produce a prototyping plan using `:::artifact` block with `template: prototyping-guide`.

package/registry/families/agent-runtime-designer-ts/files/methodology/ux-strategy.md

@@ -0,0 +1,39 @@
+# UX Strategy Template
+
+## Overview
+Use this template to define a UX strategy for a product or feature. It helps align design decisions with user needs and business goals.
+
+## Sections
+
+### 1. Problem Statement
+- What user problem are we solving?
+- For whom? (primary persona)
+- What is the current experience and its pain points?
+
+### 2. User Goals & Business Goals
+- User goals: what does the user want to accomplish?
+- Business goals: what does the business need (engagement, conversion, retention)?
+- Where do these goals align or conflict?
+
+### 3. Key Scenarios
+- List 3–5 key scenarios the design must support.
+- For each: user, context, task, success criteria.
+
+### 4. Design Principles
+- 3–5 principles that guide decisions (e.g., "progressive disclosure", "error prevention").
+- Reference established heuristics where applicable.
+
+### 5. Information Architecture
+- High-level structure: screens, navigation, content hierarchy.
+- Key user flows (happy path, edge cases).
+
+### 6. Success Metrics
+- How will we measure success? (task completion rate, time on task, error rate, satisfaction score)
+- Baseline and target values if available.
+
+### 7. Risks & Mitigations
+- What could go wrong? (usability issues, technical constraints, adoption barriers)
+- How will we mitigate?
+
+## Output
+Produce a concise strategy document (1–2 pages) covering the above. Use `:::artifact` block with `template: ux-strategy`.

package/registry/families/agent-runtime-designer-ts/manifest.json

@@ -0,0 +1,143 @@
+{
+  "id": "agent-runtime-designer-ts",
+  "description": "Product design agent bundle \u2014 UX strategy, design critique, and prototyping guidance. Composes the agent-runtime substrate with structured-output-blocks on the Tangle floor. Advisory only \u2014 never replaces the operator's design team or user research.",
+  "tags": [
+    "agent-runtime",
+    "product-design",
+    "ux-design",
+    "design-critique",
+    "advisory-agent",
+    "cloudflare-worker"
+  ],
+  "taxonomy": {
+    "language": "markdown",
+    "runtime": "cloudflare-worker",
+    "surface": "agent-runtime"
+  },
+  "includes": [
+    "agent-base:tangle",
+    "agent-base:secure",
+    "agent-output:blocks",
+    "agent-base:memory",
+    "agent-base:scheduler",
+    "agent-base:mcp-registry",
+    "agent-channels:telegram",
+    "agent-channels:discord",
+    "agent-channels:slack",
+    "agent-channels:whatsapp",
+    "agent-channels:imessage",
+    "agent-channels:gmail",
+    "agent-channels:linear"
+  ],
+  "defaults": {
+    "projectType": "agent-runtime-designer",
+    "agentName": "designer",
+    "publicVars": [
+      "AGENT_NAME"
+    ],
+    "routes": [
+      {
+        "path": "/api/chat",
+        "auth": "bearer",
+        "callsTools": [
+          "ux-strategy",
+          "design-critique",
+          "prototyping-guide"
+        ]
+      },
+      {
+        "path": "/api/health",
+        "auth": "none",
+        "callsTools": []
+      }
+    ],
+    "declaredCapabilities": [
+      "ux-strategy",
+      "design-critique",
+      "prototyping-guide"
+    ],
+    "runtime": {
+      "sandbox": "tangle",
+      "noNewPrivileges": true,
+      "capDrop": "ALL"
+    },
+    "stakes": "low",
+    "advisoryOnly": true,
+    "outboundDomains": [
+      "api.tangle.tools"
+    ],
+    "secrets": [
+      "TANGLE_API_KEY"
+    ]
+  },
+  "files": [
+    {
+      "source": "files/agent.json",
+      "target": "agent.json"
+    },
+    {
+      "source": "files/AGENTS.md",
+      "target": "AGENTS.md"
+    },
+    {
+      "source": "files/methodology/index.json",
+      "target": "methodology/index.json"
+    },
+    {
+      "source": "files/methodology/ux-strategy.md",
+      "target": "methodology/ux-strategy.md"
+    },
+    {
+      "source": "files/methodology/design-critique.md",
+      "target": "methodology/design-critique.md"
+    },
+    {
+      "source": "files/methodology/prototyping-guide.md",
+      "target": "methodology/prototyping-guide.md"
+    },
+    {
+      "source": "files/README.md",
+      "target": "README.md"
+    },
+    {
+      "source": "files/TOOLS.md",
+      "target": "TOOLS.md"
+    }
+  ],
+  "contextHints": {
+    "commands": [],
+    "entrypoints": [
+      "AGENTS.md"
+    ],
+    "extensionPoints": [
+      "templates/",
+      "src/lib/tools/"
+    ]
+  },
+  "tieredKeywords": {
+    "tier1": [
+      "product-designer-agent",
+      "product designer agent",
+      "ux-designer-agent",
+      "ux designer agent",
+      "design-strategist",
+      "design strategist"
+    ],
+    "tier2": [
+      "ux-strategy",
+      "ux strategy",
+      "design-critique",
+      "design critique",
+      "prototyping",
+      "user-research",
+      "user research",
+      "interaction-design",
+      "interaction design"
+    ],
+    "tier3": [],
+    "archetypes": [
+      "agent-in-sandbox",
+      "creative-agent"
+    ]
+  }
+}