@nextsparkjs/core 0.1.0-beta.8 → 0.1.0-beta.82

package/dist/presets/ai-workflow/claude/commands/bdd:write.md

@@ -1,300 +0,0 @@
----
-description: "[BDD] Generate BDD documentation (.bdd.md) from Cypress tests"
----
-
-# BDD Write - Generate BDD Documentation
-
-You are generating BDD test documentation from Cypress test files.
-
-**Target (session path or test file path):**
-{{{ input }}}
-
----
-
-## Your Mission
-
-Generate `.bdd.md` documentation files from Cypress tests following the BDD Viewer format:
-
-1. **Parse Cypress tests** to extract test cases and steps
-2. **Generate bilingual Gherkin** scenarios (EN + ES)
-3. **Create metadata** (frontmatter with tags, priority, coverage)
-4. **Document expected results** for each test case
-5. **Place .bdd.md files** alongside the source .cy.ts files
-
----
-
-## Protocol
-
-### Step 1: Determine Input Type
-
-```typescript
-// If input is a session path
-if (input.includes('.claude/sessions/')) {
-  // Read session context
-  await Read(`${input}/requirements.md`)
-  await Read(`${input}/tests.md`)
-
-  // Find all Cypress tests in session scope
-  const scope = JSON.parse(await Read(`${input}/scope.json`))
-  const themePath = `contents/themes/${scope.theme}/tests/cypress/e2e`
-
-  await Glob(`${themePath}/**/*.cy.ts`)
-}
-
-// If input is a specific file path
-else if (input.endsWith('.cy.ts')) {
-  await Read(input)
-}
-
-// If no input, scan default theme
-else {
-  await Glob('contents/themes/default/tests/cypress/e2e/**/*.cy.ts')
-}
-```
-
-### Step 2: Read BDD Format Reference
-
-```typescript
-// Read existing BDD examples to understand format
-await Glob('contents/themes/**/tests/cypress/e2e/**/*.bdd.md')
-
-// Read BDD parser to understand expected structure
-await Read('contents/themes/default/components/dev/bdd/parser.ts')
-await Read('contents/themes/default/components/dev/bdd/types.ts')
-```
-
-### Step 3: Parse Each Cypress Test File
-
-For each `.cy.ts` file found:
-
-```typescript
-// Read the test file
-const testContent = await Read(cypressFilePath)
-
-// Extract describe blocks -> features
-// Extract it() blocks -> test cases
-// Extract cy.* commands -> Gherkin steps
-// Extract assertions -> expected results
-```
-
-### Step 4: Generate BDD Document
-
-```typescript
-const bddPath = cypressFilePath.replace('.cy.ts', '.bdd.md')
-
-await Write({
-  file_path: bddPath,
-  content: generateBDDDocument(parsedTests)
-})
-```
-
----
-
-## BDD Document Format
-
-The generated `.bdd.md` file must follow this structure:
-
-```markdown
----
-feature: Feature Name
-priority: high | medium | low
-tags: [tag1, tag2, tag3]
-grepTags: [uat, feat-xxx, smoke, regression]
-coverage: N
----
-
-# Feature Name
-
-> Brief description of what this feature tests.
-
-## @test FEATURE-AREA-001: Test Title
-
-### Metadata
-- **Priority:** High | Medium | Low
-- **Type:** Smoke | Regression | Integration | E2E
-- **Tags:** tag1, tag2
-
-```gherkin:en
-Scenario: English scenario description
-
-Given some precondition
-And another precondition
-When user performs action
-And another action
-Then expected outcome
-And another expectation
-```
-
-```gherkin:es
-Scenario: Descripción del escenario en español
-
-Given alguna precondición
-And otra precondición
-When el usuario realiza una acción
-And otra acción
-Then resultado esperado
-And otra expectativa
-```
-
-### Expected Results
-- Expected result 1
-- Expected result 2
-- Expected result 3
-
----
-
-## @test FEATURE-AREA-002: Next Test Title
-... (repeat pattern)
-```
-
----
-
-## Cypress to Gherkin Mapping
-
-### Command Mappings
-
-| Cypress Command | Gherkin Step (EN) | Gherkin Step (ES) |
-|-----------------|-------------------|-------------------|
-| `cy.visit('/path')` | Given I am on the page | Given estoy en la página |
-| `cy.loginByUI()` | Given I am logged in as {role} | Given estoy logueado como {role} |
-| `cy.get('[data-cy="x"]').click()` | When I click the {element} | When hago clic en {element} |
-| `cy.get('[data-cy="x"]').type('text')` | When I enter "text" | When ingreso "text" |
-| `cy.get('[data-cy="x"]').should('be.visible')` | Then {element} should be visible | Then {element} debería ser visible |
-| `cy.get('[data-cy="x"]').should('contain', 'text')` | Then {element} should contain "text" | Then {element} debería contener "text" |
-| `cy.request('POST', ...)` | Given I have created {entity} via API | Given he creado {entity} via API |
-| `cy.intercept()` | Given the API response is intercepted | Given la respuesta API es interceptada |
-
-### Priority Mapping
-
-| Cypress Pattern | Priority |
-|-----------------|----------|
-| `describe('Happy Path', ...)` | high |
-| `describe('Smoke', ...)` | high |
-| `describe('Critical', ...)` | high |
-| `describe('Validation', ...)` | medium |
-| `describe('Edge Cases', ...)` | low |
-| `describe('Accessibility', ...)` | low |
-| Default | medium |
-
-### Type Mapping
-
-| Cypress Pattern | Type |
-|-----------------|------|
-| File path contains `api/` | integration |
-| File path contains `uat/` | e2e |
-| Test tags contain `@smoke` | smoke |
-| Test tags contain `@regression` | regression |
-| Default | e2e |
-
----
-
-## Test ID Generation
-
-Test IDs follow the pattern: `FEATURE-AREA-NNN`
-
-```typescript
-// Examples:
-// File: auth/login.cy.ts
-// -> AUTH-LOGIN-001, AUTH-LOGIN-002, ...
-
-// File: page-builder/admin/block-crud.cy.ts
-// -> PB-BLOCK-001, PB-BLOCK-002, ...
-
-// File: posts/public/posts-public.cy.ts
-// -> POSTS-PUBLIC-001, POSTS-PUBLIC-002, ...
-
-function generateTestId(filePath: string, index: number): string {
-  const parts = filePath
-    .replace(/.*\/e2e\//, '')
-    .replace('.cy.ts', '')
-    .split('/')
-
-  const feature = parts[0].toUpperCase().replace(/-/g, '')
-  const area = parts.length > 1
-    ? parts[parts.length - 1].toUpperCase().replace(/-/g, '').slice(0, 6)
-    : 'MAIN'
-
-  const num = String(index + 1).padStart(3, '0')
-
-  return `${feature}-${area}-${num}`
-}
-```
-
----
-
-## grepTags Extraction
-
-Extract grep tags from:
-
-1. **Test file comments:**
-   ```typescript
-   // @tags: uat, feat-auth, smoke
-   ```
-
-2. **Describe block strings:**
-   ```typescript
-   describe('@smoke @feat-auth Authentication', () => ...)
-   ```
-
-3. **it() block strings:**
-   ```typescript
-   it('@regression should handle edge case', () => ...)
-   ```
-
-4. **File path inference:**
-   - `e2e/api/` → `@api`
-   - `e2e/uat/` → `@uat`
-   - Feature name → `@feat-{feature}`
-
----
-
-## Output Format
-
-After generating BDD documents, report:
-
-```markdown
-## BDD Documentation Generated
-
-### Files Created
-| Source (.cy.ts) | Generated (.bdd.md) | Tests |
-|-----------------|---------------------|-------|
-| `path/to/file.cy.ts` | `path/to/file.bdd.md` | 5 |
-| ... | ... | ... |
-
-### Summary
-- **Total test files processed:** N
-- **Total BDD documents created:** N
-- **Total test cases documented:** N
-
-### Validation
-- [ ] All files have matching .bdd.md
-- [ ] All scenarios have EN + ES versions
-- [ ] All test IDs follow naming convention
-- [ ] All frontmatter is valid YAML
-
-### Next Steps
-1. View generated docs in Dev Area `/dev/tests`
-2. Review bilingual scenarios for accuracy
-3. Add any missing expected results
-```
-
----
-
-## Error Handling
-
-If parsing fails for a file:
-
-```markdown
-### Warnings
-
-| File | Issue | Action |
-|------|-------|--------|
-| `path/file.cy.ts` | Could not parse test structure | Manual review required |
-| `path/file.cy.ts` | Missing describe block | Skipped |
-```
-
-Continue processing other files even if some fail.
-
----
-
-**Now generate BDD documentation for the target specified above.**

