Slash Command

/component

Standalone Glimmer GTS component specialist — create, modify, or get expert advice on A3 components

Install

Run in your terminal

npx claudepluginhub trusted-american/marketplace --plugin a3-plugin

Details

Argument<component-description-or-question>

Allowed Tools

ReadWriteEditGrepGlobBashAgent

Command Content

Other plugins with /component

/component

Scaffolds a new Vue component using Nuxt UI v4 patterns, TypeScript typing, and composables. Supports form, table, modal, dashboard, chat, page, card, dropdown types via <type> <name> [--path <dir>].

ReadWriteBash+2

nuxt-ui-v4

/component

Generate styled UI components with design system consistency

ReadWriteGlob+2

frontend-design-system

/component

Generate Bootstrap 5.3 component code interactively or with arguments

ReadWriteEdit+1

bootstrap-expert

/component

Generate DAPR component YAML files for state stores, pub/sub, bindings, and secrets across Azure, AWS, and GCP

dapr

/component

Generate Chart.js chart code interactively

ReadWriteEdit+1

chartjs-expert

/component

commands/

Build a UI component (Button, Card, Modal, Input, Table, Dropdown, etc.) with all variants, interactive states (hover, focus, disabled, loading), accessibility attributes, and design token references — consistent with the project's established design system.

claude-frontforge

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 26, 2026

Actions

View Source View Plugin View on GitHub View README

Behavior

Understand the request: Parse what the user needs — new component, modify existing, or advice

Investigate A3: Read 2-3 similar existing components to understand conventions

Ask clarifying questions if the request is ambiguous:

What data does this component receive?
Where does it live in the component hierarchy?
Are there existing components to reuse or extend?
Does it need loading/error/empty states?

Spawn component-writer agent with full context

Optional: spawn other agents for help if the component needs:

A new model → spawn model-writer
New test coverage → spawn test-writer
Integration verification → spawn integration-specialist

Self-review: The component-writer reviews its own output against A3 conventions

Deliver: Present the component code to the user

/component Command

Standalone entry point for the component-writer specialist. Use this when working on an isolated component task.

Authentication Gate

gh api repos/trusted-american/a3 --jq '.full_name' 2>/dev/null

STOP if this fails — user needs GitHub access to trusted-american/a3.

Behavior

Understand the request: Parse what the user needs — new component, modify existing, or advice
Investigate A3: Read 2-3 similar existing components to understand conventions
Ask clarifying questions if the request is ambiguous:
- What data does this component receive?
- Where does it live in the component hierarchy?
- Are there existing components to reuse or extend?
- Does it need loading/error/empty states?
Spawn component-writer agent with full context
Optional: spawn other agents for help if the component needs:
- A new model → spawn model-writer
- New test coverage → spawn test-writer
- Integration verification → spawn integration-specialist
Self-review: The component-writer reviews its own output against A3 conventions
Deliver: Present the component code to the user

When to Escalate

If the component task reveals that more is needed (new route, new model, backend changes), suggest the user run /orchestrate instead for full coordination.