specweave 0.1.8 → 0.3.0

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"
----

package/src/skills/figma-to-code/test-cases/test-1-token-generation.yaml

@@ -1,29 +0,0 @@
----
-name: "Design Tokens Generation"
-description: "Test generation of design tokens from Figma variables"
-input:
-  figma_variables:
-    - name: "color/primary/500"
-      value: "#3b82f6"
-    - name: "spacing/4"
-      value: "4px"
-  framework: "react"
-expected_output:
-  type: "design_tokens"
-  css_variables:
-    - "--color-primary-500: #3b82f6;"
-    - "--spacing-4: 0.25rem;"
-  tailwind_config:
-    colors:
-      primary:
-        500: "#3b82f6"
-    spacing:
-      4: "0.25rem"
-validation:
-  - "CSS variables correctly formatted"
-  - "Tailwind config valid"
-  - "TypeScript types generated"
-success_criteria:
-  - "All tokens converted"
-  - "No syntax errors"
----

package/src/skills/figma-to-code/test-cases/test-2-component-generation.yaml

@@ -1,27 +0,0 @@
----
-name: "React Component Generation"
-description: "Test generation of React component from Figma component"
-input:
-  figma_component:
-    name: "Button"
-    variants:
-      - variant: "primary"
-        size: "md"
-    properties:
-      - name: "disabled"
-        type: "boolean"
-  framework: "react"
-expected_output:
-  type: "react_component"
-  files:
-    - "Button.tsx"
-    - "types.ts"
-  typescript_interface: true
-validation:
-  - "Component structure correct"
-  - "Props match Figma properties"
-  - "TypeScript types exported"
-success_criteria:
-  - "Component compiles"
-  - "No TypeScript errors"
----

package/src/skills/figma-to-code/test-cases/test-3-typescript-generation.yaml

@@ -1,28 +0,0 @@
----
-name: "TypeScript Interface Generation"
-description: "Test generation of TypeScript interfaces from Figma properties"
-input:
-  figma_component: "Button"
-  properties:
-    - name: "variant"
-      type: "enum"
-      values: ["primary", "secondary"]
-    - name: "size"
-      type: "enum"
-      values: ["sm", "md", "lg"]
-    - name: "disabled"
-      type: "boolean"
-expected_output:
-  type: "typescript_interfaces"
-  types:
-    - "type ButtonVariant = 'primary' | 'secondary';"
-    - "type ButtonSize = 'sm' | 'md' | 'lg';"
-    - "interface ButtonProps { variant?: ButtonVariant; size?: ButtonSize; disabled?: boolean; }"
-validation:
-  - "Types follow TypeScript conventions"
-  - "All properties mapped"
-  - "Exports correct"
-success_criteria:
-  - "TypeScript compiles"
-  - "No type errors"
----

package/src/skills/frontend/test-cases/test-1-react-component.yaml

@@ -1,13 +0,0 @@
-name: "Create React Component with Hooks"
-description: "Test creating a React component using hooks"
-user_input: "Create a user profile component with state management"
-expected_behavior:
-  - Generates functional component with TypeScript
-  - Uses useState for local state
-  - Uses useEffect for side effects
-  - Implements proper prop types
-validation:
-  - Uses React.FC or function component syntax
-  - Includes TypeScript interfaces for props
-  - Implements useState hook
-  - Includes proper cleanup in useEffect

package/src/skills/frontend/test-cases/test-2-form-validation.yaml

@@ -1,13 +0,0 @@
-name: "Implement Form with Validation"
-description: "Test creating a form with validation using React Hook Form"
-user_input: "Create a registration form with validation"
-expected_behavior:
-  - Uses react-hook-form for form management
-  - Implements Zod schema validation
-  - Includes error message display
-  - Handles form submission
-validation:
-  - Uses useForm hook
-  - Implements Zod schema with zodResolver
-  - Shows validation errors
-  - Includes submit handler

package/src/skills/frontend/test-cases/test-3-state-management.yaml

@@ -1,13 +0,0 @@
-name: "Implement Global State Management"
-description: "Test setting up Zustand for global state"
-user_input: "Add global state management for user authentication"
-expected_behavior:
-  - Creates Zustand store
-  - Implements actions and selectors
-  - Uses TypeScript for type safety
-  - Includes persistence if needed
-validation:
-  - Uses create from zustand
-  - Implements store interface
-  - Exports custom hooks
-  - Includes proper typing

package/src/skills/github-sync/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/github-sync/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/github-sync/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/hetzner-provisioner/test-cases/test-1-basic-provision.yaml