package/dist/presets/ai-workflow/claude/commands/block:create.md

@@ -1,156 +0,0 @@
----
-description: "[Block] Create a new page builder block with complete file structure"
----
-
-# Create New Block
-
-You are creating a new block for the Page Builder system.
-
-**Block Requirements:**
-{{{ input }}}
-
----
-
-## Protocol
-
-### Step 1: Determine Theme
-
-Check if `--theme=X` was specified in the input above.
-
-- **If specified:** Use that theme
-- **If not specified:** Read `NEXT_PUBLIC_ACTIVE_THEME` from `.env` or `.env.local`
-- **If no variable:** Use `"default"`
-
-```bash
-# Check for theme variable
-grep "NEXT_PUBLIC_ACTIVE_THEME" .env .env.local 2>/dev/null
-```
-
-**ALWAYS confirm:** "Creating block in theme: {THEME}"
-
-### Step 2: Parse Requirements
-
-From the input above, extract:
-- **Block name** (required)
-- **Category** (if not specified, ask user)
-- **Fields/functionality** description
-
-If category is missing, ask:
-
-```typescript
-await AskUserQuestion({
-  questions: [{
-    header: "Category",
-    question: "What category should this block belong to?",
-    options: [
-      { label: "hero", description: "Full-width hero sections" },
-      { label: "content", description: "General content blocks" },
-      { label: "features", description: "Feature showcases" },
-      { label: "cta", description: "Call-to-action sections" },
-      { label: "testimonials", description: "Customer testimonials" },
-      { label: "pricing", description: "Pricing tables" },
-      { label: "faq", description: "FAQ/Accordion sections" },
-      { label: "forms", description: "Form blocks" },
-      { label: "other", description: "Other block types" }
-    ],
-    multiSelect: false
-  }]
-})
-```
-
-### Step 3: Launch block-developer Agent
-
-Launch the `block-developer` agent with full context:
-
-```
-Create a new block with:
-
-**Theme:** {determined theme}
-**Block Name:** {extracted name}
-**Slug:** {kebab-case name}
-**Category:** {extracted or asked category}
-**Description:** {from input}
-**Fields Needed:** {from input}
-
-**IMPORTANT:**
-1. First discover existing blocks in this theme to learn patterns
-2. Create all 5 required files (config, schema, fields, component, index)
-3. Extend baseBlockSchema - do NOT recreate base fields
-4. Organize fields in order: Content → Design → Advanced
-5. Include data-cy="block-{slug}" attribute
-6. Run build-registry after creation
-7. Verify block appears in BLOCK_REGISTRY
-```
-
-### Step 4: Verify Creation
-
-After agent completes:
-- Confirm all 5 files were created
-- Verify build-registry was executed
-- Check block appears in BLOCK_REGISTRY
-
----
-
-## Output Format
-
-```markdown
-## Block Created: {block-name}
-
-**Theme:** {theme}
-**Location:** `contents/themes/{theme}/blocks/{slug}/`
-
-### Files Created
-- [x] config.ts - Block metadata
-- [x] schema.ts - Zod validation schema
-- [x] fields.ts - DynamicForm field definitions
-- [x] component.tsx - React component
-- [x] index.ts - Re-exports
-
-### Block Configuration
-- **Slug:** {slug}
-- **Category:** {category}
-- **Icon:** {icon}
-
-### Fields
-**Content Tab:**
-- {list of content fields}
-
-**Design Tab:**
-- {list of design fields}
-
-**Advanced Tab:**
-- className, id (standard)
-
-### Registry
-- [x] `node core/scripts/build/registry.mjs` executed
-- [x] Block appears in BLOCK_REGISTRY
-
-### Next Steps
-1. Test block in page editor
-2. Create thumbnail image: `/theme/blocks/{slug}-thumbnail.png`
-3. Add E2E tests if needed
-```
-
----
-
-## Available Categories
-
-```
-hero, content, features, cta, testimonials, media, forms,
-navigation, footer, pricing, team, stats, faq, newsletter, other
-```
-
-## Available Field Types
-
-```
-text, textarea, url, email, number, select, checkbox, radio,
-rich-text, image, color, date, time, datetime, array
-```
-
-## Available Icons
-
-Use Lucide icon names: `Rocket`, `Grid`, `MessageSquare`, `DollarSign`, `Users`, `Star`, `HelpCircle`, `Mail`, `Image`, `Type`, `Layout`, etc.
-
----
-
-**Now create the block as specified above.**

