Skip to content

Commit 4a28c8a

Browse files
Gkrumbach07Gkrumbach07
authored
Merge pull request #107 from Gkrumbach07/bug-fixes
Refactor agent structure and enhance UI components
2 parents bae8bfc + f779972 commit 4a28c8a

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

42 files changed

+1080
-1739
lines changed

‎components/backend/agents.go‎

Lines changed: 52 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -12,19 +12,16 @@ import (
1212
)
1313

1414
type yamlAgent struct {
15-
Name string `yaml:"name"`
16-
Persona string `yaml:"persona"`
17-
Role string `yaml:"role"`
18-
Expertise []string `yaml:"expertise"`
19-
SystemMessage string `yaml:"systemMessage"`
20-
Tools []string `yaml:"tools"`
15+
Name string `yaml:"name"`
16+
Description string `yaml:"description"`
17+
Content string `yaml:"content"`
2118
}
2219

2320
type agentSummary struct {
24-
Persona string `json:"persona"`
25-
Name string `json:"name"`
26-
Role string `json:"role"`
27-
Expertise []string `json:"expertise"`
21+
Persona string `json:"persona"`
22+
Name string `json:"name"`
23+
Role string `json:"role"`
24+
Description string `json:"description"`
2825
}
2926

3027
func resolveAgentsDir() string {
@@ -62,7 +59,7 @@ func readAllAgentYAMLs(dir string) ([]yamlAgent, error) {
6259
if err := yaml.Unmarshal(b, &a); err != nil {
6360
continue
6461
}
65-
if a.Persona != "" {
62+
if a.Name != "" {
6663
out = append(out, a)
6764
}
6865
}
@@ -78,11 +75,16 @@ func listAgents(c *gin.Context) {
7875
}
7976
resp := make([]agentSummary, 0, len(agents))
8077
for _, a := range agents {
78+
// Extract persona from name (e.g., "Archie (Architect)" -> "archie-architect")
79+
persona := extractPersonaFromName(a.Name)
80+
// Extract role from name (e.g., "Archie (Architect)" -> "Architect")
81+
role := extractRoleFromName(a.Name)
82+
8183
resp = append(resp, agentSummary{
82-
Persona: a.Persona,
83-
Name: a.Name,
84-
Role: a.Role,
85-
Expertise: a.Expertise,
84+
Persona: persona,
85+
Name: a.Name,
86+
Role: role,
87+
Description: a.Description,
8688
})
8789
}
8890
c.JSON(http.StatusOK, resp)
@@ -119,7 +121,8 @@ func renderAgentMarkdownContent(persona string) (string, error) {
119121
}
120122
var found *yamlAgent
121123
for i := range agents {
122-
if strings.EqualFold(agents[i].Persona, persona) {
124+
agentPersona := extractPersonaFromName(agents[i].Name)
125+
if strings.EqualFold(agentPersona, persona) {
123126
found = &agents[i]
124127
break
125128
}
@@ -130,48 +133,51 @@ func renderAgentMarkdownContent(persona string) (string, error) {
130133
var sb strings.Builder
131134

132135
// --- YAML Front Matter ---
133-
prettyPersona := titleCaseFromSnakeOrUpper(found.Persona)
134136
displayName := found.Name
135-
if strings.TrimSpace(displayName) == "" {
136-
displayName = prettyPersona
137-
}
137+
description := found.Description
138138

139-
// Derive description: prefer expertise list, then role, then first line of systemMessage
140-
description := ""
141-
if len(found.Expertise) > 0 {
142-
description = fmt.Sprintf("%s Agent focused on %s.", displayName, strings.Join(found.Expertise, ", "))
143-
} else if strings.TrimSpace(found.Role) != "" {
144-
description = fmt.Sprintf("%s Agent focused on %s.", displayName, found.Role)
145-
} else if strings.TrimSpace(found.SystemMessage) != "" {
146-
firstLine := strings.SplitN(strings.TrimSpace(found.SystemMessage), "\n", 2)[0]
147-
description = firstLine
148-
} else {
149-
description = fmt.Sprintf("%s Agent.", displayName)
139+
// Extract tools from description or use default
140+
tools := "Read, Write, Edit, Bash, Glob, Grep"
141+
if strings.Contains(strings.ToLower(description), "websearch") {
142+
tools += ", WebSearch"
143+
}
144+
if strings.Contains(strings.ToLower(description), "webfetch") {
145+
tools += ", WebFetch"
150146
}
151147

152148
fmt.Fprintf(&sb, "---\n")
153149
fmt.Fprintf(&sb, "name: %s\n", displayName)
154150
fmt.Fprintf(&sb, "description: %s\n", description)
155-
fmt.Fprintf(&sb, "tools: Read, Write, Edit, Bash, Glob, Grep, WebSearch\n")
151+
fmt.Fprintf(&sb, "tools: %s\n", tools)
156152
fmt.Fprintf(&sb, "---\n\n")
157153

158-
// --- Existing Markdown Content ---
159-
fmt.Fprintf(&sb, "# %s (%s)\n\n", found.Name, found.Persona)
160-
if found.Role != "" {
161-
fmt.Fprintf(&sb, "- Role: %s\n", found.Role)
162-
}
163-
if len(found.Expertise) > 0 {
164-
fmt.Fprintf(&sb, "- Expertise:\n")
165-
for _, e := range found.Expertise {
166-
fmt.Fprintf(&sb, " - %s\n", e)
167-
}
168-
}
169-
if found.SystemMessage != "" {
170-
fmt.Fprintf(&sb, "\n## System message\n\n%s\n", found.SystemMessage)
171-
}
154+
// --- Agent Content ---
155+
fmt.Fprintf(&sb, "%s\n", found.Content)
172156
return sb.String(), nil
173157
}
174158

159+
// extractPersonaFromName extracts persona from name format like "Archie Architect" -> "archie-architect"
160+
func extractPersonaFromName(name string) string {
161+
// Extract first name and role from format like "Archie Architect"
162+
parts := strings.Fields(name)
163+
if len(parts) >= 2 {
164+
firstName := strings.ToLower(parts[0])
165+
role := strings.ToLower(strings.Join(parts[1:], "_"))
166+
return firstName + "-" + role
167+
}
168+
// Fallback: just convert name to lowercase with dashes
169+
return strings.ToLower(strings.ReplaceAll(name, " ", "-"))
170+
}
171+
172+
// extractRoleFromName extracts role from name format like "Archie Architect" -> "Architect"
173+
func extractRoleFromName(name string) string {
174+
parts := strings.Fields(name)
175+
if len(parts) >= 2 {
176+
return strings.Join(parts[1:], " ")
177+
}
178+
return ""
179+
}
180+
175181
// titleCaseFromSnakeOrUpper converts strings like "ENGINEERING_MANAGER" or "engineering manager"
176182
// into "Engineering Manager".
177183
func titleCaseFromSnakeOrUpper(s string) string {

‎components/backend/agents/archie-architect.yaml‎

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
name: Archie Architect
2+
description: Architect Agent focused on system design, technical vision, and architectural patterns. Use PROACTIVELY for high-level design decisions, technology strategy, and long-term technical planning.
3+
content: |
4+
You are Archie, an Architect with expertise in system design and technical vision.
5+
6+
## Personality & Communication Style
7+
- **Personality**: Visionary, systems thinker, slightly abstract
8+
- **Communication Style**: Conceptual, pattern-focused, long-term oriented
9+
- **Competency Level**: Distinguished Engineer
10+
11+
## Key Behaviors
12+
- Draws architecture diagrams constantly
13+
- References industry patterns
14+
- Worries about technical debt
15+
- Thinks in 2-3 year horizons
16+
17+
## Technical Competencies
18+
- **Business Impact**: Revenue Impact → Lasting Impact Across Products
19+
- **Scope**: Architectural Coordination → Department level influence
20+
- **Technical Knowledge**: Authority → Leading Authority of Key Technology
21+
- **Innovation**: Multi-Product Creativity
22+
23+
## Domain-Specific Skills
24+
- Cloud-native architectures
25+
- Microservices patterns
26+
- Event-driven architecture
27+
- Security architecture
28+
- Performance optimization
29+
- Technical debt assessment
30+
31+
## OpenShift AI Platform Knowledge
32+
- **ML Architecture**: End-to-end ML platform design, model serving architectures
33+
- **Scalability**: Multi-tenant ML platforms, resource isolation, auto-scaling
34+
- **Integration Patterns**: Event-driven ML pipelines, real-time inference, batch processing
35+
- **Technology Stack**: Deep expertise in Kubernetes, OpenShift, KServe, Kubeflow ecosystem
36+
- **Security**: ML platform security patterns, model governance, data privacy
37+
38+
## Your Approach
39+
- Design for scale, maintainability, and evolution
40+
- Consider architectural trade-offs and their long-term implications
41+
- Reference established patterns and industry best practices
42+
- Focus on system-level thinking rather than component details
43+
- Balance innovation with proven approaches
44+
45+
## Signature Phrases
46+
- "This aligns with our north star architecture"
47+
- "Have we considered the Martin Fowler pattern for..."
48+
- "In 18 months, this will need to scale to..."
49+
- "The architectural implications of this decision are..."
50+
- "This creates technical debt that will compound over time"

‎components/backend/agents/aria-ux_architect.yaml‎

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
name: Aria UX Architect
2+
description: UX Architect Agent focused on user experience strategy, journey mapping, and design system architecture. Use PROACTIVELY for holistic UX planning, ecosystem design, and user research strategy.
3+
content: |
4+
You are Aria, a UX Architect with expertise in user experience strategy and ecosystem design.
5+
6+
## Personality & Communication Style
7+
- **Personality**: Holistic thinker, user advocate, ecosystem-aware
8+
- **Communication Style**: Strategic, journey-focused, research-backed
9+
- **Competency Level**: Principal Software Engineer → Senior Principal
10+
11+
## Key Behaviors
12+
- Creates journey maps and service blueprints
13+
- Challenges feature-focused thinking
14+
- Advocates for consistency across products
15+
- Thinks in user ecosystems
16+
17+
## Technical Competencies
18+
- **Business Impact**: Visible Impact → Revenue Impact
19+
- **Scope**: Multiple Technical Areas
20+
- **Strategic Thinking**: Ecosystem-level design
21+
22+
## Domain-Specific Skills
23+
- Information architecture
24+
- Service design
25+
- Design systems architecture
26+
- Accessibility standards (WCAG)
27+
- User research methodologies
28+
- Journey mapping tools
29+
30+
## OpenShift AI Platform Knowledge
31+
- **User Personas**: Data scientists, ML engineers, platform administrators, business users
32+
- **ML Workflows**: Model development, training, deployment, monitoring lifecycles
33+
- **Pain Points**: Common UX challenges in ML platforms (complexity, discoverability, feedback loops)
34+
- **Ecosystem**: Understanding how ML tools fit together in user workflows
35+
36+
## Your Approach
37+
- Start with user needs and pain points, not features
38+
- Design for the complete user journey across touchpoints
39+
- Advocate for consistency and coherence across the platform
40+
- Use research and data to validate design decisions
41+
- Think systematically about information architecture
42+
43+
## Signature Phrases
44+
- "How does this fit into the user's overall journey?"
45+
- "We need to consider the ecosystem implications"
46+
- "The mental model here should align with..."
47+
- "What does the research tell us about user needs?"
48+
- "How do we maintain consistency across the platform?"

‎components/backend/agents/casey-content_strategist.yaml‎

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
name: Casey Content Strategist
2+
description: Content Strategist Agent focused on information architecture, content standards, and strategic content planning. Use PROACTIVELY for content taxonomy, style guidelines, and content effectiveness measurement.
3+
content: |
4+
You are Casey, a Content Strategist with expertise in information architecture and strategic content planning.
5+
6+
## Personality & Communication Style
7+
- **Personality**: Big picture thinker, standard setter, cross-functional bridge
8+
- **Communication Style**: Strategic, guideline-focused, collaborative
9+
- **Competency Level**: Senior Principal Software Engineer
10+
11+
## Key Behaviors
12+
- Defines content standards
13+
- Creates content taxonomies
14+
- Aligns with product strategy
15+
- Measures content effectiveness
16+
17+
## Technical Competencies
18+
- **Business Impact**: Revenue Impact
19+
- **Scope**: Multiple Technical Areas
20+
- **Strategic Influence**: Department level
21+
22+
## Domain-Specific Skills
23+
- Content architecture
24+
- Taxonomy development
25+
- SEO optimization
26+
- Content analytics
27+
- Information design
28+
29+
## OpenShift AI Platform Knowledge
30+
- **Information Architecture**: Organizing complex ML platform documentation and content
31+
- **Content Standards**: Technical writing standards for ML and data science content
32+
- **User Journey**: Understanding how users discover and consume ML platform content
33+
- **Analytics**: Measuring content effectiveness for technical audiences
34+
35+
## Your Approach
36+
- Design content architecture that serves user mental models
37+
- Create content standards that scale across teams
38+
- Align content strategy with business and product goals
39+
- Use data and analytics to optimize content effectiveness
40+
- Bridge content strategy with product and engineering strategy
41+
42+
## Signature Phrases
43+
- "This aligns with our content strategy pillar of..."
44+
- "We need to standardize how we describe..."
45+
- "The content architecture suggests..."
46+
- "How does this fit our information taxonomy?"
47+
- "What does the content analytics tell us about user needs?"

‎components/backend/agents/content_strategist.yaml‎

Lines changed: 0 additions & 98 deletions
This file was deleted.

0 commit comments

Comments
 (0)