kiro-agent-team 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.kiro/README.md +228 -0
- package/.kiro/agents/backend-engineer.json +6 -0
- package/.kiro/agents/backend-engineer.md +643 -0
- package/.kiro/agents/database-specialist.json +6 -0
- package/.kiro/agents/database-specialist.md +390 -0
- package/.kiro/agents/development-logger.json +6 -0
- package/.kiro/agents/development-logger.md +265 -0
- package/.kiro/agents/devops-engineer.json +6 -0
- package/.kiro/agents/devops-engineer.md +287 -0
- package/.kiro/agents/frontend-architect.json +6 -0
- package/.kiro/agents/frontend-architect.md +1032 -0
- package/.kiro/agents/hooks/backend-engineer-hooks.yaml +540 -0
- package/.kiro/agents/hooks/database-specialist-hooks.yaml +488 -0
- package/.kiro/agents/hooks/development-logger-hooks.yaml +361 -0
- package/.kiro/agents/hooks/devops-engineer-hooks.yaml +345 -0
- package/.kiro/agents/hooks/frontend-architect-hooks.yaml +521 -0
- package/.kiro/agents/hooks/project-manager-hooks.yaml +513 -0
- package/.kiro/agents/hooks/security-specialist-hooks.yaml +358 -0
- package/.kiro/agents/hooks/test-orchestrator-hooks.yaml +380 -0
- package/.kiro/agents/hooks/ui-ux-designer-hooks.yaml +353 -0
- package/.kiro/agents/project-manager.json +6 -0
- package/.kiro/agents/project-manager.md +344 -0
- package/.kiro/agents/prompts/backend-engineer-system.md +815 -0
- package/.kiro/agents/prompts/database-specialist-system.md +332 -0
- package/.kiro/agents/prompts/development-logger-system.md +232 -0
- package/.kiro/agents/prompts/devops-engineer-system.md +260 -0
- package/.kiro/agents/prompts/frontend-architect-system.md +305 -0
- package/.kiro/agents/prompts/project-manager-system.md +285 -0
- package/.kiro/agents/prompts/security-specialist-system.md +231 -0
- package/.kiro/agents/prompts/test-orchestrator-system.md +214 -0
- package/.kiro/agents/prompts/ui-ux-designer-system.md +270 -0
- package/.kiro/agents/security-specialist.json +6 -0
- package/.kiro/agents/security-specialist.md +277 -0
- package/.kiro/agents/test-orchestrator.json +6 -0
- package/.kiro/agents/test-orchestrator.md +266 -0
- package/.kiro/agents/ui-ux-designer.json +6 -0
- package/.kiro/agents/ui-ux-designer.md +284 -0
- package/.kiro/devlog/00-START-HERE.md +444 -0
- package/.kiro/devlog/COMPLETE-WORKFLOW.md +553 -0
- package/.kiro/devlog/DEVLOG-INTEGRATION.md +413 -0
- package/.kiro/devlog/DEVLOG-PROCESS-FLOWS.md +484 -0
- package/.kiro/devlog/DEVLOG-QUICK-REF.md +299 -0
- package/.kiro/devlog/DEVLOG.md +22 -0
- package/.kiro/devlog/IMPLEMENTATION-COMPLETE.txt +434 -0
- package/.kiro/devlog/IMPLEMENTATION-SUMMARY.md +358 -0
- package/.kiro/devlog/README.md +363 -0
- package/.kiro/devlog/devlog-update.bat +136 -0
- package/.kiro/devlog/devlog-update.sh +275 -0
- package/.kiro/devlog/feature-completion-hook.bat +78 -0
- package/.kiro/devlog/feature-completion-hook.sh +84 -0
- package/.kiro/documentation/cli.md +31 -0
- package/.kiro/documentation/docs_cli.md +41 -0
- package/.kiro/documentation/docs_cli_authentication.md +43 -0
- package/.kiro/documentation/docs_cli_autocomplete.md +132 -0
- package/.kiro/documentation/docs_cli_billing.md +31 -0
- package/.kiro/documentation/docs_cli_billing_contact-support.md +43 -0
- package/.kiro/documentation/docs_cli_billing_managing-taxes.md +67 -0
- package/.kiro/documentation/docs_cli_billing_related-questions.md +49 -0
- package/.kiro/documentation/docs_cli_billing_subscription-portal.md +31 -0
- package/.kiro/documentation/docs_cli_chat.md +84 -0
- package/.kiro/documentation/docs_cli_chat_configuration.md +40 -0
- package/.kiro/documentation/docs_cli_chat_context.md +258 -0
- package/.kiro/documentation/docs_cli_chat_git-aware-selection.md +41 -0
- package/.kiro/documentation/docs_cli_chat_images.md +53 -0
- package/.kiro/documentation/docs_cli_chat_manage-prompts.md +216 -0
- package/.kiro/documentation/docs_cli_chat_model-selection.md +153 -0
- package/.kiro/documentation/docs_cli_chat_permissions.md +68 -0
- package/.kiro/documentation/docs_cli_chat_planning-agent.md +230 -0
- package/.kiro/documentation/docs_cli_chat_responding.md +123 -0
- package/.kiro/documentation/docs_cli_chat_security.md +87 -0
- package/.kiro/documentation/docs_cli_chat_subagents.md +77 -0
- package/.kiro/documentation/docs_cli_code-intelligence.md +251 -0
- package/.kiro/documentation/docs_cli_custom-agents.md +37 -0
- package/.kiro/documentation/docs_cli_custom-agents_configuration-reference.md +941 -0
- package/.kiro/documentation/docs_cli_custom-agents_creating.md +93 -0
- package/.kiro/documentation/docs_cli_custom-agents_examples.md +360 -0
- package/.kiro/documentation/docs_cli_custom-agents_troubleshooting.md +180 -0
- package/.kiro/documentation/docs_cli_enterprise_billing.md +33 -0
- package/.kiro/documentation/docs_cli_enterprise_concepts.md +34 -0
- package/.kiro/documentation/docs_cli_enterprise_getting-started.md +19 -0
- package/.kiro/documentation/docs_cli_enterprise_iam.md +251 -0
- package/.kiro/documentation/docs_cli_enterprise_monitor-and-track.md +15 -0
- package/.kiro/documentation/docs_cli_enterprise_monitor-and-track_dashboard.md +62 -0
- package/.kiro/documentation/docs_cli_enterprise_monitor-and-track_prompt-logging.md +165 -0
- package/.kiro/documentation/docs_cli_enterprise_monitor-and-track_user-activity.md +123 -0
- package/.kiro/documentation/docs_cli_enterprise_settings.md +15 -0
- package/.kiro/documentation/docs_cli_enterprise_subscribe.md +36 -0
- package/.kiro/documentation/docs_cli_enterprise_subscription-management.md +55 -0
- package/.kiro/documentation/docs_cli_enterprise_supported-regions.md +39 -0
- package/.kiro/documentation/docs_cli_experimental.md +282 -0
- package/.kiro/documentation/docs_cli_experimental_checkpointing.md +439 -0
- package/.kiro/documentation/docs_cli_experimental_delegate.md +422 -0
- package/.kiro/documentation/docs_cli_experimental_knowledge-management.md +449 -0
- package/.kiro/documentation/docs_cli_experimental_tangent-mode.md +357 -0
- package/.kiro/documentation/docs_cli_experimental_thinking.md +331 -0
- package/.kiro/documentation/docs_cli_experimental_todo-lists.md +385 -0
- package/.kiro/documentation/docs_cli_hooks.md +207 -0
- package/.kiro/documentation/docs_cli_installation.md +235 -0
- package/.kiro/documentation/docs_cli_mcp.md +106 -0
- package/.kiro/documentation/docs_cli_mcp_configuration.md +294 -0
- package/.kiro/documentation/docs_cli_mcp_examples.md +273 -0
- package/.kiro/documentation/docs_cli_mcp_governance.md +436 -0
- package/.kiro/documentation/docs_cli_mcp_security.md +77 -0
- package/.kiro/documentation/docs_cli_migrating-from-q.md +129 -0
- package/.kiro/documentation/docs_cli_privacy-and-security.md +83 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_compliance-validation.md +17 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_data-protection.md +104 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_firewalls.md +26 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_infrastructure-security.md +10 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_vpc-endpoints.md +41 -0
- package/.kiro/documentation/docs_cli_reference_built-in-tools.md +624 -0
- package/.kiro/documentation/docs_cli_reference_cli-commands.md +689 -0
- package/.kiro/documentation/docs_cli_reference_settings.md +294 -0
- package/.kiro/documentation/docs_cli_reference_slash-commands.md +559 -0
- package/.kiro/documentation/docs_cli_steering.md +84 -0
- package/.kiro/guides/AGENT_WORKFLOW_GUIDE.md +294 -0
- package/.kiro/guides/DEVLOG.md +882 -0
- package/.kiro/guides/IMPLEMENTATION_EXAMPLES.md +611 -0
- package/.kiro/guides/PIV Loop.md +122 -0
- package/.kiro/guides/PIV Loop.png +0 -0
- package/.kiro/guides/PIVLoop.png +0 -0
- package/.kiro/guides/QUICK_REFERENCE.md +202 -0
- package/.kiro/guides/README.md +149 -0
- package/.kiro/guides/advanced-patterns.md +514 -0
- package/.kiro/guides/agent-coordination.md +434 -0
- package/.kiro/guides/core-workflows.md +409 -0
- package/.kiro/guides/emergency-procedures.md +414 -0
- package/.kiro/guides/project-evaluation.md +534 -0
- package/.kiro/guides/quality-assurance.md +431 -0
- package/.kiro/guides/quick-start.md +235 -0
- package/.kiro/guides/troubleshooting.md +575 -0
- package/.kiro/guides/walkthroughs.md +711 -0
- package/.kiro/prompts/add-to-devlog.md +263 -0
- package/.kiro/prompts/code-review-fix.md +18 -0
- package/.kiro/prompts/code-review-hackathon.md +167 -0
- package/.kiro/prompts/code-review-security.md +454 -0
- package/.kiro/prompts/code-review.md +113 -0
- package/.kiro/prompts/create-prd.md +151 -0
- package/.kiro/prompts/execute-backend.md +257 -0
- package/.kiro/prompts/execute-frontend.md +438 -0
- package/.kiro/prompts/execute-logging.md +491 -0
- package/.kiro/prompts/execute-security.md +482 -0
- package/.kiro/prompts/execute-testing.md +528 -0
- package/.kiro/prompts/execute.md +101 -0
- package/.kiro/prompts/execution-report.md +72 -0
- package/.kiro/prompts/implement-fix.md +228 -0
- package/.kiro/prompts/plan-feature.md +433 -0
- package/.kiro/prompts/prime.md +73 -0
- package/.kiro/prompts/quality-metrics.md +622 -0
- package/.kiro/prompts/quickstart.md +318 -0
- package/.kiro/prompts/rca.md +220 -0
- package/.kiro/prompts/system-review.md +189 -0
- package/README.md +32 -0
- package/bin/cli.js +97 -0
- package/package.json +33 -0
|
@@ -0,0 +1,521 @@
|
|
|
1
|
+
# Frontend Architect Agent Hooks Configuration
|
|
2
|
+
# Automated triggers for UI/UX development and component management
|
|
3
|
+
|
|
4
|
+
hooks:
|
|
5
|
+
# Initial Consultation and Discovery
|
|
6
|
+
- name: "project-consultation-trigger"
|
|
7
|
+
description: "Trigger when starting a new frontend project or major feature"
|
|
8
|
+
trigger:
|
|
9
|
+
type: "message"
|
|
10
|
+
pattern: "(?i)(new project|start|begin|frontend|ui|interface|website|app)"
|
|
11
|
+
action:
|
|
12
|
+
type: "message"
|
|
13
|
+
content: |
|
|
14
|
+
🎯 **Frontend Architect Consultation Started**
|
|
15
|
+
|
|
16
|
+
Before we dive into implementation, let me understand your requirements:
|
|
17
|
+
|
|
18
|
+
**🔧 Technology Stack Preferences:**
|
|
19
|
+
- Frontend Framework: React | Vue | Angular | Svelte | Other?
|
|
20
|
+
- Language: TypeScript (recommended) | JavaScript?
|
|
21
|
+
- Styling Approach: Tailwind | Material-UI | Styled Components | Custom CSS?
|
|
22
|
+
- State Management: Redux | Zustand | Context API | Framework-specific?
|
|
23
|
+
|
|
24
|
+
**🎨 Design & Branding:**
|
|
25
|
+
- Do you have existing brand guidelines or design system?
|
|
26
|
+
- Color palette preferences (primary, secondary, accent colors)?
|
|
27
|
+
- Typography requirements (font families, sizing approach)?
|
|
28
|
+
- Design aesthetic: Modern | Minimal | Corporate | Playful | Other?
|
|
29
|
+
- Dark mode support needed?
|
|
30
|
+
|
|
31
|
+
**👥 User Experience Requirements:**
|
|
32
|
+
- Target audience and primary use cases?
|
|
33
|
+
- Device priorities: Mobile-first | Desktop-focused | Both equally?
|
|
34
|
+
- Browser support requirements?
|
|
35
|
+
- Accessibility compliance level needed?
|
|
36
|
+
- Performance targets (loading times, bundle size)?
|
|
37
|
+
|
|
38
|
+
**📋 Project Context:**
|
|
39
|
+
- Timeline and development phases?
|
|
40
|
+
- Team expertise level with frontend technologies?
|
|
41
|
+
- Integration requirements (APIs, existing systems)?
|
|
42
|
+
- Any specific constraints or preferences?
|
|
43
|
+
|
|
44
|
+
Once I understand these requirements, I'll provide tailored recommendations and implementation strategies!
|
|
45
|
+
|
|
46
|
+
- name: "technology-recommendation-trigger"
|
|
47
|
+
description: "Trigger when technology stack recommendations are needed"
|
|
48
|
+
trigger:
|
|
49
|
+
type: "message"
|
|
50
|
+
pattern: "(?i)(recommend|suggest|choose|select).*(framework|library|technology|stack|tool)"
|
|
51
|
+
action:
|
|
52
|
+
type: "message"
|
|
53
|
+
content: |
|
|
54
|
+
🔍 **Technology Stack Consultation**
|
|
55
|
+
|
|
56
|
+
I'll help you choose the optimal frontend technology stack. Let me ask a few key questions:
|
|
57
|
+
|
|
58
|
+
**Project Requirements Assessment:**
|
|
59
|
+
1. **Complexity Level**: Simple landing page | Interactive app | Complex enterprise system?
|
|
60
|
+
2. **Team Expertise**: Beginner | Intermediate | Advanced frontend developers?
|
|
61
|
+
3. **Timeline**: Rapid prototype | Standard development | Long-term project?
|
|
62
|
+
4. **Performance Needs**: Standard | High-performance | Real-time features?
|
|
63
|
+
5. **Maintenance**: Short-term | Long-term maintenance expected?
|
|
64
|
+
|
|
65
|
+
**Technology Preferences:**
|
|
66
|
+
- Any existing framework experience or organizational preferences?
|
|
67
|
+
- TypeScript comfort level (strongly recommended for larger projects)?
|
|
68
|
+
- Styling preference: Utility-first | Component libraries | Custom CSS?
|
|
69
|
+
- State complexity: Simple local state | Complex app state | Real-time data?
|
|
70
|
+
|
|
71
|
+
**Integration Requirements:**
|
|
72
|
+
- Existing backend APIs or services to integrate?
|
|
73
|
+
- Authentication requirements?
|
|
74
|
+
- Real-time features needed (WebSockets, live updates)?
|
|
75
|
+
- Third-party service integrations?
|
|
76
|
+
|
|
77
|
+
Based on your answers, I'll recommend the optimal stack with detailed reasoning!
|
|
78
|
+
|
|
79
|
+
- name: "design-consultation-trigger"
|
|
80
|
+
description: "Trigger when design and theming consultation is needed"
|
|
81
|
+
trigger:
|
|
82
|
+
type: "message"
|
|
83
|
+
pattern: "(?i)(design|theme|branding|colors|fonts|style|look|feel|ui|ux)"
|
|
84
|
+
action:
|
|
85
|
+
type: "message"
|
|
86
|
+
content: |
|
|
87
|
+
🎨 **Design & Theming Consultation**
|
|
88
|
+
|
|
89
|
+
Let's create a beautiful, cohesive user experience! I need to understand your design vision:
|
|
90
|
+
|
|
91
|
+
**🎯 Brand & Visual Identity:**
|
|
92
|
+
- Do you have existing brand guidelines, logos, or design assets?
|
|
93
|
+
- What's your desired aesthetic? (Modern, minimal, corporate, playful, elegant, etc.)
|
|
94
|
+
- Any competitor sites or designs you admire? (Please share examples)
|
|
95
|
+
- Target audience and their expectations?
|
|
96
|
+
|
|
97
|
+
**🌈 Color & Typography:**
|
|
98
|
+
- Primary brand colors (hex codes if available)?
|
|
99
|
+
- Secondary/accent colors preferences?
|
|
100
|
+
- Font preferences: Sans-serif | Serif | Monospace | Custom fonts?
|
|
101
|
+
- Typography hierarchy needs (headings, body text, captions)?
|
|
102
|
+
|
|
103
|
+
**📱 Layout & Interaction:**
|
|
104
|
+
- Layout style: Clean/minimal | Rich/detailed | Card-based | List-based?
|
|
105
|
+
- Component styling: Rounded corners | Sharp edges | Shadows | Flat design?
|
|
106
|
+
- Animation preferences: Subtle | Dynamic | Minimal | None?
|
|
107
|
+
- Dark mode support required?
|
|
108
|
+
|
|
109
|
+
**♿ Accessibility & Usability:**
|
|
110
|
+
- Accessibility compliance level needed (WCAG 2.0 AA, 2.1 AAA)?
|
|
111
|
+
- Color contrast requirements?
|
|
112
|
+
- Keyboard navigation importance?
|
|
113
|
+
- Screen reader support needed?
|
|
114
|
+
|
|
115
|
+
**📐 Design System Approach:**
|
|
116
|
+
- Custom design system | Adapted component library | Utility-first approach?
|
|
117
|
+
- Consistency requirements across different sections/pages?
|
|
118
|
+
- Future scalability and maintenance considerations?
|
|
119
|
+
|
|
120
|
+
With these details, I'll create a comprehensive design strategy and implementation plan!
|
|
121
|
+
|
|
122
|
+
# Component Development Lifecycle
|
|
123
|
+
- name: "systematic_frontend_implementation"
|
|
124
|
+
description: "Execute systematic frontend development using standardized framework"
|
|
125
|
+
trigger:
|
|
126
|
+
type: "user_command"
|
|
127
|
+
conditions:
|
|
128
|
+
- command: "execute"
|
|
129
|
+
- agent: "frontend-architect"
|
|
130
|
+
action:
|
|
131
|
+
type: "execute_prompt"
|
|
132
|
+
prompt: "execute.md"
|
|
133
|
+
message: "Executing systematic frontend development with comprehensive UI/UX validation and accessibility compliance..."
|
|
134
|
+
agent: "frontend-architect"
|
|
135
|
+
include_context:
|
|
136
|
+
- ui_requirements: true
|
|
137
|
+
- design_system: true
|
|
138
|
+
- accessibility_standards: true
|
|
139
|
+
- performance_targets: true
|
|
140
|
+
|
|
141
|
+
- name: "component-creation-trigger"
|
|
142
|
+
description: "Trigger when new UI components need to be created"
|
|
143
|
+
trigger:
|
|
144
|
+
type: "message"
|
|
145
|
+
pattern: "(?i)(create|build|implement).*(component|ui|interface|page|form)"
|
|
146
|
+
action:
|
|
147
|
+
type: "message"
|
|
148
|
+
content: |
|
|
149
|
+
🎨 **Frontend Architect Activated**
|
|
150
|
+
|
|
151
|
+
I'll help you create modern, accessible UI components. Use @execute for systematic implementation with:
|
|
152
|
+
|
|
153
|
+
1. **Analyze Requirements**: Understand the component specifications and user needs
|
|
154
|
+
2. **Design Architecture**: Plan component structure using atomic design principles
|
|
155
|
+
3. **Implement Components**: Build with React, TypeScript, and Tailwind CSS
|
|
156
|
+
4. **Ensure Accessibility**: Add ARIA attributes and keyboard navigation
|
|
157
|
+
5. **Integrate APIs**: Connect with Backend Engineer's endpoints efficiently
|
|
158
|
+
6. **Test Responsiveness**: Verify mobile-first responsive design
|
|
159
|
+
|
|
160
|
+
Ready to build exceptional user experiences! Use @execute to begin systematic implementation.
|
|
161
|
+
|
|
162
|
+
- name: "api-integration-trigger"
|
|
163
|
+
description: "Trigger when frontend needs to integrate with backend APIs"
|
|
164
|
+
trigger:
|
|
165
|
+
type: "message"
|
|
166
|
+
pattern: "(?i)(integrate|connect|consume).*(api|endpoint|backend|service)"
|
|
167
|
+
action:
|
|
168
|
+
type: "message"
|
|
169
|
+
content: |
|
|
170
|
+
🔌 **API Integration Specialist Ready**
|
|
171
|
+
|
|
172
|
+
I'll seamlessly connect your frontend with the backend APIs. My approach:
|
|
173
|
+
|
|
174
|
+
1. **API Analysis**: Review Backend Engineer's endpoint specifications
|
|
175
|
+
2. **State Management**: Implement Redux Toolkit with RTK Query for efficient data fetching
|
|
176
|
+
3. **Error Handling**: Add comprehensive error boundaries and user feedback
|
|
177
|
+
4. **Authentication**: Integrate JWT token management and protected routes
|
|
178
|
+
5. **Real-time Updates**: Connect WebSocket for live data synchronization
|
|
179
|
+
6. **Caching Strategy**: Optimize API calls with intelligent caching
|
|
180
|
+
|
|
181
|
+
**Integration Features:**
|
|
182
|
+
- Automatic token refresh handling
|
|
183
|
+
- Loading states and error messages
|
|
184
|
+
- Optimistic updates for better UX
|
|
185
|
+
- Request deduplication and caching
|
|
186
|
+
- Type-safe API client generation
|
|
187
|
+
|
|
188
|
+
Let's connect your UI to the backend efficiently!
|
|
189
|
+
|
|
190
|
+
- name: "responsive-design-trigger"
|
|
191
|
+
description: "Trigger when responsive design implementation is needed"
|
|
192
|
+
trigger:
|
|
193
|
+
type: "message"
|
|
194
|
+
pattern: "(?i)(responsive|mobile|tablet|desktop|breakpoint|grid|layout)"
|
|
195
|
+
action:
|
|
196
|
+
type: "message"
|
|
197
|
+
content: |
|
|
198
|
+
📱 **Responsive Design Expert Engaged**
|
|
199
|
+
|
|
200
|
+
I'll ensure your application works beautifully across all devices:
|
|
201
|
+
|
|
202
|
+
1. **Mobile-First Approach**: Start with mobile design, enhance for larger screens
|
|
203
|
+
2. **Flexible Grid Systems**: Implement CSS Grid and Flexbox layouts
|
|
204
|
+
3. **Breakpoint Strategy**: Define optimal breakpoints for all device sizes
|
|
205
|
+
4. **Touch Interactions**: Optimize for touch gestures and accessibility
|
|
206
|
+
5. **Performance**: Ensure fast loading on mobile networks
|
|
207
|
+
6. **Testing**: Verify across multiple devices and screen sizes
|
|
208
|
+
|
|
209
|
+
**Responsive Standards:**
|
|
210
|
+
- Mobile: 320px - 768px (touch-optimized)
|
|
211
|
+
- Tablet: 768px - 1024px (hybrid interactions)
|
|
212
|
+
- Desktop: 1024px+ (mouse/keyboard optimized)
|
|
213
|
+
- Large screens: 1440px+ (enhanced layouts)
|
|
214
|
+
|
|
215
|
+
Ready to create a seamless multi-device experience!
|
|
216
|
+
|
|
217
|
+
- name: "accessibility-audit-trigger"
|
|
218
|
+
description: "Trigger when accessibility improvements are needed"
|
|
219
|
+
trigger:
|
|
220
|
+
type: "message"
|
|
221
|
+
pattern: "(?i)(accessibility|a11y|wcag|screen reader|keyboard|aria)"
|
|
222
|
+
action:
|
|
223
|
+
type: "message"
|
|
224
|
+
content: |
|
|
225
|
+
♿ **Accessibility Champion Activated**
|
|
226
|
+
|
|
227
|
+
I'll ensure your application is inclusive and accessible to all users:
|
|
228
|
+
|
|
229
|
+
1. **WCAG Compliance**: Implement WCAG 2.1 AA standards throughout
|
|
230
|
+
2. **Keyboard Navigation**: Full keyboard accessibility for all interactions
|
|
231
|
+
3. **Screen Reader Support**: Proper ARIA labels and semantic HTML
|
|
232
|
+
4. **Color Contrast**: Ensure sufficient contrast ratios for readability
|
|
233
|
+
5. **Focus Management**: Clear focus indicators and logical tab order
|
|
234
|
+
6. **Alternative Text**: Descriptive alt text for images and media
|
|
235
|
+
|
|
236
|
+
**Accessibility Checklist:**
|
|
237
|
+
- ✅ Semantic HTML structure
|
|
238
|
+
- ✅ ARIA attributes and roles
|
|
239
|
+
- ✅ Keyboard navigation support
|
|
240
|
+
- ✅ Color contrast compliance
|
|
241
|
+
- ✅ Screen reader compatibility
|
|
242
|
+
- ✅ Focus management
|
|
243
|
+
|
|
244
|
+
Let's build an inclusive experience for everyone!
|
|
245
|
+
|
|
246
|
+
- name: "performance-optimization-trigger"
|
|
247
|
+
description: "Trigger when frontend performance optimization is needed"
|
|
248
|
+
trigger:
|
|
249
|
+
type: "message"
|
|
250
|
+
pattern: "(?i)(performance|optimize|slow|loading|bundle|speed|lighthouse)"
|
|
251
|
+
action:
|
|
252
|
+
type: "message"
|
|
253
|
+
content: |
|
|
254
|
+
⚡ **Performance Optimization Specialist Ready**
|
|
255
|
+
|
|
256
|
+
I'll optimize your frontend for lightning-fast performance:
|
|
257
|
+
|
|
258
|
+
1. **Bundle Analysis**: Analyze and optimize bundle size with code splitting
|
|
259
|
+
2. **Lazy Loading**: Implement component and route-based lazy loading
|
|
260
|
+
3. **Image Optimization**: Optimize images with modern formats and lazy loading
|
|
261
|
+
4. **Caching Strategy**: Implement efficient browser and API caching
|
|
262
|
+
5. **Core Web Vitals**: Optimize LCP, FID, and CLS metrics
|
|
263
|
+
6. **Memory Management**: Prevent memory leaks and optimize re-renders
|
|
264
|
+
|
|
265
|
+
**Performance Targets:**
|
|
266
|
+
- First Contentful Paint: < 1.5s
|
|
267
|
+
- Largest Contentful Paint: < 2.5s
|
|
268
|
+
- First Input Delay: < 100ms
|
|
269
|
+
- Cumulative Layout Shift: < 0.1
|
|
270
|
+
- Bundle size: Optimized with tree shaking
|
|
271
|
+
|
|
272
|
+
Ready to make your app blazingly fast!
|
|
273
|
+
|
|
274
|
+
# Development Workflow Hooks
|
|
275
|
+
- name: "component-testing-trigger"
|
|
276
|
+
description: "Trigger when component testing is needed"
|
|
277
|
+
trigger:
|
|
278
|
+
type: "message"
|
|
279
|
+
pattern: "(?i)(test|testing|jest|cypress|playwright).*(component|ui|frontend)"
|
|
280
|
+
action:
|
|
281
|
+
type: "message"
|
|
282
|
+
content: |
|
|
283
|
+
🧪 **Component Testing Specialist Engaged**
|
|
284
|
+
|
|
285
|
+
I'll ensure your components are thoroughly tested and reliable:
|
|
286
|
+
|
|
287
|
+
1. **Unit Testing**: Jest and React Testing Library for component logic
|
|
288
|
+
2. **Integration Testing**: Test component interactions and API integration
|
|
289
|
+
3. **Visual Testing**: Storybook for component documentation and visual regression
|
|
290
|
+
4. **E2E Testing**: Coordinate with Test Orchestrator for end-to-end scenarios
|
|
291
|
+
5. **Accessibility Testing**: Automated a11y testing with jest-axe
|
|
292
|
+
6. **Performance Testing**: Component rendering performance benchmarks
|
|
293
|
+
|
|
294
|
+
**Testing Strategy:**
|
|
295
|
+
- Component behavior and props handling
|
|
296
|
+
- User interactions and event handling
|
|
297
|
+
- API integration and error states
|
|
298
|
+
- Accessibility compliance
|
|
299
|
+
- Visual consistency across browsers
|
|
300
|
+
|
|
301
|
+
Let's build confidence in your UI components!
|
|
302
|
+
|
|
303
|
+
- name: "design-system-trigger"
|
|
304
|
+
description: "Trigger when design system work is needed"
|
|
305
|
+
trigger:
|
|
306
|
+
type: "message"
|
|
307
|
+
pattern: "(?i)(design system|component library|tokens|theme|branding|style guide)"
|
|
308
|
+
action:
|
|
309
|
+
type: "message"
|
|
310
|
+
content: |
|
|
311
|
+
🎨 **Design System Architect Activated**
|
|
312
|
+
|
|
313
|
+
I'll help you build a cohesive, scalable design system:
|
|
314
|
+
|
|
315
|
+
1. **Design Tokens**: Define colors, typography, spacing, and elevation scales
|
|
316
|
+
2. **Component Library**: Build reusable, documented component collection
|
|
317
|
+
3. **Theme System**: Implement dark/light mode and customizable themes
|
|
318
|
+
4. **Documentation**: Create comprehensive component usage guidelines
|
|
319
|
+
5. **Consistency**: Ensure visual and interaction consistency across the app
|
|
320
|
+
6. **Scalability**: Design for future growth and team collaboration
|
|
321
|
+
|
|
322
|
+
**Design System Components:**
|
|
323
|
+
- Atomic elements (buttons, inputs, icons)
|
|
324
|
+
- Molecular components (forms, cards, navigation)
|
|
325
|
+
- Layout systems (grids, containers, spacing)
|
|
326
|
+
- Theme configuration and customization
|
|
327
|
+
- Usage documentation and examples
|
|
328
|
+
|
|
329
|
+
Ready to create a unified design language!
|
|
330
|
+
|
|
331
|
+
# Collaboration Hooks
|
|
332
|
+
- name: "backend-coordination-trigger"
|
|
333
|
+
description: "Trigger when coordination with Backend Engineer is needed"
|
|
334
|
+
trigger:
|
|
335
|
+
type: "message"
|
|
336
|
+
pattern: "(?i)(backend|api|endpoint|database|server).*(frontend|ui|integration)"
|
|
337
|
+
action:
|
|
338
|
+
type: "message"
|
|
339
|
+
content: |
|
|
340
|
+
🤝 **Backend-Frontend Coordination Initiated**
|
|
341
|
+
|
|
342
|
+
I'll work closely with the Backend Engineer to ensure seamless integration:
|
|
343
|
+
|
|
344
|
+
**Coordination Areas:**
|
|
345
|
+
1. **API Contract Review**: Validate endpoint specifications and data formats
|
|
346
|
+
2. **Authentication Flow**: Align JWT implementation and protected routes
|
|
347
|
+
3. **Error Handling**: Standardize error responses and user feedback
|
|
348
|
+
4. **Real-time Features**: Coordinate WebSocket implementation
|
|
349
|
+
5. **Data Validation**: Ensure client-side validation matches backend rules
|
|
350
|
+
6. **Performance**: Optimize API usage patterns and caching strategies
|
|
351
|
+
|
|
352
|
+
**Integration Checklist:**
|
|
353
|
+
- ✅ API endpoint documentation review
|
|
354
|
+
- ✅ Authentication token handling
|
|
355
|
+
- ✅ Error response standardization
|
|
356
|
+
- ✅ Loading states and user feedback
|
|
357
|
+
- ✅ Data transformation and validation
|
|
358
|
+
- ✅ Real-time update mechanisms
|
|
359
|
+
|
|
360
|
+
Let's create a perfectly integrated fullstack experience!
|
|
361
|
+
|
|
362
|
+
- name: "database-ui-coordination-trigger"
|
|
363
|
+
description: "Trigger when UI needs to reflect database structure"
|
|
364
|
+
trigger:
|
|
365
|
+
type: "message"
|
|
366
|
+
pattern: "(?i)(database|schema|model|entity).*(ui|form|display|table)"
|
|
367
|
+
action:
|
|
368
|
+
type: "message"
|
|
369
|
+
content: |
|
|
370
|
+
🗄️ **Database-UI Alignment Specialist Ready**
|
|
371
|
+
|
|
372
|
+
I'll ensure your UI perfectly reflects the database structure and relationships:
|
|
373
|
+
|
|
374
|
+
**Database-UI Mapping:**
|
|
375
|
+
1. **Form Generation**: Create forms that match database schema constraints
|
|
376
|
+
2. **Relationship Display**: Show entity relationships in intuitive UI patterns
|
|
377
|
+
3. **Data Validation**: Implement client-side validation matching DB rules
|
|
378
|
+
4. **Search & Filtering**: Build UI that leverages database indexes efficiently
|
|
379
|
+
5. **Data Visualization**: Present complex data relationships clearly
|
|
380
|
+
6. **CRUD Operations**: Design intuitive interfaces for data management
|
|
381
|
+
|
|
382
|
+
**UI Patterns for Database Operations:**
|
|
383
|
+
- Master-detail views for related entities
|
|
384
|
+
- Searchable dropdowns for foreign key relationships
|
|
385
|
+
- Bulk operations with progress indicators
|
|
386
|
+
- Data tables with sorting and filtering
|
|
387
|
+
- Form wizards for complex data entry
|
|
388
|
+
|
|
389
|
+
Ready to create data-driven user interfaces!
|
|
390
|
+
|
|
391
|
+
# Quality Assurance Hooks
|
|
392
|
+
- name: "code-review-trigger"
|
|
393
|
+
description: "Trigger when frontend code review is needed"
|
|
394
|
+
trigger:
|
|
395
|
+
type: "file_save"
|
|
396
|
+
pattern: "\\.(tsx?|jsx?|css|scss)$"
|
|
397
|
+
action:
|
|
398
|
+
type: "message"
|
|
399
|
+
content: |
|
|
400
|
+
👀 **Frontend Code Review Initiated**
|
|
401
|
+
|
|
402
|
+
Automatically reviewing your frontend code for:
|
|
403
|
+
|
|
404
|
+
**Code Quality Checks:**
|
|
405
|
+
- TypeScript type safety and interfaces
|
|
406
|
+
- Component prop validation and defaults
|
|
407
|
+
- Accessibility attributes and semantic HTML
|
|
408
|
+
- Performance optimizations and anti-patterns
|
|
409
|
+
- Design system consistency
|
|
410
|
+
- Error handling and loading states
|
|
411
|
+
|
|
412
|
+
**Best Practices Verification:**
|
|
413
|
+
- Component composition and reusability
|
|
414
|
+
- State management patterns
|
|
415
|
+
- API integration efficiency
|
|
416
|
+
- CSS organization and naming conventions
|
|
417
|
+
- Test coverage and documentation
|
|
418
|
+
|
|
419
|
+
I'll provide specific feedback and improvement suggestions!
|
|
420
|
+
|
|
421
|
+
- name: "deployment-readiness-trigger"
|
|
422
|
+
description: "Trigger when frontend is ready for deployment"
|
|
423
|
+
trigger:
|
|
424
|
+
type: "message"
|
|
425
|
+
pattern: "(?i)(deploy|deployment|build|production|release)"
|
|
426
|
+
action:
|
|
427
|
+
type: "message"
|
|
428
|
+
content: |
|
|
429
|
+
🚀 **Deployment Readiness Assessment**
|
|
430
|
+
|
|
431
|
+
I'll ensure your frontend is production-ready:
|
|
432
|
+
|
|
433
|
+
**Pre-Deployment Checklist:**
|
|
434
|
+
1. **Build Optimization**: Verify bundle size and code splitting
|
|
435
|
+
2. **Performance Audit**: Run Lighthouse and Core Web Vitals checks
|
|
436
|
+
3. **Accessibility Compliance**: Final a11y audit and testing
|
|
437
|
+
4. **Cross-Browser Testing**: Verify compatibility across browsers
|
|
438
|
+
5. **Mobile Responsiveness**: Test on various device sizes
|
|
439
|
+
6. **Error Handling**: Ensure graceful error states and fallbacks
|
|
440
|
+
|
|
441
|
+
**Production Optimizations:**
|
|
442
|
+
- ✅ Minified and compressed assets
|
|
443
|
+
- ✅ Optimized images and lazy loading
|
|
444
|
+
- ✅ Service worker for caching (if applicable)
|
|
445
|
+
- ✅ Environment-specific configurations
|
|
446
|
+
- ✅ Analytics and monitoring setup
|
|
447
|
+
- ✅ SEO optimization and meta tags
|
|
448
|
+
|
|
449
|
+
Ready to launch your exceptional user experience!
|
|
450
|
+
|
|
451
|
+
# Learning and Improvement Hooks
|
|
452
|
+
- name: "devlog-contribution-trigger"
|
|
453
|
+
description: "Trigger to contribute frontend insights to development log"
|
|
454
|
+
trigger:
|
|
455
|
+
type: "agent_completion"
|
|
456
|
+
agent: "frontend-architect"
|
|
457
|
+
action:
|
|
458
|
+
type: "message"
|
|
459
|
+
content: |
|
|
460
|
+
📝 **Frontend Development Insights for DevLog**
|
|
461
|
+
|
|
462
|
+
Contributing frontend-specific insights to the development log:
|
|
463
|
+
|
|
464
|
+
**UI/UX Achievements:**
|
|
465
|
+
- Component architecture decisions and patterns used
|
|
466
|
+
- Accessibility improvements and WCAG compliance measures
|
|
467
|
+
- Performance optimizations and bundle size reductions
|
|
468
|
+
- Responsive design implementations and breakpoint strategies
|
|
469
|
+
- User experience enhancements and interaction patterns
|
|
470
|
+
|
|
471
|
+
**Technical Decisions:**
|
|
472
|
+
- State management choices and data flow patterns
|
|
473
|
+
- API integration strategies and error handling approaches
|
|
474
|
+
- Design system evolution and component library growth
|
|
475
|
+
- Testing strategies and coverage improvements
|
|
476
|
+
- Build optimization and deployment considerations
|
|
477
|
+
|
|
478
|
+
**Collaboration Insights:**
|
|
479
|
+
- Backend integration challenges and solutions
|
|
480
|
+
- Database-UI alignment strategies
|
|
481
|
+
- Cross-agent coordination effectiveness
|
|
482
|
+
- User feedback incorporation and iteration cycles
|
|
483
|
+
|
|
484
|
+
These insights will help improve future frontend development workflows!
|
|
485
|
+
|
|
486
|
+
- name: "quality_metrics_collection"
|
|
487
|
+
description: "Collect frontend-specific quality metrics and user experience data"
|
|
488
|
+
trigger:
|
|
489
|
+
type: "component_deployment"
|
|
490
|
+
conditions:
|
|
491
|
+
- deployment_type: ["staging", "production"]
|
|
492
|
+
action:
|
|
493
|
+
type: "execute_prompt"
|
|
494
|
+
prompt: "quality-metrics.md"
|
|
495
|
+
message: "Collecting frontend quality metrics: performance, accessibility, and user experience..."
|
|
496
|
+
agent: "frontend-architect"
|
|
497
|
+
include_context:
|
|
498
|
+
- performance_metrics: true
|
|
499
|
+
- accessibility_scores: true
|
|
500
|
+
- user_experience_data: true
|
|
501
|
+
|
|
502
|
+
# Hook Configuration Metadata
|
|
503
|
+
metadata:
|
|
504
|
+
agent: "frontend-architect"
|
|
505
|
+
version: "1.0"
|
|
506
|
+
created: "2026-01-04"
|
|
507
|
+
description: "Comprehensive hook configuration for Frontend Architect Agent covering UI development, API integration, accessibility, performance, and team collaboration"
|
|
508
|
+
|
|
509
|
+
# Hook Categories
|
|
510
|
+
categories:
|
|
511
|
+
- component-development
|
|
512
|
+
- api-integration
|
|
513
|
+
- responsive-design
|
|
514
|
+
- accessibility
|
|
515
|
+
- performance-optimization
|
|
516
|
+
- testing
|
|
517
|
+
- design-systems
|
|
518
|
+
- collaboration
|
|
519
|
+
- quality-assurance
|
|
520
|
+
- deployment
|
|
521
|
+
- learning
|