/**
* Mock Data for Debug Tools
*
* Realistic test data for each MCP tool type to simulate real-world scenarios
* during UI development.
*/
export interface AskOneQuestionData {
question: string;
context?: any;
options?: string[];
}
export interface AskMultipleChoiceData {
questions: Array<{
text: string;
options: string[];
}>;
}
export interface ChallengeHypothesisData {
hypothesis: string;
context?: any;
evidence?: string[];
}
export interface ChooseNextData {
title: string;
description: string;
options: Array<{
id: string;
title: string;
description: string;
icon?: string;
}>;
}
/**
* Mock data for ask-one-question tool
*/
export const mockAskOneQuestionData: AskOneQuestionData = {
question: `# API Architecture Decision
We're designing the authentication system for our new microservices platform. The system needs to handle:
- **User Authentication**: Login/logout with email and social providers
- **Service-to-Service**: Secure communication between internal services
- **Third-party Integration**: API access for external partners
- **Mobile Apps**: Native iOS/Android authentication
## Key Requirements
- **Security**: Must support OAuth 2.0/OpenID Connect standards
- **Performance**: Sub-100ms token validation
- **Scalability**: Support for 100K+ concurrent users
- **Compliance**: SOC 2 and GDPR requirements
## Current Options Under Consideration
1. **Auth0/Okta** - Managed identity provider
2. **AWS Cognito** - Cloud-native solution
3. **Custom JWT** - In-house implementation
4. **Keycloak** - Open-source identity server
What's your recommendation and reasoning? Consider cost, complexity, vendor lock-in, and long-term maintainability.`,
context: {
project: "microservices-platform",
team: "backend-architecture",
deadline: "2024-02-15",
budget: "$50k-100k annually"
},
options: ["Auth0/Okta", "AWS Cognito", "Custom JWT", "Keycloak", "Other (specify)"]
};
/**
* Mock data for ask-multiple-choice tool
*/
export const mockAskMultipleChoiceData: AskMultipleChoiceData = {
questions: [
{
text: "Which features should be prioritized for the Q1 release?",
options: [
"Real-time collaboration editor",
"Advanced search with filters",
"Mobile app for iOS/Android",
"API rate limiting and quotas",
"Dashboard analytics and reporting",
"Single sign-on (SSO) integration",
"Dark mode theme support",
"Export to PDF/Excel formats"
]
},
{
text: "What deployment environments should be set up first?",
options: [
"Development environment",
"Staging/QA environment",
"Production environment",
"Load testing environment",
"Demo/Sales environment"
]
},
{
text: "Which testing strategies should we implement?",
options: [
"Unit tests with Jest/Vitest",
"Integration tests with Supertest",
"End-to-end tests with Playwright",
"Load testing with Artillery",
"Security testing with OWASP ZAP",
"Visual regression testing",
"API contract testing"
]
}
]
};
/**
* Mock data for challenge-hypothesis tool
*/
export const mockChallengeHypothesisData: ChallengeHypothesisData = {
hypothesis: "Moving from a monolithic architecture to microservices will improve our system's scalability, development velocity, and fault tolerance, making it worth the increased operational complexity.",
context: {
currentSystem: "Rails monolith serving 50K+ daily active users",
teamSize: "12 engineers across 3 teams",
growthRate: "20% monthly user growth",
challenges: ["Deploy bottlenecks", "Database scaling", "Feature conflicts"]
},
evidence: [
"Current deploy time is 45 minutes with frequent rollbacks",
"Database queries are hitting performance limits at peak traffic",
"Teams are frequently blocked by conflicting changes",
"Similar companies (Airbnb, Uber) successfully made this transition",
"Our infrastructure team has Kubernetes expertise",
"Recent outages affected entire system vs isolated features"
]
};
/**
* Mock data for choose-next tool
*/
export const mockChooseNextData: ChooseNextData = {
title: "Sprint Planning: Choose Next Development Focus",
description: `# Q4 Sprint Planning Decision
We have 4 weeks remaining in Q4 and need to choose our development focus. Each option has different strategic implications for our product roadmap and customer satisfaction.
## Current Context
- **Team Capacity**: 8 engineers, 2 designers, 1 PM
- **Customer Feedback**: 247 feature requests, 89 bug reports
- **Revenue Impact**: Q4 targets require strong feature adoption
- **Technical Debt**: Accumulated over 6 months, affecting velocity
## Decision Criteria
Your choice will determine our Q4 deliverables, customer satisfaction metrics, and Q1 2024 foundation. Consider both immediate impact and long-term strategic value.`,
options: [
{
id: "performance-optimization",
title: "Performance & Infrastructure Optimization",
description: "Focus on system performance, database optimization, caching, and infrastructure improvements. Address the 30% slowdown we've seen over the past quarter.",
icon: "⚡"
},
{
id: "user-experience-overhaul",
title: "User Experience & Design System",
description: "Redesign core user flows, implement design system, improve onboarding, and address the 23% drop in user engagement metrics.",
icon: "🎨"
},
{
id: "feature-expansion",
title: "New Feature Development",
description: "Build the top 3 requested features: advanced reporting, team collaboration tools, and API integrations. High customer demand.",
icon: "🚀"
},
{
id: "technical-debt-reduction",
title: "Technical Debt & Code Quality",
description: "Refactor legacy code, improve test coverage from 45% to 80%, update dependencies, and establish better development practices.",
icon: "🔧"
},
{
id: "security-compliance",
title: "Security & Compliance",
description: "Implement SOC 2 compliance, security audit findings, GDPR improvements, and penetration testing recommendations.",
icon: "🔒"
}
]
};
/**
* Mock human responses for each tool type
*/
export const mockResponses = {
askOneQuestion: {
answer: `I recommend **AWS Cognito** for the following reasons:
## Why AWS Cognito
1. **Perfect Fit for Requirements**
- Native OAuth 2.0/OpenID Connect support
- Built-in scalability (handles millions of users)
- SOC 2 and GDPR compliant out of the box
- Sub-50ms token validation with proper caching
2. **Cost Effectiveness**
- $25-40k annually at 100K users (vs $80-120k for Auth0)
- No surprise pricing as you scale
- Includes SMS/email delivery
3. **Integration Benefits**
- Seamless AWS ecosystem integration
- Works perfectly with API Gateway, Lambda
- Native mobile SDK support
- Easy CloudFormation deployment
## Implementation Strategy
Start with Cognito User Pools for user management, add Identity Pools for service-to-service auth. This gives us 80% of Auth0's features at 40% of the cost, with room to grow.
The main tradeoff is less UI customization, but our design team can work within those constraints.`,
timestamp: new Date().toISOString()
},
askMultipleChoice: {
responses: [
{
questionIndex: 0,
selections: [
{
text: "Real-time collaboration editor",
selected: true,
priority: "high",
comment: "This is our biggest differentiator and customer request"
},
{
text: "API rate limiting and quotas",
selected: true,
priority: "high",
comment: "Critical for platform stability as we scale"
},
{
text: "Dashboard analytics and reporting",
selected: true,
priority: "medium",
comment: "Important for customer retention and insights"
},
{
text: "Single sign-on (SSO) integration",
selected: true,
priority: "medium",
comment: "Enterprise customers are asking for this"
},
{
text: "Mobile app for iOS/Android",
selected: false,
priority: "low",
comment: "Resource intensive, can wait for Q2"
}
]
},
{
questionIndex: 1,
selections: [
{
text: "Staging/QA environment",
selected: true,
priority: "high",
comment: "Essential for quality releases"
},
{
text: "Production environment",
selected: true,
priority: "high",
comment: "Obviously needed for launch"
},
{
text: "Load testing environment",
selected: true,
priority: "medium",
comment: "Important for performance validation"
}
]
},
{
questionIndex: 2,
selections: [
{
text: "Unit tests with Jest/Vitest",
selected: true,
priority: "high",
comment: "Foundation of our testing strategy"
},
{
text: "End-to-end tests with Playwright",
selected: true,
priority: "high",
comment: "Critical user flow validation"
},
{
text: "API contract testing",
selected: true,
priority: "medium",
comment: "Important for microservices communication"
}
]
}
],
completionStatus: "done",
generalComment: "Focused on high-impact features that deliver immediate customer value while building a solid technical foundation. The collaboration editor and API rate limiting are non-negotiable for our Q1 goals."
},
challengeHypothesis: {
agreement: 5, // Somewhat agree (1-7 scale)
reasoning: `I **somewhat agree** with moving to microservices, but with important caveats:
## Strengths of the Hypothesis ✅
- **Deployment bottlenecks** are a real problem that microservices can solve
- **Team scaling** benefits are proven at our size (12 engineers)
- **Fault isolation** would prevent system-wide outages
- Our **Kubernetes expertise** reduces implementation risk
## Concerns & Risks ⚠️
- **Premature optimization**: 50K DAU isn't necessarily microservices scale
- **Operational complexity**: Distributed debugging, monitoring, networking
- **Data consistency**: Eventual consistency challenges across services
- **Performance overhead**: Network latency between services
## Alternative Recommendation 🎯
**Modular monolith first**: Extract problematic components (auth, notifications) as separate services while keeping core business logic together. This gives us 70% of the benefits with 30% of the complexity.
Then evaluate full microservices in 6 months when we hit 100K+ DAU.`,
confidence: 7, // High confidence (1-10 scale)
alternativeApproach: "Start with modular monolith architecture, extract high-contention services first",
additionalContext: "Consider team communication overhead (Conway's Law) and ensure service boundaries align with business domains"
},
chooseNext: {
action: "selected",
selectedOption: {
id: "performance-optimization",
title: "Performance & Infrastructure Optimization",
description: "Focus on system performance, database optimization, caching, and infrastructure improvements. Address the 30% slowdown we've seen over the past quarter.",
icon: "⚡"
},
message: `**Performance optimization is the clear priority** for Q4. Here's why:
## Critical Business Impact 🚨
- 30% slowdown directly impacts user satisfaction and churn
- Performance issues compound - they get worse under load
- Fast systems enable all other initiatives to succeed
## Strategic Foundation 🏗️
- Performance improvements benefit every future feature
- Infrastructure work scales with user growth
- Technical credibility with customers and team
## Q1 Enablement 🚀
- Optimized platform handles new feature load better
- Team velocity improves with faster development environment
- Customer satisfaction recovery enables feature adoption
## Execution Plan
1. **Week 1-2**: Database query optimization, indexing strategy
2. **Week 3**: Implement Redis caching layer
3. **Week 4**: CDN setup and asset optimization
This choice maximizes both immediate impact and long-term strategic value. The other options can build on this foundation in Q1.`
}
};
