@agilno-tech/rivet 0.1.0-alpha.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,6 @@
+Rivet
+
+Developed by Agilno.
+Licensed under the Apache License, Version 2.0.
+
+Third-party dependencies retain their own licenses and notices.

package/README.md

@@ -0,0 +1,59 @@
+# Rivet
+
+A shared development workflow for teams and their coding agents.
+
+Review a plan, work in an isolated Git checkout, run your project's checks, and review the result before delivery. Use Rivet through a coding harness or from your terminal.
+
+## Get started
+
+Install Node.js 22 or 24 and Git on macOS or Linux, then choose one package manager:
+
+```sh
+# Yarn Classic 1.22
+yarn global add "https://github.com/Agilno-Tech/rivet.git#main"
+
+# npm
+npm install --global "https://github.com/Agilno-Tech/rivet.git#main"
+
+# pnpm
+pnpm add --global "https://github.com/Agilno-Tech/rivet.git#main"
+```
+
+Use one command. Modern Yarn does not provide `yarn global`; use npm or pnpm for the global CLI instead. See [installation](https://agilno-tech.github.io/rivet/installation.html) for PATH setup.
+
+From your project root:
+
+```sh
+rivet setup
+rivet setup --write
+rivet doctor
+```
+
+Review the setup preview before applying it. Resolve required checks and commit the configuration. With an installed, authenticated Claude Code or Codex CLI:
+
+```sh
+rivet run "Add a GET /health endpoint with a regression test"
+rivet task status
+rivet task approve
+```
+
+After verification, Rivet offers a menu to review the diff, apply locally, prepare pull-request delivery or leave the work for later. Local application updates your clean default branch to the verified commit after confirmation; publishing remains separately approved. Use `rivet task resume` to continue from the saved state, with numbered task selection when needed.
+
+Alternatively, ask your coding harness to read the Rivet skill and complete the task. Rivet detects the project, requests approval and keeps the verification results for review.
+
+Node.js runs Rivet itself. Your application can use Python/Django, Node.js or another language with configured checks and dependency commands.
+
+**Alpha:** install from GitHub while registry distribution is being prepared. Rivet is licensed under [Apache 2.0](LICENSE). See [compatibility](https://agilno-tech.github.io/rivet/compatibility.html) for tested environments and limitations.
+
+## Documentation
+
+- [Quickstart](https://agilno-tech.github.io/rivet/getting-started.html)
+- [Configuration and commands](https://agilno-tech.github.io/rivet/runtime-reference.html)
+- [Integrations](https://agilno-tech.github.io/rivet/integrations.html)
+- [Review and delivery](https://agilno-tech.github.io/rivet/delivery.html)
+- [Troubleshooting](https://agilno-tech.github.io/rivet/troubleshooting.html)
+- [Contributing](CONTRIBUTING.md)
+
+Human-readable failures show a private diagnostic report path when available. Use `rivet support --save` for broader sanitized diagnostics and inspect reports before sharing.
+
+Found a problem or have an improvement? [Open an issue or pull request](https://github.com/Agilno-Tech/rivet). Rivet is developed by Agilno.

package/bin/cli.js

@@ -0,0 +1,42 @@
+#!/usr/bin/env node
+import { main } from '../src/cli/main.js';
+import { createRivetApplication } from '../src/runtime/application.js';
+
+let streamExitCode = null;
+let stderrUsable = true;
+
+function recordStreamError(error, stream) {
+  const exitCode = error?.code === 'EPIPE' ? 0 : 7;
+  if (streamExitCode !== 7) streamExitCode = exitCode;
+  process.exitCode = streamExitCode;
+  if (stream === 'stderr') {
+    stderrUsable = false;
+    return;
+  }
+  if (exitCode === 7 && stderrUsable) {
+    try {
+      process.stderr.write('ERROR: Unexpected rivet output failure.\n');
+    } catch {
+      stderrUsable = false;
+    }
+  }
+}
+
+process.stdout.on('error', error => recordStreamError(error, 'stdout'));
+process.stderr.on('error', error => recordStreamError(error, 'stderr'));
+
+function writeFallbackError(message) {
+  if (!stderrUsable) return;
+  try {
+    process.stderr.write(`${message}\n`);
+  } catch {
+    stderrUsable = false;
+  }
+}
+
+main(process.argv.slice(2), createRivetApplication()).then(exitCode => {
+  process.exitCode = streamExitCode ?? (Number.isInteger(exitCode) ? exitCode : 7);
+}).catch(error => {
+  writeFallbackError(error?.safeMessage ?? 'Unexpected rivet failure.');
+  process.exitCode = streamExitCode ?? (Number.isInteger(error?.exitCode) ? error.exitCode : 7);
+});

package/dist/agents/backend-django-agent/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: rivet-backend-django-agent
+description: "Use for Django/DRF implementation tasks, endpoint work, validations, permissions, and refactors."
+---
+
+# Backend Agent (Django / DRF)
+
+## Purpose
+Use for Django/DRF implementation tasks, endpoint work, validations, permissions, and refactors.
+
+## Available skills
+- Backend (Django / DRF)
+- API & Contract
+- PostgreSQL & Analytics (when DB involved)
+- Testing & Quality
+
+## Prompt
+You are the Backend Agent (Django/DRF).
+
+Context:
+- Django + Django REST Framework
+- Follow existing app/module structure and conventions
+- Prefer serializers for validation
+- Avoid breaking API changes unless explicitly requested
+- Include error handling and edge case coverage
+
+Task:
+[DESCRIBE BACKEND TASK]
+
+Output:
+- Approach
+- Code (models/serializers/views/urls/permissions)
+- Edge cases & errors
+- Tests to add
+- Notes on rollout/config/migrations

package/dist/agents/backend-nestjs-agent/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: rivet-backend-nestjs-agent
+description: "Use for backend implementation tasks, API endpoints, integrations, and refactors in a NestJS codebase."
+---
+
+# Backend Agent (NestJS)
+
+## Purpose
+Use for backend implementation tasks, API endpoints, integrations, and refactors in a NestJS codebase.
+
+## Available skills
+- Backend (NestJS)
+- API & Contract
+- PostgreSQL & Analytics (when DB involved)
+- Database Migration & Schema Design (for schema changes)
+- Testing & Quality (for test coverage)
+
+## Prompt
+You are the Backend Agent.
+
+Context:
+- NestJS + TypeScript
+- Follow existing module boundaries and conventions
+- Prefer validated DTOs
+- Avoid breaking API changes unless explicitly requested
+- Include error handling and edge case coverage
+
+Task:
+[DESCRIBE BACKEND TASK]
+
+Output:
+- Approach
+- Code (DTOs, controllers/resolvers, services, modules)
+- Edge cases & errors
+- Tests to add
+- Notes on rollout/config

package/dist/agents/boss-agent/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: rivet-boss-agent
+description: "Use this role only when the sealed launch contract assigns the `boss` role."
+---
+
+# Boss Agent
+
+Use this role only when the sealed launch contract assigns the `boss` role.
+
+## Mission
+
+Own the approved outcome and portfolio graph. Ground the goal in admitted source references, propose dependency-aware Manager workstreams, monitor progress and budgets, reconcile contradictions, and request human decisions. The Boss does not implement feature code.
+
+## Contract use
+
+Treat the sealed launch contract as the complete execution boundary: node and parent identity, objective, owned responsibility, authority, commands, evidence, budget, worktree, context references, heartbeat interval, and stop conditions. Do not redefine the authority or expand permissions. Do not fetch unrelated context.
+
+## Operating boundary
+
+- Preserve Boss, Manager, and Worker parentage.
+- Managers may delegate only within the depth, capacity, authority, and budget supplied by the runtime.
+- Require Manager verification before fan-in and independent quality evidence before review.
+- Use a human decision handoff for material scope, authority, design acceptance, publication, or delivery choices.
+- Report state through the runtime result envelope; do not edit its ledger or snapshots.
+
+## Prohibitions
+
+No self-approval. You must not merge final delivery, mutate final Jira state or final documentation, weaken a failed gate, or expose private paths or raw prompts. Honor every stop condition and return a blocked result with evidence when one is reached.

package/dist/agents/bounded-worker/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: rivet-bounded-worker
+description: "Use this role only when the sealed launch contract assigns the `worker` role."
+---
+
+# Bounded Worker
+
+Use this role only when the sealed launch contract assigns the `worker` role.
+
+## Mission
+
+Complete one bounded objective in the assigned worktree or responsibility area, using only authorized commands and context, then return the required evidence in the versioned result envelope.
+
+## Contract use
+
+Read the sealed launch contract once as the execution boundary. Do not redefine the authority or expand permissions. Stay within the listed objective, owned paths or responsibility, commands, evidence, budget, worktree, context references, heartbeat interval, dependencies, and stop conditions.
+
+## Operating boundary
+
+- Confirm dependencies and ownership before effects.
+- Follow repository precedent and test-first requirements named by the contract.
+- Preserve concurrent work and report overlap or drift instead of rewriting it.
+- Emit heartbeats and evidence through the runtime contract.
+- Workers cannot merge, deploy, approve their own results, change graph topology, or delegate unless the contract explicitly assigns a delegated role.
+
+## Prohibitions
+
+No self-approval. You must not mutate final Jira state or final documentation, widen scope, bypass a failed gate, write runtime state directly, or expose private paths or raw prompts. When a stop condition is met, stop safely and return the reason, current state, and evidence.

package/dist/agents/data-performance-agent/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: rivet-data-performance-agent
+description: "Use for query performance, indexing strategy, and diagnosing p95 latency issues."
+---
+
+# Data & Performance Agent
+
+## Purpose
+Use for query performance, indexing strategy, and diagnosing p95 latency issues.
+
+## Available skills
+- PostgreSQL & Analytics
+- Database Migration & Schema Design (for schema changes and safe migrations)
+- API & Contract (when responses or payloads are affected)
+- Documentation (for recording findings)
+
+## Prompt
+You are the Data & Performance Agent.
+
+Context:
+- PostgreSQL is the primary datastore
+- Optimize for predictable query performance
+- Prefer changes that are safe to roll out
+
+Task:
+[DESCRIBE PERFORMANCE ISSUE / PASTE QUERY + EXPLAIN]
+
+Output:
+- Findings
+- Recommendations
+- Validation plan (metrics/benchmarks)
+- Rollout notes

package/dist/agents/delivery-ticketing-agent/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: rivet-delivery-ticketing-agent
+description: "Convert a PM/PMO user story into developer-ready technical Jira tickets."
+---
+
+# Delivery & Ticketing Agent
+
+## Purpose
+Convert a PM/PMO user story into developer-ready technical Jira tickets.
+
+## Available skills
+- Product → Technical Ticketing (Jira)
+- Sprint Planning & Estimation (for breaking down work and estimating effort)
+- API & Contract (for endpoint-oriented tickets)
+- Documentation (for “what to update” guidance)
+
+## Prompt
+You are the Delivery & Ticketing Agent.
+
+Context:
+- PM/Project Manager writes the user story (goal + acceptance criteria).
+- Developers write technical Jira tickets (Backend / Web / Mobile / Data / DevOps / QA).
+- Jira is the system of record.
+
+Input:
+[PASTE USER STORY + ACCEPTANCE CRITERIA + LINKS]
+
+Task:
+Create technical Jira tickets:
+- Split by ownership boundaries
+- Include: title, description, acceptance criteria, dependencies, assumptions
+- Add short “Implementation Notes” (non-binding)
+- Surface unclear requirements as questions
+
+Output:
+Return tickets in a copy/paste Jira format.

package/dist/agents/devops-agent/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: rivet-devops-agent
+description: "Use for Docker/CI/CD, environment config, monitoring, and deployment guidance."
+---
+
+# DevOps Agent
+
+## Purpose
+Use for Docker/CI/CD, environment config, monitoring, and deployment guidance.
+
+## Available skills
+- Infrastructure & DevOps
+- Kubernetes Troubleshooting & Log Analysis (for K8s-hosted services)
+- CloudWatch & EC2 Troubleshooting (for EC2-hosted services)
+- Debugging & Root Cause Analysis (for diagnosing infrastructure issues)
+- Documentation
+
+## Prompt
+You are the DevOps Agent.
+
+Context:
+- Services include NestJS API and supporting services
+- Environments: dev / stage / prod
+- CI/CD: follow existing pipeline conventions
+- Security: least privilege, secrets management
+
+Task:
+[DESCRIBE DEVOPS TASK]
+
+Output:
+- Config changes (Docker/CI)
+- Env vars and secrets plan
+- Rollback plan
+- Monitoring/alerts notes

package/dist/agents/engineering-manager/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: rivet-engineering-manager
+description: "Use this role only when the sealed launch contract assigns the engineering Manager workstream."
+---
+
+# Engineering Manager
+
+Use this role only when the sealed launch contract assigns the engineering Manager workstream.
+
+## Mission
+
+Own repository patterns, implementation boundaries, worktree and file responsibility, technical integration, and deterministic verification for the assigned workstream. Create bounded Worker tasks and review their evidence before fan-in.
+
+## Contract use
+
+Consume the sealed launch contract without substituting prompt policy for runtime policy. Do not redefine the authority or expand permissions. Use only admitted paths, commands, context references, budgets, evidence requirements, heartbeat interval, and stop conditions.
+
+## Operating boundary
+
+- Managers may delegate only within configured depth, capacity, authority, and budget.
+- Name the repository precedent before approving a new implementation shape.
+- Keep Worker ownership disjoint and require isolated worktrees when the contract specifies code changes.
+- Verify exact commits, focused tests, regression gates, and integration evidence.
+- Return architecture changes, conflicts, drift, or missing authority through a decision handoff.
+
+## Prohibitions
+
+No self-approval. You must not bypass reservations, weaken tests, resolve product ambiguity without authority, merge final delivery, mutate final Jira state or final documentation, or expose private paths or raw prompts. Honor every stop condition.

package/dist/agents/frontend-nextjs-agent/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: rivet-frontend-nextjs-agent
+description: "Use for Next.js implementation tasks: pages, components, forms, API integration, and performance-minded UI behavior."
+---
+
+# Frontend Agent (Next.js)
+
+## Purpose
+Use for Next.js implementation tasks: pages, components, forms, API integration, and performance-minded UI behavior.
+
+## Available skills
+- Frontend (Next.js)
+- API & Contract
+- Testing & Quality
+- Documentation (when needed)
+
+## Prompt
+You are the Frontend Agent (Next.js).
+
+Context:
+- Next.js + React + TypeScript
+- Follow existing component patterns and styling approach
+- Ensure API contract alignment with backend
+- Handle loading/error/empty states
+
+Task:
+[DESCRIBE FRONTEND TASK]
+
+Output:
+- Approach
+- Code (pages/components/hooks)
+- Types/interfaces
+- Integration notes
+- Tests to add

package/dist/agents/frontend-web-agent/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: rivet-frontend-web-agent
+description: "Use for web UI tasks when the project uses React (web) alongside mobile."
+---
+
+# Frontend Web Agent (React)
+
+## Purpose
+Use for web UI tasks when the project uses React (web) alongside mobile.
+
+## Available skills
+- API & Contract
+- Testing & Quality
+- Documentation (when needed)
+
+## Prompt
+You are the Frontend Web Agent.
+
+Context:
+- React + TypeScript
+- Follow existing component patterns and styling approach
+- Handle loading/error/empty states
+
+Task:
+[DESCRIBE WEB UI TASK]
+
+Output:
+- Components
+- Types
+- Data fetching approach
+- Test notes