bmad-elsabro 1.0.0

package/renderer/context/ThemeContext.tsx

@@ -0,0 +1,97 @@
+/**
+ * ThemeContext
+ *
+ * React context for managing application theme across all components.
+ * Provides theme state and toggle functionality through context API.
+ *
+ * Features:
+ * - Global theme state management
+ * - Theme persistence via useTheme hook
+ * - Type-safe context with TypeScript
+ * - Easy access via useThemeContext hook
+ */
+
+import React, { createContext, useContext, ReactNode } from 'react';
+import { useTheme, Theme } from '../hooks/useTheme';
+
+export interface ThemeContextValue {
+  /**
+   * Current theme value
+   */
+  theme: Theme;
+
+  /**
+   * Toggle between light and dark theme
+   */
+  toggleTheme: () => void;
+
+  /**
+   * Set a specific theme
+   */
+  setTheme: (theme: Theme) => void;
+}
+
+const ThemeContext = createContext<ThemeContextValue | undefined>(undefined);
+
+export interface ThemeProviderProps {
+  /**
+   * Child components that will have access to theme context
+   */
+  children: ReactNode;
+}
+
+/**
+ * ThemeProvider Component
+ *
+ * Wraps the application to provide theme context to all child components.
+ * Must be placed at the root of your component tree.
+ *
+ * @example
+ * ```tsx
+ * <ThemeProvider>
+ *   <App />
+ * </ThemeProvider>
+ * ```
+ */
+export const ThemeProvider: React.FC<ThemeProviderProps> = ({ children }) => {
+  const themeValue = useTheme();
+
+  return (
+    <ThemeContext.Provider value={themeValue}>
+      {children}
+    </ThemeContext.Provider>
+  );
+};
+
+ThemeProvider.displayName = 'ThemeProvider';
+
+/**
+ * useThemeContext Hook
+ *
+ * Access the theme context in any component.
+ * Must be used within a ThemeProvider.
+ *
+ * @throws {Error} If used outside of ThemeProvider
+ *
+ * @example
+ * ```tsx
+ * const { theme, toggleTheme } = useThemeContext();
+ *
+ * return (
+ *   <button onClick={toggleTheme}>
+ *     Switch to {theme === 'dark' ? 'light' : 'dark'} mode
+ *   </button>
+ * );
+ * ```
+ */
+export const useThemeContext = (): ThemeContextValue => {
+  const context = useContext(ThemeContext);
+
+  if (context === undefined) {
+    throw new Error('useThemeContext must be used within a ThemeProvider');
+  }
+
+  return context;
+};
+
+export default ThemeProvider;

package/renderer/data/shortcuts.json