@@ -1,71 +0,0 @@
----
-name: "Basic Hetzner CX11 Provisioning"
-description: "Provision a basic CX11 instance with Docker for NextJS app deployment"
-skill: hetzner-provisioner
-priority: P1
-estimated_time: "5-10 minutes"
-
-input:
-  prompt: "Deploy my NextJS app on Hetzner as cheaply as possible"
-  requirements:
-    app_type: nextjs
-    instance_type: cx11
-    database: none
-    ssl: false
-    budget: "$10/month"
-
-expected_output:
-  terraform_files_generated:
-    - main.tf
-    - variables.tf
-    - outputs.tf
-    - cloud-init.yaml
-
-  terraform_resources:
-    - type: hcloud_server
-      name: app
-      server_type: cx11
-      image: ubuntu-22.04
-      location: nbg1
-
-    - type: hcloud_firewall
-      name: app
-      rules:
-        - port: 80
-        - port: 443
-        - port: 22
-
-  dockerfile_generated: true
-
-  github_actions_workflow: true
-
-  cost_estimate:
-    monthly: "$5.83"
-    breakdown:
-      - "CX11 instance: $5.83/month"
-      - "Storage (20GB): $0.50/month"
-    total: "$6.33/month"
-    within_budget: true
-
-  deployment_guide:
-    steps:
-      - "Set HETZNER_API_TOKEN in GitHub secrets"
-      - "Push code to GitHub"
-      - "GitHub Actions will deploy automatically"
-      - "Access app at http://[SERVER_IP]:3000"
-
-validation:
-  - "terraform validate passes without errors"
-  - "main.tf contains hcloud_server resource"
-  - "Dockerfile exists and is valid"
-  - "Cost estimate under $10/month"
-  - "GitHub Actions workflow file exists"
-
-expected_errors: []
-
-success_criteria:
-  - "All Terraform files generated"
-  - "Cost within budget"
-  - "Deployment guide provided"
-  - "No validation errors"
----

package/src/skills/hetzner-provisioner/test-cases/test-2-postgres-provision.yaml

@@ -1,85 +0,0 @@
----
-name: "Hetzner Provisioning with Managed Postgres"
-description: "Provision CX11 instance + managed Postgres database for full-stack app"
-skill: hetzner-provisioner
-priority: P1
-estimated_time: "10-15 minutes"
-
-input:
-  prompt: "Deploy my NextJS app on Hetzner with Postgres database"
-  requirements:
-    app_type: nextjs
-    instance_type: cx11
-    database: postgres
-    database_size: "2GB"
-    ssl: false
-    budget: "$15/month"
-
-expected_output:
-  terraform_files_generated:
-    - main.tf
-    - variables.tf
-    - outputs.tf
-    - cloud-init.yaml
-    - database.tf
-
-  terraform_resources:
-    - type: hcloud_server
-      name: app
-      server_type: cx11
-
-    - type: hcloud_database
-      name: postgres
-      engine: postgresql
-      version: "15"
-      size: db-1x-small
-
-    - type: hcloud_firewall
-      name: app
-
-  environment_variables:
-    - DATABASE_URL: "postgresql://user:pass@[DB_HOST]:5432/dbname"
-    - POSTGRES_HOST: "[DB_HOST from terraform output]"
-    - POSTGRES_PORT: "5432"
-    - POSTGRES_DB: "my_saas_db"
-
-  dockerfile_generated: true
-
-  docker_compose_generated: true
-  docker_compose_services:
-    - app
-    - (database managed separately by Hetzner)
-
-  cost_estimate:
-    monthly: "$10.83"
-    breakdown:
-      - "CX11 instance: $5.83/month"
-      - "Managed Postgres (2GB): $5.00/month"
-      - "Storage (20GB): $0.50/month"
-    total: "$11.33/month"
-    within_budget: true
-
-  deployment_guide:
-    steps:
-      - "Set HETZNER_API_TOKEN in GitHub secrets"
-      - "Set database credentials in environment variables"
-      - "Run terraform apply to provision infrastructure"
-      - "Database will be accessible at terraform output"
-      - "Configure app DATABASE_URL"
-      - "Deploy app with GitHub Actions"
-
-validation:
-  - "terraform validate passes"
-  - "hcloud_database resource exists in main.tf or database.tf"
-  - "Database connection string in outputs.tf"
-  - "Environment variables documented"
-  - "Cost under $15/month"
-
-expected_errors: []
-
-success_criteria:
-  - "Managed Postgres provisioned"
-  - "Connection string outputted"
-  - "Cost within budget"
-  - "App can connect to database"
----