By brighthills
BrightHills Agile toolkit: feature planning, ticket creation, implementation workflow, story writing, code review, QA testing, security auditing, and project setup.
Use this agent when you need expert guidance on product design, user experience, or interface design decisions. This includes creating user flows, wireframes, design systems, conducting design reviews, solving UX problems, evaluating usability, creating product specifications, or translating technical requirements into user-friendly designs. <example> Context: The user needs help designing a new feature for their application. user: "I need to add a notification system to my app but I'm not sure how to make it user-friendly" assistant: "I'll use the product-ux-designer agent to help design an intuitive notification system" <commentary> Since the user needs UX design guidance for a new feature, use the product-ux-designer agent to provide expert design recommendations. </commentary> </example> <example> Context: The user wants feedback on their existing interface design. user: "Can you review this dashboard layout and suggest improvements?" assistant: "Let me engage the product-ux-designer agent to provide a comprehensive UX review of your dashboard" <commentary> The user is asking for a design review, so the product-ux-designer agent should be used to evaluate and improve the interface. </commentary> </example>
Use this agent when you need to plan, create, or execute E2E tests based on Story Acceptance Criteria. This includes analyzing AC to create test plans, writing test code, running tests, and reporting results. <example> Context: User wants to create E2E tests for a story user: "Create E2E tests for story #45" assistant: "I'll use the qa-tester agent to analyze the acceptance criteria and create E2E tests." <commentary> User requesting E2E test creation for a story triggers the qa-tester agent. </commentary> </example> <example> Context: User wants to run tests and get a QA report user: "Run the E2E tests and give me a report" assistant: "I'll use the qa-tester agent to execute the tests and generate a structured report." <commentary> User requesting test execution and reporting triggers the qa-tester agent. </commentary> </example> <example> Context: User wants a test plan for acceptance criteria user: "Create a test plan for the login feature AC" assistant: "I'll use the qa-tester agent to break down the acceptance criteria into testable scenarios." <commentary> User asking for a test plan based on AC triggers the qa-tester agent. </commentary> </example>
Use this agent to perform comprehensive security audits focusing on data leakage, authentication vulnerabilities, and data security issues. The agent analyzes code for OWASP Top 10 vulnerabilities, checks for sensitive data exposure, reviews authentication/authorization flows, and identifies potential attack vectors. <example> Context: User wants a security audit of their application user: "Run a security audit on our codebase" assistant: "I'll use the security-auditor agent to perform a comprehensive OWASP Top 10 security audit." <commentary> User requesting a security audit triggers the security-auditor agent. </commentary> </example> <example> Context: User is concerned about data leakage user: "Check if we're exposing sensitive data in our API responses" assistant: "I'll use the security-auditor agent to analyze API responses for data leakage and over-fetching." <commentary> User asking about data exposure triggers the security-auditor agent with focus on data leakage. </commentary> </example> <example> Context: User wants to review authentication security user: "Are our auth flows secure? Check for vulnerabilities" assistant: "I'll use the security-auditor agent to audit authentication and authorization patterns." <commentary> User asking about auth security triggers the security-auditor agent. </commentary> </example>
Use this agent when you need expert guidance on UI/frontend development, including component architecture, responsive design, CSS patterns, performance optimization, accessibility, design system implementation, or modern framework usage (React, TypeScript, Next.js, TailwindCSS, Vue.js, Svelte). This agent excels at providing practical, production-ready solutions with code examples. <example> Context: User needs help with a UI component implementation user: "How should I create an interactive card component with hover effects?" assistant: "I'll use the ui-frontend-expert agent to provide you with a professional solution for your interactive card component." <commentary> The user is asking about UI component implementation, which is a core expertise of the ui-frontend-expert agent. </commentary> </example> <example> Context: User is working on performance optimization user: "My React app is slow, especially on mobile. What should I check?" assistant: "Let me engage the ui-frontend-expert agent to analyze common performance bottlenecks and provide optimization strategies." <commentary> Performance optimization for React applications falls directly within the ui-frontend-expert's domain. </commentary> </example> <example> Context: User needs design system guidance user: "We're starting a new project and need to set up a scalable component architecture" assistant: "I'll use the ui-frontend-expert agent to help you design a robust component architecture and design system." <commentary> Design systems and component architecture are key specialties of the ui-frontend-expert agent. </commentary> </example>
Review code for DRY, SOLID, and Clean Code violations. Use when the user asks to "review code", "code review", "check code quality", "/code-review". Also activates during /implement Phase 3.5 when code-simplifier agent is invoked.
Create Epic, Stories, and Tasks in the issue tracker from feature documentation or structured input. Triggers: "create tickets", "create issues from docs", "plan tickets", "/create-tickets".
Implement a feature from a ticket or local documentation with structured phases, quality gates, and optional ticket administration. Triggers: "implement", "work on #XX", "implement from docs", "/implement".
Plan a new feature through service design discovery and expert consultation. Generates feature documentation in docs/features/. Triggers: "plan feature", "design feature", "plan new feature", "/plan-feature".
Create professional Agile Epics, Stories, and Tasks with proper structure. Use when the user asks to "create epic", "write story", "add user story", "define acceptance criteria", "plan feature". Provides templates and best practices following vertical slice principles.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Internal Claude Code plugin marketplace for BrightHills.
| Component | Type | Invocation | Description |
|---|---|---|---|
| session | command | /bh:session | Create session summaries to preserve development context before /compact, or organize existing session files into a year/month/day hierarchy with --organize. |
| hook-logger | hook | (auto-active) | Logs all Claude Code hook events (PreToolUse, PostToolUse, Stop, SessionStart, SessionEnd, etc.) to .claude/hook_logs/{event}.jsonl for debugging and analytics. |
| Component | Type | Invocation | Description |
|---|---|---|---|
| story-writer | skill | /bh-agile:story-writer | Write professional Agile Epics, Stories, and Tasks following vertical slice principles with Given-When-Then acceptance criteria. |
| implement | skill | /bh-agile:implement | Implement a feature from a ticket (#45) or local documentation (@docs/features/auth/) with structured phases, quality gates, and optional ticket administration. |
| plan-feature | skill | /bh-agile:plan-feature | Plan a new feature through service design discovery and expert agent consultation. Generates feature documentation in docs/features/. |
| create-tickets | skill | /bh-agile:create-tickets | Create Epic, Stories, and Tasks in the issue tracker from feature documentation or structured input. |
| code-review | skill | /bh-agile:code-review | Review code for DRY, SOLID, and Clean Code violations. Also used during implement Phase 3.5. |
| setup | command | /bh-agile:setup | Project setup wizard: explores codebase, generates clean-code rules from skeletons, copies static rules, creates issue tracking labels (GitHub/GitLab), and generates a platform-specific ticket manager agent. |
| agile-ticket-manager | agent template | (generated by setup) | Manages Epic/Story/Task hierarchy with status propagation. Generated into .claude/agents/ with platform-specific commands (gh/glab). |
| qa-tester | agent | (auto-discovered) | Plans, creates, and executes E2E tests based on Story Acceptance Criteria. Analyzes AC to create test plans, writes test code, runs tests, and reports results. |
| security-auditor | agent | (auto-discovered) | Performs comprehensive security audits focusing on OWASP Top 10 vulnerabilities, data leakage, authentication flows, and sensitive data exposure. |
Workflow integration:
/plan-feature "auth system" → docs/features/auth/
/create-tickets @docs/features/auth/ → Epic #1, Stories #2-#5
/implement #2 OR /implement @docs/features/auth/ → Implementation
Additional resources in plugin:
| Resource | Path | Purpose |
|---|---|---|
| Rule skeletons | assets/rules/skeletons/ | Instructions for generating project-specific rules (e.g., clean-code) |
| Static rules | assets/rules/ | Pre-built rules copied with path customization (e.g., feature-docs) |
| Agent template | assets/agents/ | Agent template with placeholder-based assembly |
| Agent fragments | assets/agents/fragments/{github,gitlab}/ | Platform-specific command snippets for template assembly |
| Component | Type | Invocation | Description |
|---|---|---|---|
| setup | command | /bh-statusline:setup | Install the BrightHills custom status line script (~/.claude/statusline-command.sh) and configure Claude Code to use it. Checks for existing configuration and asks before overwriting. |
Displays: Model | Git branch | Context left [████░░░░░░] 72% | Directory | Output style
remaining_percentage for accuracyjqAll BrightHills skills use the bh prefix. Scoped skills use bh-<scope>:
/bh:skill-name/bh-agile:skill-name/plugin marketplace add https://github.com/brighthills/brighthills-cc-plugins.git
/plugin install bh@brighthills-cc-plugins-public
/plugin install bh-agile@brighthills-cc-plugins-public
/plugin install bh-statusline@brighthills-cc-plugins-public
npx claudepluginhub brighthills/brighthills-cc-plugins --plugin bh-agileBrightHills general-purpose tools: session summaries, context preservation, and hook event logging.
Custom Claude Code status line with model name, git branch, context window progress bar, working directory, and output style.
Project management agents — agile coach, delivery manager, progress tracking
agent-flow — Claude Code plugin for automated bug-fix, feature, and scaffold workflows. Issue tracker to merged PR via a pipeline of specialized AI agents.
Virtual development team: TDD, debugging, code review, backlog management, and proven workflow patterns
Spec-driven development for big features. When features get too big, plan mode gets too vague—leading to hallucinations during implementation. ShipSpec replaces vague plans with structured PRDs, technical designs, and ordered tasks that keep Claude grounded.
GitHub Project Management workflow for product development: PRD creation, epic/task breakdown, TDD execution, and QA planning
Helder's personal SDLC toolbelt for AI coding agents — from PRD to ship. Bundles the tracer-bullet workflow alongside TDD, code review, audits, and shipping skills.