@@ -0,0 +1,94 @@
+{
+  "shortcuts": [
+    {
+      "id": "command-palette",
+      "name": "Command Palette",
+      "description": "Open the command palette to quickly access actions",
+      "key": "ctrl+k",
+      "keyMac": "cmd+k",
+      "category": "General",
+      "enabled": true
+    },
+    {
+      "id": "toggle-sidebar",
+      "name": "Toggle Sidebar",
+      "description": "Show or hide the navigation sidebar",
+      "key": "ctrl+b",
+      "keyMac": "cmd+b",
+      "category": "Navigation",
+      "enabled": true
+    },
+    {
+      "id": "toggle-terminal",
+      "name": "Toggle Terminal",
+      "description": "Show or hide the integrated terminal",
+      "key": "ctrl+`",
+      "keyMac": "cmd+`",
+      "category": "Navigation",
+      "enabled": true
+    },
+    {
+      "id": "new-workflow",
+      "name": "New Workflow",
+      "description": "Create a new workflow",
+      "key": "ctrl+n",
+      "keyMac": "cmd+n",
+      "category": "Workflows",
+      "enabled": true
+    },
+    {
+      "id": "save-workflow",
+      "name": "Save Workflow",
+      "description": "Save the current workflow",
+      "key": "ctrl+s",
+      "keyMac": "cmd+s",
+      "category": "Workflows",
+      "enabled": true
+    },
+    {
+      "id": "open-settings",
+      "name": "Open Settings",
+      "description": "Open the settings panel",
+      "key": "ctrl+,",
+      "keyMac": "cmd+,",
+      "category": "General",
+      "enabled": true
+    },
+    {
+      "id": "toggle-theme",
+      "name": "Toggle Theme",
+      "description": "Switch between light and dark theme",
+      "key": "ctrl+shift+t",
+      "keyMac": "cmd+shift+t",
+      "category": "Appearance",
+      "enabled": true
+    },
+    {
+      "id": "search-files",
+      "name": "Search Files",
+      "description": "Search for files in the current project",
+      "key": "ctrl+p",
+      "keyMac": "cmd+p",
+      "category": "Navigation",
+      "enabled": true
+    },
+    {
+      "id": "focus-chat",
+      "name": "Focus Chat",
+      "description": "Move focus to the chat input",
+      "key": "ctrl+shift+c",
+      "keyMac": "cmd+shift+c",
+      "category": "Navigation",
+      "enabled": true
+    },
+    {
+      "id": "close-panel",
+      "name": "Close Panel",
+      "description": "Close the current panel or modal",
+      "key": "escape",
+      "keyMac": "escape",
+      "category": "General",
+      "enabled": true
+    }
+  ]
+}

package/renderer/data/testing-guides.json

