specweave 0.1.9 → 0.3.0

package/src/skills/design-system-architect/test-cases/test-2-component-hierarchy.yaml

@@ -1,24 +0,0 @@
----
-name: "Component Hierarchy Validation"
-description: "Test validation of Atomic Design hierarchy"
-input:
-  components:
-    atoms:
-      - "Button"
-      - "Input"
-    molecules:
-      - "FormField"
-    organisms:
-      - "Navigation"
-expected_output:
-  type: "validation_result"
-  valid: true
-  hierarchy_correct: true
-validation:
-  - "Atoms are smallest components"
-  - "Molecules compose atoms"
-  - "Organisms compose molecules/atoms"
-success_criteria:
-  - "Hierarchy follows Atomic Design"
-  - "No circular dependencies"
----

package/src/skills/design-system-architect/test-cases/test-3-accessibility-checklist.yaml

@@ -1,23 +0,0 @@
----
-name: "Accessibility Checklist Validation"
-description: "Test validation of accessibility requirements"
-input:
-  component: "Button"
-  accessibility:
-    aria_label: true
-    keyboard_navigation: true
-    color_contrast: 4.6
-    touch_target: "44x44"
-expected_output:
-  type: "validation_result"
-  valid: true
-  wcag_compliant: true
-validation:
-  - "ARIA labels present"
-  - "Keyboard navigation supported"
-  - "Color contrast >= 4.5:1"
-  - "Touch targets >= 44x44px"
-success_criteria:
-  - "WCAG 2.1 AA compliance"
-  - "No accessibility violations"
----

package/src/skills/diagrams-architect/test-cases/test-1-c4-context.yaml

@@ -1,13 +0,0 @@
-name: "Create C4 Context Diagram"
-description: "Test creating a C4 Level 1 context diagram for a system"
-user_input: "Create a C4 context diagram for an e-commerce platform"
-expected_behavior:
-  - Generates valid Mermaid C4Context diagram
-  - Includes system boundary
-  - Shows external actors (users, external systems)
-  - Shows relationships and dependencies
-validation:
-  - Diagram starts with C4Context keyword
-  - Contains Person/System elements
-  - Includes Boundary definition
-  - Has BiRel or Rel relationship arrows

package/src/skills/diagrams-architect/test-cases/test-2-sequence-diagram.yaml

@@ -1,13 +0,0 @@
-name: "Create Sequence Diagram"
-description: "Test creating a sequence diagram for API authentication flow"
-user_input: "Create a sequence diagram for OAuth 2.0 authentication flow"
-expected_behavior:
-  - Generates valid Mermaid sequence diagram
-  - Shows participants (client, auth server, resource server)
-  - Includes authentication steps in correct order
-  - Shows token exchange flow
-validation:
-  - Diagram starts with sequenceDiagram keyword
-  - Contains participant declarations
-  - Has sequential messages (->>, -->)
-  - Includes notes for clarity

package/src/skills/diagrams-architect/test-cases/test-3-er-diagram.yaml

