Skip to content
Back to skills

Agentstudio Bridgeweb React Ui

ASecurity

Use when editing Agent Studio BridgeWeb React UI controls, chrome, toolbars, toggles, menus, inputs, or shared viewer components in this repo.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentsreact

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add ShravanSunder/agentstudio --skill agentstudio-bridgeweb-react-ui --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agentstudio Bridgeweb React Ui?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agentstudio Bridgeweb React Ui
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/shravansunder-agentstudio-bridgeweb-react-ui/badge)](https://www.skillsdirectory.com/skills/shravansunder-agentstudio-bridgeweb-react-ui)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agentstudio-bridgeweb-react-ui
description: Use when editing Agent Studio BridgeWeb React UI controls, chrome, toolbars, toggles, menus, inputs, or shared viewer components in this repo.
---

# Agent Studio BridgeWeb React UI

BridgeWeb React UI uses shadcn-style owned source primitives.

## Required Pattern

1. Inspect `BridgeWeb/src/components/ui/` before building a control.
2. If the needed shadcn primitive is missing, add the primitive source there.
3. Reuse the owned primitive unchanged when its recipe fits the intended role.
   Change its tokens, sizing or states only to supply a missing reusable meaning,
   not merely because the task edits a control.
4. Compose product-specific controls from those primitives. A shared wrapper
   needs shared composition or behavior; styling parity alone does not justify it.
5. Keep FileViewer and ReviewViewer controls with the same interaction
   semantics on the same primitive layer and visual scale.

## Prohibited Pattern

Do not hand-roll route-local toggles, segmented controls, buttons, menus,
inputs, or toolbar widgets because one route has nearby markup. A local wrapper
around `Button` is not enough when the interaction is really a shadcn primitive
such as ToggleGroup, Tabs, DropdownMenu, or Input.

## Proof

Any visible BridgeWeb UI checkpoint must include browser/native screenshots and
geometry or interaction proof for the changed controls. DOM-only or jsdom-only
proof is not sufficient for visual UX.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…