package/dist/presets/ai-workflow/claude/commands/block:docs.md

@@ -1,251 +0,0 @@
----
-description: "[Block] Generate documentation for a page builder block"
----
-
-# Document Block
-
-You are generating documentation for a page builder block.
-
-**Documentation Request:**
-{{{ input }}}
-
----
-
-## Protocol
-
-### Step 1: Determine Theme
-
-Check if `--theme=X` was specified in the input above.
-
-- **If specified:** Use that theme
-- **If not specified:** Read `NEXT_PUBLIC_ACTIVE_THEME` from `.env` or `.env.local`
-- **If no variable:** Use `"default"`
-
-```bash
-grep "NEXT_PUBLIC_ACTIVE_THEME" .env .env.local 2>/dev/null
-```
-
-### Step 2: Identify Block
-
-Extract the block slug from the input.
-
-```bash
-# Verify block exists
-ls contents/themes/{THEME}/blocks/{slug}/
-```
-
-**If block not found, list available blocks.**
-
-### Step 3: Read Block Files
-
-Read all 5 files to extract complete information:
-
-```bash
-# Read all block files
-cat contents/themes/{THEME}/blocks/{slug}/config.ts
-cat contents/themes/{THEME}/blocks/{slug}/schema.ts
-cat contents/themes/{THEME}/blocks/{slug}/fields.ts
-cat contents/themes/{THEME}/blocks/{slug}/component.tsx
-cat contents/themes/{THEME}/blocks/{slug}/index.ts
-```
-
-### Step 4: Generate Documentation
-
-Create comprehensive documentation based on the block structure.
-
----
-
-## Output Format
-
-```markdown
-# {Block Name} Block
-
-> {Description from config.ts}
-
-## Overview
-
-| Property | Value |
-|----------|-------|
-| **Slug** | `{slug}` |
-| **Category** | {category} |
-| **Icon** | {icon} |
-| **Thumbnail** | {thumbnail path or "Not set"} |
-| **Location** | `contents/themes/{theme}/blocks/{slug}/` |
-
----
-
-## Props Reference
-
-### Base Props (Inherited)
-
-These props come from `baseBlockSchema` and are available in ALL blocks:
-
-| Prop | Type | Default | Description |
-|------|------|---------|-------------|
-| `title` | `string?` | `''` | Block title/heading |
-| `content` | `string?` | `''` | Main content text (rich text supported) |
-| `cta.text` | `string?` | `''` | Call-to-action button text |
-| `cta.link` | `string?` | `''` | CTA button URL |
-| `cta.target` | `'_self' \| '_blank'` | `'_self'` | Link target |
-| `backgroundColor` | `BackgroundColor` | `'transparent'` | Section background |
-| `className` | `string?` | `''` | Additional CSS classes |
-| `id` | `string?` | `''` | HTML id for anchors |
-
-### Block-Specific Props
-
-{Table of block-specific props from schema.ts}
-
-| Prop | Type | Required | Default | Description |
-|------|------|----------|---------|-------------|
-| `{name}` | `{type}` | {Yes/No} | `{default}` | {description} |
-
----
-
-## Editor Fields
-
-### Content Tab
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| Title | text | No | Block heading |
-| Content | rich-text | No | Main content area |
-| CTA Text | text | No | Button text |
-| CTA Link | url | No | Button URL |
-| {block-specific content fields} |
-
-### Design Tab
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| Background Color | select | No | Section background color |
-| {block-specific design fields} |
-
-### Advanced Tab
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| CSS Class | text | No | Additional CSS classes |
-| HTML ID | text | No | Element ID for anchor links |
-
----
-
-## Usage Example
-
-### In Page Editor
-
-1. Open the Page Editor
-2. Click "Add Block" in the block picker
-3. Select "{Block Name}" from the {category} category
-4. Configure fields in the settings panel
-5. Save the page
-
-### JSON Structure (BlockInstance)
-
-```json
-{
-  "id": "uuid-here",
-  "blockSlug": "{slug}",
-  "props": {
-    "title": "Example Title",
-    "content": "Example content text",
-    "cta.text": "Learn More",
-    "cta.link": "/about",
-    "backgroundColor": "primary",
-    {block-specific example props}
-  }
-}
-```
-
-### Rendered HTML Structure
-
-```html
-<section
-  id="optional-id"
-  class="py-16 px-4 bg-primary text-primary-foreground optional-class"
-  data-cy="block-{slug}"
->
-  <h2 class="...">Title</h2>
-  <div class="prose">Content</div>
-  {block-specific structure}
-</section>
-```
-
----
-
-## Component Code
-
-### File: `component.tsx`
-
-```typescript
-{Show simplified component structure highlighting key patterns}
-```
-
-### Key Patterns Used
-
-- ✅ Uses `buildSectionClasses` for consistent styling
-- ✅ Has `data-cy="block-{slug}"` for testing
-- ✅ Handles optional props safely
-- ✅ Supports responsive design
-- {Any other notable patterns}
-
----
-
-## Styling
-
-### Background Color Options
-
-| Value | CSS Classes |
-|-------|-------------|
-| `transparent` | (no background) |
-| `white` | `bg-white` |
-| `gray-50` | `bg-gray-50` |
-| `gray-100` | `bg-gray-100` |
-| `gray-900` | `bg-gray-900 text-white` |
-| `primary` | `bg-primary text-primary-foreground` |
-| `primary-light` | `bg-primary/10` |
-| `primary-dark` | `bg-primary-dark text-white` |
-| `secondary` | `bg-secondary text-secondary-foreground` |
-| `accent` | `bg-accent text-accent-foreground` |
-
-### Custom Styling
-
-Add custom CSS classes via the "CSS Class" field in the Advanced tab.
-
-```html
-<!-- Example with custom class -->
-<section class="py-16 px-4 bg-primary my-custom-class">
-```
-
----
-
-## Testing
-
-### Cypress Selector
-
-```typescript
-cy.get('[data-cy="block-{slug}"]')
-```
-
-### Test Cases to Consider
-
-1. Block renders with minimal props
-2. Block renders with all props filled
-3. CTA button works when provided
-4. Background colors apply correctly
-5. Custom className is applied
-6. HTML id is applied for anchor links
-
----
-
-## Related
-
-- **Schema:** `contents/themes/{theme}/blocks/{slug}/schema.ts`
-- **Fields:** `contents/themes/{theme}/blocks/{slug}/fields.ts`
-- **Component:** `contents/themes/{theme}/blocks/{slug}/component.tsx`
-- **Similar Blocks:** {list similar blocks in same category}
-- **Documentation:** `core/docs/18-page-builder/`
-```
-
----
-
-**Now generate documentation for the block specified above.**