@@ -0,0 +1,261 @@
+{
+  "guides": [
+    {
+      "id": "what-is-testing",
+      "topic": "What is Testing?",
+      "shortDescription": "Learn the basics of software testing",
+      "explanation": "Testing is like checking your homework before you turn it in! Just like you check your math problems to make sure you got the right answer, we test our code to make sure it works correctly.",
+      "examples": [
+        "If you build a calculator app, testing checks that 2 + 2 really equals 4",
+        "If you make a login form, testing makes sure users can actually log in",
+        "If you create a game, testing verifies the score updates correctly"
+      ],
+      "category": "basics",
+      "relatedTopics": ["test-scenarios", "assertions"]
+    },
+    {
+      "id": "test-scenarios",
+      "topic": "Test Scenarios",
+      "shortDescription": "Different situations to test your code",
+      "explanation": "Test scenarios are like different stories of how someone might use your code. Imagine you're testing a vending machine - you'd want to try normal situations, weird situations, and broken situations!",
+      "examples": [
+        {
+          "type": "Happy Path",
+          "emoji": "✅",
+          "description": "Everything works perfectly - like putting in exact change and getting your snack",
+          "example": "User enters valid email and password, successfully logs in"
+        },
+        {
+          "type": "Edge Case",
+          "emoji": "⚠️",
+          "description": "Unusual but valid situations - like using a $100 bill for a $1 candy",
+          "example": "User enters extremely long (but valid) email address"
+        },
+        {
+          "type": "Error Handling",
+          "emoji": "❌",
+          "description": "When things go wrong - like the vending machine being empty",
+          "example": "User enters wrong password, sees helpful error message"
+        }
+      ],
+      "category": "concepts",
+      "relatedTopics": ["assertions", "test-types"]
+    },
+    {
+      "id": "assertions",
+      "topic": "Assertions",
+      "shortDescription": "Checking if results match expectations",
+      "explanation": "Assertions are like rules that say 'this MUST be true'. Think of it like a teacher's answer key - if your answer doesn't match the key, you got it wrong! Assertions check if your code's answers match what they should be.",
+      "examples": [
+        {
+          "type": "Equals",
+          "description": "Check if two things are exactly the same",
+          "example": "2 + 2 should equal 4 (not 3, not 5, exactly 4!)"
+        },
+        {
+          "type": "Contains",
+          "description": "Check if something includes a specific thing",
+          "example": "Your shopping list should contain 'milk'"
+        },
+        {
+          "type": "Throws Error",
+          "description": "Check that code properly shows an error when something's wrong",
+          "example": "Dividing by zero should show an error message"
+        },
+        {
+          "type": "Truthy/Falsy",
+          "description": "Check if something is true or false",
+          "example": "User logged in should be true"
+        }
+      ],
+      "category": "concepts",
+      "relatedTopics": ["test-scenarios"]
+    },
+    {
+      "id": "test-types",
+      "topic": "Types of Tests",
+      "shortDescription": "Different kinds of code you can test",
+      "explanation": "Just like you can test different subjects in school (math, spelling, science), you can test different types of code! Each type needs slightly different testing approaches.",
+      "examples": [
+        {
+          "type": "Function Test",
+          "icon": "🔧",
+          "description": "Testing a single tool that does one job",
+          "example": "Test a 'calculateTax()' function to make sure it adds the right tax amount"
+        },
+        {
+          "type": "Class Test",
+          "icon": "📦",
+          "description": "Testing a container with multiple tools inside",
+          "example": "Test a 'ShoppingCart' class that can add items, remove items, and calculate total"
+        },
+        {
+          "type": "Component Test",
+          "icon": "🎨",
+          "description": "Testing a visual piece of your app",
+          "example": "Test a 'LoginButton' to make sure it looks right and works when clicked"
+        },
+        {
+          "type": "Workflow Test",
+          "icon": "🔄",
+          "description": "Testing a series of steps that work together",
+          "example": "Test the complete process: search for product → add to cart → checkout → confirm order"
+        }
+      ],
+      "category": "concepts",
+      "relatedTopics": ["test-frameworks"]
+    },
+    {
+      "id": "test-frameworks",
+      "topic": "Test Frameworks",
+      "shortDescription": "Tools that help you write and run tests",
+      "explanation": "Test frameworks are like different board games - they all let you have fun, but each has different rules! Each framework helps you test your code, but with slightly different features.",
+      "examples": [
+        {
+          "framework": "Jest",
+          "emoji": "🃏",
+          "description": "The most popular choice - like Monopoly, everyone knows it!",
+          "bestFor": "React apps, beginners, projects that need lots of features built-in",
+          "recommendation": "Start here if you're new to testing!"
+        },
+        {
+          "framework": "Mocha",
+          "emoji": "☕",
+          "description": "Very flexible - like LEGO, you can build exactly what you want",
+          "bestFor": "Node.js projects, teams that want to choose their own tools",
+          "recommendation": "Good if you like customization"
+        },
+        {
+          "framework": "Vitest",
+          "emoji": "⚡",
+          "description": "Super fast and modern - like an electric car vs. a regular car",
+          "bestFor": "Vite projects, developers who want speed",
+          "recommendation": "Great for new projects using Vite"
+        }
+      ],
+      "category": "tools",
+      "relatedTopics": ["test-types"]
+    },
+    {
+      "id": "code-coverage",
+      "topic": "Code Coverage",
+      "shortDescription": "How much of your code is tested",
+      "explanation": "Code coverage is like coloring a picture - it shows which parts you've colored (tested) and which parts are still blank (not tested). If you have 80% coverage, that means 80% of your code has tests checking it!",
+      "examples": [
+        "If your app has 10 functions and you test 8 of them, you have 80% coverage",
+        "Lines of code that turn green when you run tests are covered",
+        "Lines that stay red or gray haven't been tested yet"
+      ],
+      "visualization": {
+        "good": "🟢 Green = Tested ✅",
+        "bad": "🔴 Red = Not tested ⚠️",
+        "target": "🎯 Aim for at least 80% coverage"
+      },
+      "category": "metrics",
+      "relatedTopics": ["what-is-testing"]
+    },
+    {
+      "id": "mocking",
+      "topic": "Mocking",
+      "shortDescription": "Pretending something exists for testing",
+      "explanation": "Mocking is like using a toy phone instead of a real phone when you're pretending to call someone. When testing, we use 'fake' versions of things (like databases or APIs) so we can test our code without needing the real thing!",
+      "examples": [
+        "Instead of calling a real bank's API, use a fake one that always says 'balance: $100'",
+        "Instead of sending real emails, pretend to send them and just check that the code tried to",
+        "Instead of waiting for a slow database, use a fake instant one"
+      ],
+      "benefits": [
+        "Tests run faster (no waiting for real servers)",
+        "Tests are more reliable (fake things always work the same way)",
+        "You can test error cases (make the fake thing 'break' on purpose)"
+      ],
+      "category": "advanced",
+      "relatedTopics": ["assertions"]
+    },
+    {
+      "id": "tdd",
+      "topic": "Test-Driven Development (TDD)",
+      "shortDescription": "Writing tests before writing code",
+      "explanation": "TDD is like planning your route before taking a trip. Instead of just starting to drive and hoping you get there, you first decide where you want to go, THEN start driving. With TDD, you write the test (decide where you're going) before writing the code (taking the trip)!",
+      "steps": [
+        {
+          "step": 1,
+          "emoji": "🔴",
+          "name": "Red",
+          "description": "Write a test that fails (because the code doesn't exist yet)"
+        },
+        {
+          "step": 2,
+          "emoji": "🟢",
+          "name": "Green",
+          "description": "Write just enough code to make the test pass"
+        },
+        {
+          "step": 3,
+          "emoji": "✨",
+          "name": "Refactor",
+          "description": "Make the code better (cleaner, faster) while keeping tests passing"
+        }
+      ],
+      "category": "advanced",
+      "relatedTopics": ["what-is-testing"]
+    },
+    {
+      "id": "integration-vs-unit",
+      "topic": "Unit vs Integration Tests",
+      "shortDescription": "Testing parts vs. testing the whole",
+      "explanation": "Unit tests check one small piece (like testing a single LEGO brick), while integration tests check how pieces work together (like testing if the LEGO bricks connect properly to build a house).",
+      "comparison": [
+        {
+          "aspect": "What they test",
+          "unit": "One function or component alone",
+          "integration": "Multiple parts working together"
+        },
+        {
+          "aspect": "Speed",
+          "unit": "Very fast ⚡",
+          "integration": "Slower 🐢"
+        },
+        {
+          "aspect": "Example",
+          "unit": "Test that calculateTax() returns correct tax for $100",
+          "integration": "Test that cart total includes product price + tax + shipping"
+        }
+      ],
+      "analogy": "Unit test = testing if your bike pedals turn. Integration test = testing if pedaling makes the whole bike move forward.",
+      "category": "concepts",
+      "relatedTopics": ["what-is-testing", "test-types"]
+    },
+    {
+      "id": "debugging-tests",
+      "topic": "Debugging Failed Tests",
+      "shortDescription": "What to do when tests don't pass",
+      "explanation": "When a test fails, it's like getting an answer wrong on a quiz - the test is telling you something's not right! Don't panic, it's actually helpful because it shows you exactly what to fix.",
+      "steps": [
+        {
+          "step": "1. Read the error message",
+          "tip": "It usually tells you what went wrong, like 'Expected 5 but got 4'"
+        },
+        {
+          "step": "2. Look at what was expected vs. what actually happened",
+          "tip": "The test wanted one thing, but your code did something else"
+        },
+        {
+          "step": "3. Check your code logic",
+          "tip": "Is there a math mistake? A typo? A missing step?"
+        },
+        {
+          "step": "4. Fix the code (or sometimes, fix the test!)",
+          "tip": "Sometimes the test itself is wrong, not your code"
+        }
+      ],
+      "commonMistakes": [
+        "Comparing numbers to strings ('5' is not the same as 5)",
+        "Forgetting to wait for async operations to complete",
+        "Using real data that changes instead of test data"
+      ],
+      "category": "troubleshooting",
+      "relatedTopics": ["assertions"]
+    }
+  ]
+}