@@ -1,13 +0,0 @@
-name: "Create Entity Relationship Diagram"
-description: "Test creating an ER diagram for database schema"
-user_input: "Create an ER diagram for a multi-tenant SaaS database"
-expected_behavior:
-  - Generates valid Mermaid ER diagram
-  - Shows entities (tables)
-  - Shows relationships with cardinality
-  - Includes key attributes
-validation:
-  - Diagram starts with erDiagram keyword
-  - Contains entity definitions
-  - Has relationships (||--o{, etc.)
-  - Shows primary/foreign key fields

package/src/skills/diagrams-generator/test-cases/test-1.yaml

@@ -1,9 +0,0 @@
----
-name: "Detect Diagram Request"
-description: "Tests if diagrams-generator activates for diagram creation"
-input:
-  prompt: "Create C4 context diagram"
-expected_output:
-  skill_activated: true
-  agent_invoked: "diagrams-architect"
----

package/src/skills/diagrams-generator/test-cases/test-2.yaml

@@ -1,9 +0,0 @@
----
-name: "Detect C4 Level 3 (LLD)"
-description: "Tests if diagrams-generator correctly identifies LLD component diagrams"
-input:
-  prompt: "Create component diagram for Auth Service"
-expected_output:
-  diagram_type: "C4Component"
-  document_type: "LLD"
----

package/src/skills/diagrams-generator/test-cases/test-3.yaml

@@ -1,8 +0,0 @@
----
-name: "Save to Correct Location"
-description: "Tests if diagrams are saved to correct paths (HLD vs LLD)"
-input:
-  prompt: "Create component diagram for Payment Service"
-expected_output:
-  file_location: ".specweave/docs/internal/architecture/diagrams/payments/component-payment-service.mmd"
----

package/src/skills/docs-updater/test-cases/test-1-placeholder.yaml

@@ -1,12 +0,0 @@
----
-name: "Placeholder Test"
-description: "TODO: Add actual test case for this skill"
-input:
-  prompt: "Test prompt"
-expected_output:
-  type: "validation"
-validation:
-  - "Placeholder validation"
-success_criteria:
-  - "Test passes"
----

package/src/skills/docs-updater/test-cases/test-2-placeholder.yaml

@@ -1,12 +0,0 @@
----
-name: "Placeholder Test"
-description: "TODO: Add actual test case for this skill"
-input:
-  prompt: "Test prompt"
-expected_output:
-  type: "validation"
-validation:
-  - "Placeholder validation"
-success_criteria:
-  - "Test passes"
----

package/src/skills/docs-updater/test-cases/test-3-placeholder.yaml

@@ -1,12 +0,0 @@
----
-name: "Placeholder Test"
-description: "TODO: Add actual test case for this skill"
-input:
-  prompt: "Test prompt"
-expected_output:
-  type: "validation"
-validation:
-  - "Placeholder validation"
-success_criteria:
-  - "Test passes"
----

package/src/skills/dotnet-backend/test-cases/test-1-rest-api.yaml

@@ -1,14 +0,0 @@
-name: "Create ASP.NET Core REST API"
-description: "Test creating a REST API controller with Entity Framework"
-user_input: "Create a REST API for managing products with CRUD operations"
-expected_behavior:
-  - Generates ASP.NET Core controller with appropriate attributes
-  - Includes Entity Framework DbContext integration
-  - Implements CRUD endpoints (GET, POST, PUT, DELETE)
-  - Includes async/await pattern
-  - Adds proper HTTP status codes
-validation:
-  - Uses [ApiController] and [Route] attributes
-  - Controller inherits from ControllerBase
-  - Methods use async Task<ActionResult> pattern
-  - Includes dependency injection for DbContext

package/src/skills/dotnet-backend/test-cases/test-2-authentication.yaml

@@ -1,13 +0,0 @@
-name: "Implement JWT Authentication"
-description: "Test implementing JWT authentication in ASP.NET Core"
-user_input: "Add JWT token-based authentication to my API"
-expected_behavior:
-  - Configures JWT authentication in Program.cs/Startup.cs
-  - Creates login endpoint that generates JWT tokens
-  - Includes claims-based authorization
-  - Protects endpoints with [Authorize] attribute
-validation:
-  - Uses Microsoft.AspNetCore.Authentication.JwtBearer
-  - Configures token validation parameters
-  - Generates tokens with claims
-  - Implements token refresh logic

package/src/skills/dotnet-backend/test-cases/test-3-minimal-api.yaml

@@ -1,13 +0,0 @@
-name: "Create Minimal API"
-description: "Test creating .NET 6+ minimal API endpoints"
-user_input: "Create a minimal API for user management"
-expected_behavior:
-  - Uses app.MapGet/MapPost/MapPut/MapDelete
-  - Implements endpoints in Program.cs
-  - Includes route parameters and query strings
-  - Uses dependency injection
-validation:
-  - No controller classes needed
-  - Uses lambda expressions for endpoints
-  - Implements proper HTTP verbs
-  - Includes validation and error handling

package/src/skills/e2e-playwright/test-cases/TC-001-basic-navigation.yaml

@@ -1,54 +0,0 @@
-id: TC-001
-name: Basic Navigation Test
-description: Verify that the skill can navigate to a webpage and capture a screenshot
-priority: high
-category: functional
-
-preconditions:
-  - Playwright is installed
-  - Chromium browser is available
-  - Development server is running on localhost:3000
-
-test_steps:
-  - step: 1
-    action: Create test script that navigates to localhost:3000
-    expected: Test script is created in /tmp/
-
-  - step: 2
-    action: Execute test script via execute.js
-    expected: Browser launches and navigates to homepage
-
-  - step: 3
-    action: Capture full-page screenshot
-    expected: Screenshot is saved to /tmp/ with timestamp
-
-  - step: 4
-    action: Verify page title
-    expected: Page title is captured and logged to console
-
-  - step: 5
-    action: Close browser
-    expected: Browser closes cleanly without errors
-
-acceptance_criteria:
-  - Browser launches in visible mode (headless: false)
-  - Navigation completes successfully
-  - Screenshot file is created with correct naming pattern
-  - Console output shows execution steps
-  - No errors are thrown during execution
-
-test_data:
-  url: http://localhost:3000
-  expected_title: SpecWeave
-  screenshot_pattern: /tmp/homepage-*.png
-
-expected_results:
-  - Browser opens visibly
-  - Page loads within 10 seconds
-  - Screenshot file exists and is valid PNG
-  - Console shows "✅ Test passed" message
-  - Process exits with code 0
-
-notes: |
-  This is the most basic test case to verify core functionality.
-  All other tests depend on this working correctly.

package/src/skills/e2e-playwright/test-cases/TC-002-form-interaction.yaml

@@ -1,64 +0,0 @@
-id: TC-002
-name: Form Interaction Test
-description: Verify that the skill can interact with form elements using helper utilities
-priority: high
-category: functional
-
-preconditions:
-  - TC-001 passes
-  - Test page has a login form with email and password fields
-  - safeType and safeClick utilities are available
-
-test_steps:
-  - step: 1
-    action: Navigate to login page
-    expected: Login form is visible
-
-  - step: 2
-    action: Use safeType() to enter email address
-    expected: Email field is filled with test email
-
-  - step: 3
-    action: Use safeType() to enter password
-    expected: Password field is filled (masked)
-
-  - step: 4
-    action: Use safeClick() to submit form
-    expected: Form submission is triggered
-
-  - step: 5
-    action: Wait for navigation or success message
-    expected: User is redirected or sees success state
-
-  - step: 6
-    action: Capture screenshot of result
-    expected: Screenshot shows post-login state
-
-acceptance_criteria:
-  - safeType() handles focus and clearing automatically
-  - safeType() verifies text was entered correctly
-  - safeClick() waits for element to be visible
-  - Form submission completes without timeout
-  - Screenshots capture both pre and post submission states
-
-test_data:
-  email: test@example.com
-  password: testpassword123
-  login_url: http://localhost:3000/login
-  expected_redirect: /dashboard
-
-expected_results:
-  - Email field contains entered value
-  - Password field is masked
-  - Form submits successfully
-  - Navigation completes within 10 seconds
-  - Success state is reached
-
-error_scenarios:
-  - If email field not found: Error message with selector details
-  - If click times out: Retry up to 3 times
-  - If verification fails: Clear error about mismatch
-
-notes: |
-  Tests the core interaction utilities that make Playwright easier to use.
-  safeType() and safeClick() should handle common edge cases automatically.

package/src/skills/e2e-playwright/test-cases/TC-003-specweave-integration.yaml

@@ -1,74 +0,0 @@
-id: TC-003
-name: SpecWeave Integration Test
-description: Verify that the skill detects SpecWeave context and generates test reports in increment folders
-priority: medium
-category: integration
-
-preconditions:
-  - TC-001 and TC-002 pass
-  - Running in a SpecWeave project (.specweave/ directory exists)
-  - Active increment with in-progress status exists
-  - Increment has reports/ directory
-
-test_steps:
-  - step: 1
-    action: Execute test from within SpecWeave project
-    expected: Executor detects SpecWeave context
-
-  - step: 2
-    action: Check console output for SpecWeave detection message
-    expected: "🔷 SpecWeave project detected" is logged
-
-  - step: 3
-    action: Verify active increment detection
-    expected: "📦 Active increment: 0001-feature-name" is logged
-
-  - step: 4
-    action: Run test that generates results
-    expected: Test executes and collects results
-
-  - step: 5
-    action: Generate test report using generateTestReport()
-    expected: Markdown report is created
-
-  - step: 6
-    action: Save report using saveTestReport()
-    expected: Report is saved to .specweave/increments/{id}/reports/
-
-acceptance_criteria:
-  - detectSpecWeaveContext() correctly identifies SpecWeave projects
-  - Active increment is detected by checking tasks.md status
-  - Test reports follow SpecWeave format (see SKILL.md)
-  - Reports are saved to correct increment folder
-  - Report includes all sections (summary, results, performance, accessibility)
-
-test_data:
-  project_root: /path/to/specweave-project
-  increment_id: "0001-test-feature"
-  increment_status: in-progress
-  report_filename: e2e-test-report.md
-
-expected_results:
-  - isSpecweaveProject: true
-  - activeIncrement: "0001-test-feature"
-  - Report file exists at: .specweave/increments/0001-test-feature/reports/e2e-test-report.md
-  - Report contains proper Markdown formatting
-  - Report includes timestamp and test results
-
-report_sections_required:
-  - Test Summary (total, passed, failed, skipped)
-  - Test Results (individual test details)
-  - Performance Metrics (page load, interactions)
-  - Accessibility Issues (grouped by type)
-  - Recommendations (actionable items)
-
-edge_cases:
-  - No active increment: Should still work, just without increment context
-  - Multiple in-progress increments: Use the first one found
-  - reports/ directory missing: Create it automatically
-  - Running outside SpecWeave: Should work normally without SpecWeave features
-
-notes: |
-  This test verifies the SpecWeave-specific enhancements that differentiate
-  this skill from the original playwright-skill. The ability to automatically
-  detect context and generate reports in the right place is a key feature.

package/src/skills/e2e-playwright/test-cases/TC-004-accessibility-check.yaml

@@ -1,98 +0,0 @@
-id: TC-004
-name: Accessibility Check Test
-description: Verify that the skill can perform basic accessibility checks on web pages
-priority: medium
-category: accessibility
-
-preconditions:
-  - TC-001 passes
-  - Test page has various HTML elements (images, forms, buttons, links)
-  - checkAccessibility() utility is available
-
-test_steps:
-  - step: 1
-    action: Navigate to test page
-    expected: Page loads successfully
-
-  - step: 2
-    action: Call checkAccessibility(page)
-    expected: Function runs without errors
-
-  - step: 3
-    action: Verify detection of images without alt text
-    expected: Missing alt text issues are reported
-
-  - step: 4
-    action: Verify detection of form inputs without labels
-    expected: Missing label issues are reported
-
-  - step: 5
-    action: Verify detection of buttons without accessible text
-    expected: Missing button text issues are reported
-
-  - step: 6
-    action: Log all accessibility issues to console
-    expected: Clear, actionable issue descriptions are shown
-
-acceptance_criteria:
-  - All four accessibility checks run successfully
-  - Issues are grouped by type (missing-alt, missing-label, etc.)
-  - Each issue includes element HTML snippet
-  - Each issue includes clear message explaining the problem
-  - Function returns array of issue objects
-
-test_data:
-  test_scenarios:
-    - scenario: Image without alt
-      html: <img src="test.png">
-      expected_issue: missing-alt
-
-    - scenario: Input without label
-      html: <input type="text" name="test">
-      expected_issue: missing-label
-
-    - scenario: Button without text
-      html: <button></button>
-      expected_issue: missing-button-text
-
-    - scenario: Link without text
-      html: <a href="/test"></a>
-      expected_issue: missing-link-text
-
-expected_results:
-  - checkAccessibility() returns array
-  - Each issue has: type, element, message
-  - Element snippets are truncated to 100 chars
-  - Hidden inputs are ignored
-  - ARIA labels are recognized as valid alternatives
-
-issue_format:
-  type: string # e.g., "missing-alt"
-  element: string # HTML snippet (max 100 chars)
-  message: string # Human-readable description
-
-valid_alternatives:
-  for_images:
-    - alt attribute
-    - aria-label attribute
-
-  for_inputs:
-    - Wrapped in <label>
-    - Associated via <label for="id">
-    - aria-label attribute
-    - aria-labelledby attribute
-
-  for_buttons:
-    - Text content
-    - aria-label attribute
-    - Alt text on child image
-
-  for_links:
-    - Text content
-    - aria-label attribute
-    - Alt text on child image
-
-notes: |
-  Basic accessibility checks help catch common issues early.
-  This is not a replacement for full accessibility audits but provides
-  quick feedback during development.

package/src/skills/figma-designer/test-cases/test-1-design-system.yaml

@@ -1,13 +0,0 @@
-name: "Create Design System Foundation"
-description: "Test creating design tokens and base components in Figma"
-user_input: "Create a design system with color palette, typography, and spacing"
-expected_behavior:
-  - Defines color tokens (primary, secondary, neutral, semantic)
-  - Sets up typography scale (headings, body, captions)
-  - Creates spacing tokens (4px, 8px, 16px, etc.)
-  - Organizes tokens in Figma variables
-validation:
-  - Uses Figma variables for colors
-  - Defines text styles for typography
-  - Creates spacing components
-  - Follows naming conventions (color/primary/500)

package/src/skills/figma-designer/test-cases/test-2-component-library.yaml

@@ -1,13 +0,0 @@
-name: "Build Component Library"
-description: "Test creating reusable UI components using atomic design"
-user_input: "Create a button component library with all variants"
-expected_behavior:
-  - Creates button component with variants (primary, secondary, ghost)
-  - Implements states (default, hover, active, disabled)
-  - Uses auto-layout for responsive sizing
-  - Includes icon support
-validation:
-  - Component uses variants
-  - States implemented as component properties
-  - Uses auto-layout
-  - Properly linked to design tokens

package/src/skills/figma-designer/test-cases/test-3-responsive-layout.yaml

@@ -1,13 +0,0 @@
-name: "Design Responsive Layout"
-description: "Test creating responsive layouts with constraints"
-user_input: "Design a responsive dashboard layout for desktop and mobile"
-expected_behavior:
-  - Creates frames for different breakpoints (mobile, tablet, desktop)
-  - Uses auto-layout for flexible content
-  - Implements proper constraints
-  - Shows responsive behavior
-validation:
-  - Multiple frames for breakpoints
-  - Auto-layout on parent containers
-  - Constraints set appropriately
-  - Components adapt to different widths

package/src/skills/figma-implementer/test-cases/test-1-design-to-react.yaml

@@ -1,13 +0,0 @@
-name: "Convert Figma Design to React Component"
-description: "Test converting a Figma component to production React code"
-user_input: "Convert this Figma button component to React with TypeScript"
-expected_behavior:
-  - Extracts design tokens (colors, spacing, typography)
-  - Generates React component with proper props
-  - Implements all variants from Figma
-  - Includes Tailwind CSS or CSS modules
-validation:
-  - Component matches Figma design pixel-perfect
-  - Props match Figma variants
-  - Uses design tokens correctly
-  - Includes TypeScript interfaces

package/src/skills/figma-implementer/test-cases/test-2-storybook.yaml

@@ -1,13 +0,0 @@
-name: "Create Storybook Stories for Figma Components"
-description: "Test generating Storybook stories from Figma components"
-user_input: "Create Storybook stories for my button component from Figma"
-expected_behavior:
-  - Generates .stories.tsx file
-  - Creates stories for each variant
-  - Includes controls for interactive props
-  - Matches Figma design exactly
-validation:
-  - Stories show all variants
-  - Controls allow testing different states
-  - Visual regression tests possible
-  - Documentation includes usage examples

package/src/skills/figma-implementer/test-cases/test-3-design-tokens.yaml

@@ -1,13 +0,0 @@
-name: "Extract and Implement Design Tokens"
-description: "Test extracting design tokens from Figma and generating code"
-user_input: "Extract all design tokens from this Figma file"
-expected_behavior:
-  - Extracts colors, typography, spacing, shadows, borders
-  - Generates token files (JSON, CSS variables, or TypeScript)
-  - Creates Tailwind config if needed
-  - Maintains consistency with Figma
-validation:
-  - All token categories extracted
-  - Proper naming conventions
-  - Values match Figma exactly
-  - Tokens are importable and usable

package/src/skills/figma-mcp-connector/test-cases/test-1-read-file-desktop.yaml

@@ -1,22 +0,0 @@
----
-name: "Read Figma File - Official Desktop MCP"
-description: "Test reading Figma file via official desktop MCP"
-input:
-  figma_url: "https://figma.com/file/ABC123"
-  mcp_type: "official_desktop"
-  mcp_url: "http://127.0.0.1:3845/mcp"
-expected_output:
-  type: "figma_file_metadata"
-  fields:
-    - "fileId"
-    - "name"
-    - "components"
-    - "variables"
-validation:
-  - "File ID extracted correctly"
-  - "Components array populated"
-  - "Variables object exists"
-success_criteria:
-  - "File read successfully"
-  - "No authentication errors"
----

package/src/skills/figma-mcp-connector/test-cases/test-2-read-file-framelink.yaml

@@ -1,21 +0,0 @@
----
-name: "Read Figma File - Community Framelink MCP"
-description: "Test reading Figma file via community Framelink MCP"
-input:
-  figma_url: "https://figma.com/file/ABC123"
-  mcp_type: "community_framelink"
-expected_output:
-  type: "figma_file_metadata"
-  fields:
-    - "fileId"
-    - "name"
-    - "components"
-    - "variables"
-validation:
-  - "File ID extracted correctly"
-  - "Components array populated"
-  - "Framelink-specific optimizations applied"
-success_criteria:
-  - "File read successfully"
-  - "Context reduced for AI accuracy"
----

package/src/skills/figma-mcp-connector/test-cases/test-3-error-handling.yaml

@@ -1,18 +0,0 @@
----
-name: "Error Handling - Invalid Token"
-description: "Test error handling for invalid Figma token"
-input:
-  figma_url: "https://figma.com/file/ABC123"
-  token: "invalid_token"
-expected_output:
-  type: "error"
-  error_code: "AUTHENTICATION_FAILED"
-  message: "Invalid Figma access token"
-validation:
-  - "Error detected correctly"
-  - "Clear error message provided"
-  - "Suggests solution (check FIGMA_ACCESS_TOKEN)"
-success_criteria:
-  - "Error handled gracefully"
-  - "User guidance provided"
----