heraspec 0.1.0

package/dist/core/templates/skills/data/ux-guidelines.csv

@@ -0,0 +1,100 @@
+No,Category,Issue,Platform,Description,Do,Don't,Code Example Good,Code Example Bad,Severity
+1,Navigation,Smooth Scroll,Web,Anchor links should scroll smoothly to target section,Use scroll-behavior: smooth on html element,Jump directly without transition,html { scroll-behavior: smooth; },<a href='#section'> without CSS,High
+2,Navigation,Sticky Navigation,Web,Fixed nav should not obscure content,Add padding-top to body equal to nav height,Let nav overlap first section content,pt-20 (if nav is h-20),No padding compensation,Medium
+3,Navigation,Active State,All,Current page/section should be visually indicated,Highlight active nav item with color/underline,No visual feedback on current location,text-primary border-b-2,All links same style,Medium
+4,Navigation,Back Button,Mobile,Users expect back to work predictably,Preserve navigation history properly,Break browser/app back button behavior,history.pushState(),location.replace(),High
+5,Navigation,Deep Linking,All,URLs should reflect current state for sharing,Update URL on state/view changes,Static URLs for dynamic content,Use query params or hash,Single URL for all states,Medium
+6,Navigation,Breadcrumbs,Web,Show user location in site hierarchy,Use for sites with 3+ levels of depth,Use for flat single-level sites,Home > Category > Product,Only on deep nested pages,Low
+7,Animation,Excessive Motion,All,Too many animations cause distraction and motion sickness,Animate 1-2 key elements per view maximum,Animate everything that moves,Single hero animation,animate-bounce on 5+ elements,High
+8,Animation,Duration Timing,All,Animations should feel responsive not sluggish,Use 150-300ms for micro-interactions,Use animations longer than 500ms for UI,transition-all duration-200,duration-1000,Medium
+9,Animation,Reduced Motion,All,Respect user's motion preferences,Check prefers-reduced-motion media query,Ignore accessibility motion settings,@media (prefers-reduced-motion: reduce),No motion query check,High
+10,Animation,Loading States,All,Show feedback during async operations,Use skeleton screens or spinners,Leave UI frozen with no feedback,animate-pulse skeleton,Blank screen while loading,High
+11,Animation,Hover vs Tap,All,Hover effects don't work on touch devices,Use click/tap for primary interactions,Rely only on hover for important actions,onClick handler,onMouseEnter only,High
+12,Animation,Continuous Animation,All,Infinite animations are distracting,Use for loading indicators only,Use for decorative elements,animate-spin on loader,animate-bounce on icons,Medium
+13,Animation,Transform Performance,Web,Some CSS properties trigger expensive repaints,Use transform and opacity for animations,Animate width/height/top/left properties,transform: translateY(),top: 10px animation,Medium
+14,Animation,Easing Functions,All,Linear motion feels robotic,Use ease-out for entering ease-in for exiting,Use linear for UI transitions,ease-out,linear,Low
+15,Layout,Z-Index Management,Web,Stacking context conflicts cause hidden elements,Define z-index scale system (10 20 30 50),Use arbitrary large z-index values,z-10 z-20 z-50,z-[9999],High
+16,Layout,Overflow Hidden,Web,Hidden overflow can clip important content,Test all content fits within containers,Blindly apply overflow-hidden,overflow-auto with scroll,overflow-hidden truncating content,Medium
+17,Layout,Fixed Positioning,Web,Fixed elements can overlap or be inaccessible,Account for safe areas and other fixed elements,Stack multiple fixed elements carelessly,Fixed nav + fixed bottom with gap,Multiple overlapping fixed elements,Medium
+18,Layout,Stacking Context,Web,New stacking contexts reset z-index,Understand what creates new stacking context,Expect z-index to work across contexts,Parent with z-index isolates children,z-index: 9999 not working,Medium
+19,Layout,Content Jumping,Web,Layout shift when content loads is jarring,Reserve space for async content,Let images/content push layout around,aspect-ratio or fixed height,No dimensions on images,High
+20,Layout,Viewport Units,Web,100vh can be problematic on mobile browsers,Use dvh or account for mobile browser chrome,Use 100vh for full-screen mobile layouts,min-h-dvh or min-h-screen,h-screen on mobile,Medium
+21,Layout,Container Width,Web,Content too wide is hard to read,Limit max-width for text content (65-75ch),Let text span full viewport width,max-w-prose or max-w-3xl,Full width paragraphs,Medium
+22,Touch,Touch Target Size,Mobile,Small buttons are hard to tap accurately,Minimum 44x44px touch targets,Tiny clickable areas,min-h-[44px] min-w-[44px],w-6 h-6 buttons,High
+23,Touch,Touch Spacing,Mobile,Adjacent touch targets need adequate spacing,Minimum 8px gap between touch targets,Tightly packed clickable elements,gap-2 between buttons,gap-0 or gap-1,Medium
+24,Touch,Gesture Conflicts,Mobile,Custom gestures can conflict with system,Avoid horizontal swipe on main content,Override system gestures,Vertical scroll primary,Horizontal swipe carousel only,Medium
+25,Touch,Tap Delay,Mobile,300ms tap delay feels laggy,Use touch-action CSS or fastclick,Default mobile tap handling,touch-action: manipulation,No touch optimization,Medium
+26,Touch,Pull to Refresh,Mobile,Accidental refresh is frustrating,Disable where not needed,Enable by default everywhere,overscroll-behavior: contain,Default overscroll,Low
+27,Touch,Haptic Feedback,Mobile,Tactile feedback improves interaction feel,Use for confirmations and important actions,Overuse vibration feedback,navigator.vibrate(10),Vibrate on every tap,Low
+28,Interaction,Focus States,All,Keyboard users need visible focus indicators,Use visible focus rings on interactive elements,Remove focus outline without replacement,focus:ring-2 focus:ring-blue-500,outline-none without alternative,High
+29,Interaction,Hover States,Web,Visual feedback on interactive elements,Change cursor and add subtle visual change,No hover feedback on clickable elements,hover:bg-gray-100 cursor-pointer,No hover style,Medium
+30,Interaction,Active States,All,Show immediate feedback on press/click,Add pressed/active state visual change,No feedback during interaction,active:scale-95,No active state,Medium
+31,Interaction,Disabled States,All,Clearly indicate non-interactive elements,Reduce opacity and change cursor,Confuse disabled with normal state,opacity-50 cursor-not-allowed,Same style as enabled,Medium
+32,Interaction,Loading Buttons,All,Prevent double submission during async actions,Disable button and show loading state,Allow multiple clicks during processing,disabled={loading} spinner,Button clickable while loading,High
+33,Interaction,Error Feedback,All,Users need to know when something fails,Show clear error messages near problem,Silent failures with no feedback,Red border + error message,No indication of error,High
+34,Interaction,Success Feedback,All,Confirm successful actions to users,Show success message or visual change,No confirmation of completed action,Toast notification or checkmark,Action completes silently,Medium
+35,Interaction,Confirmation Dialogs,All,Prevent accidental destructive actions,Confirm before delete/irreversible actions,Delete without confirmation,Are you sure modal,Direct delete on click,High
+36,Accessibility,Color Contrast,All,Text must be readable against background,Minimum 4.5:1 ratio for normal text,Low contrast text,#333 on white (7:1),#999 on white (2.8:1),High
+37,Accessibility,Color Only,All,Don't convey information by color alone,Use icons/text in addition to color,Red/green only for error/success,Red text + error icon,Red border only for error,High
+38,Accessibility,Alt Text,All,Images need text alternatives,Descriptive alt text for meaningful images,Empty or missing alt attributes,alt='Dog playing in park',alt='' for content images,High
+39,Accessibility,Heading Hierarchy,Web,Screen readers use headings for navigation,Use sequential heading levels h1-h6,Skip heading levels or misuse for styling,h1 then h2 then h3,h1 then h4,Medium
+40,Accessibility,ARIA Labels,All,Interactive elements need accessible names,Add aria-label for icon-only buttons,Icon buttons without labels,aria-label='Close menu',<button><Icon/></button>,High
+41,Accessibility,Keyboard Navigation,Web,All functionality accessible via keyboard,Tab order matches visual order,Keyboard traps or illogical tab order,tabIndex for custom order,Unreachable elements,High
+42,Accessibility,Screen Reader,All,Content should make sense when read aloud,Use semantic HTML and ARIA properly,Div soup with no semantics,<nav> <main> <article>,<div> for everything,Medium
+43,Accessibility,Form Labels,All,Inputs must have associated labels,Use label with for attribute or wrap input,Placeholder-only inputs,<label for='email'>,placeholder='Email' only,High
+44,Accessibility,Error Messages,All,Error messages must be announced,Use aria-live or role=alert for errors,Visual-only error indication,role='alert',Red border only,High
+45,Accessibility,Skip Links,Web,Allow keyboard users to skip navigation,Provide skip to main content link,No skip link on nav-heavy pages,Skip to main content link,100 tabs to reach content,Medium
+46,Performance,Image Optimization,All,Large images slow page load,Use appropriate size and format (WebP),Unoptimized full-size images,srcset with multiple sizes,4000px image for 400px display,High
+47,Performance,Lazy Loading,All,Load content as needed,Lazy load below-fold images and content,Load everything upfront,loading='lazy',All images eager load,Medium
+48,Performance,Code Splitting,Web,Large bundles slow initial load,Split code by route/feature,Single large bundle,dynamic import(),All code in main bundle,Medium
+49,Performance,Caching,Web,Repeat visits should be fast,Set appropriate cache headers,No caching strategy,Cache-Control headers,Every request hits server,Medium
+50,Performance,Font Loading,Web,Web fonts can block rendering,Use font-display swap or optional,Invisible text during font load,font-display: swap,FOIT (Flash of Invisible Text),Medium
+51,Performance,Third Party Scripts,Web,External scripts can block rendering,Load non-critical scripts async/defer,Synchronous third-party scripts,async or defer attribute,<script src='...'> in head,Medium
+52,Performance,Bundle Size,Web,Large JavaScript slows interaction,Monitor and minimize bundle size,Ignore bundle size growth,Bundle analyzer,No size monitoring,Medium
+53,Performance,Render Blocking,Web,CSS/JS can block first paint,Inline critical CSS defer non-critical,Large blocking CSS files,Critical CSS inline,All CSS in head,Medium
+54,Forms,Input Labels,All,Every input needs a visible label,Always show label above or beside input,Placeholder as only label,<label>Email</label><input>,placeholder='Email' only,High
+55,Forms,Error Placement,All,Errors should appear near the problem,Show error below related input,Single error message at top of form,Error under each field,All errors at form top,Medium
+56,Forms,Inline Validation,All,Validate as user types or on blur,Validate on blur for most fields,Validate only on submit,onBlur validation,Submit-only validation,Medium
+57,Forms,Input Types,All,Use appropriate input types,Use email tel number url etc,Text input for everything,type='email',type='text' for email,Medium
+58,Forms,Autofill Support,Web,Help browsers autofill correctly,Use autocomplete attribute properly,Block or ignore autofill,autocomplete='email',autocomplete='off' everywhere,Medium
+59,Forms,Required Indicators,All,Mark required fields clearly,Use asterisk or (required) text,No indication of required fields,* required indicator,Guess which are required,Medium
+60,Forms,Password Visibility,All,Let users see password while typing,Toggle to show/hide password,No visibility toggle,Show/hide password button,Password always hidden,Medium
+61,Forms,Submit Feedback,All,Confirm form submission status,Show loading then success/error state,No feedback after submit,Loading -> Success message,Button click with no response,High
+62,Forms,Input Affordance,All,Inputs should look interactive,Use distinct input styling,Inputs that look like plain text,Border/background on inputs,Borderless inputs,Medium
+63,Forms,Mobile Keyboards,Mobile,Show appropriate keyboard for input type,Use inputmode attribute,Default keyboard for all inputs,inputmode='numeric',Text keyboard for numbers,Medium
+64,Responsive,Mobile First,Web,Design for mobile then enhance for larger,Start with mobile styles then add breakpoints,Desktop-first causing mobile issues,Default mobile + md: lg: xl:,Desktop default + max-width queries,Medium
+65,Responsive,Breakpoint Testing,Web,Test at all common screen sizes,Test at 320 375 414 768 1024 1440,Only test on your device,Multiple device testing,Single device development,Medium
+66,Responsive,Touch Friendly,Web,Mobile layouts need touch-sized targets,Increase touch targets on mobile,Same tiny buttons on mobile,Larger buttons on mobile,Desktop-sized targets on mobile,High
+67,Responsive,Readable Font Size,All,Text must be readable on all devices,Minimum 16px body text on mobile,Tiny text on mobile,text-base or larger,text-xs for body text,High
+68,Responsive,Viewport Meta,Web,Set viewport for mobile devices,Use width=device-width initial-scale=1,Missing or incorrect viewport,<meta name='viewport'...>,No viewport meta tag,High
+69,Responsive,Horizontal Scroll,Web,Avoid horizontal scrolling,Ensure content fits viewport width,Content wider than viewport,max-w-full overflow-x-hidden,Horizontal scrollbar on mobile,High
+70,Responsive,Image Scaling,Web,Images should scale with container,Use max-width: 100% on images,Fixed width images overflow,max-w-full h-auto,width='800' fixed,Medium
+71,Responsive,Table Handling,Web,Tables can overflow on mobile,Use horizontal scroll or card layout,Wide tables breaking layout,overflow-x-auto wrapper,Table overflows viewport,Medium
+72,Typography,Line Height,All,Adequate line height improves readability,Use 1.5-1.75 for body text,Cramped or excessive line height,leading-relaxed (1.625),leading-none (1),Medium
+73,Typography,Line Length,Web,Long lines are hard to read,Limit to 65-75 characters per line,Full-width text on large screens,max-w-prose,Full viewport width text,Medium
+74,Typography,Font Size Scale,All,Consistent type hierarchy aids scanning,Use consistent modular scale,Random font sizes,Type scale (12 14 16 18 24 32),Arbitrary sizes,Medium
+75,Typography,Font Loading,Web,Fonts should load without layout shift,Reserve space with fallback font,Layout shift when fonts load,font-display: swap + similar fallback,No fallback font,Medium
+76,Typography,Contrast Readability,All,Body text needs good contrast,Use darker text on light backgrounds,Gray text on gray background,text-gray-900 on white,text-gray-400 on gray-100,High
+77,Typography,Heading Clarity,All,Headings should stand out from body,Clear size/weight difference,Headings similar to body text,Bold + larger size,Same size as body,Medium
+78,Feedback,Loading Indicators,All,Show system status during waits,Show spinner/skeleton for operations > 300ms,No feedback during loading,Skeleton or spinner,Frozen UI,High
+79,Feedback,Empty States,All,Guide users when no content exists,Show helpful message and action,Blank empty screens,No items yet. Create one!,Empty white space,Medium
+80,Feedback,Error Recovery,All,Help users recover from errors,Provide clear next steps,Error without recovery path,Try again button + help link,Error message only,Medium
+81,Feedback,Progress Indicators,All,Show progress for multi-step processes,Step indicators or progress bar,No indication of progress,Step 2 of 4 indicator,No step information,Medium
+82,Feedback,Toast Notifications,All,Transient messages for non-critical info,Auto-dismiss after 3-5 seconds,Toasts that never disappear,Auto-dismiss toast,Persistent toast,Medium
+83,Feedback,Confirmation Messages,All,Confirm successful actions,Brief success message,Silent success,Saved successfully toast,No confirmation,Medium
+84,Content,Truncation,All,Handle long content gracefully,Truncate with ellipsis and expand option,Overflow or broken layout,line-clamp-2 with expand,Overflow or cut off,Medium
+85,Content,Date Formatting,All,Use locale-appropriate date formats,Use relative or locale-aware dates,Ambiguous date formats,2 hours ago or locale format,01/02/03,Low
+86,Content,Number Formatting,All,Format large numbers for readability,Use thousand separators or abbreviations,Long unformatted numbers,"1.2K or 1,234",1234567,Low
+87,Content,Placeholder Content,All,Show realistic placeholders during dev,Use realistic sample data,Lorem ipsum everywhere,Real sample content,Lorem ipsum,Low
+88,Onboarding,User Freedom,All,Users should be able to skip tutorials,Provide Skip and Back buttons,Force linear unskippable tour,Skip Tutorial button,Locked overlay until finished,Medium
+89,Search,Autocomplete,Web,Help users find results faster,Show predictions as user types,Require full type and enter,Debounced fetch + dropdown,No suggestions,Medium
+90,Search,No Results,Web,Dead ends frustrate users,Show 'No results' with suggestions,Blank screen or '0 results',Try searching for X instead,No results found.,Medium
+91,Data Entry,Bulk Actions,Web,Editing one by one is tedious,Allow multi-select and bulk edit,Single row actions only,Checkbox column + Action bar,Repeated actions per row,Low
+92,AI Interaction,Disclaimer,All,Users need to know they talk to AI,Clearly label AI generated content,Present AI as human,AI Assistant label,Fake human name without label,High
+93,AI Interaction,Streaming,All,Waiting for full text is slow,Stream text response token by token,Show loading spinner for 10s+,Typewriter effect,Spinner until 100% complete,Medium
+94,Spatial UI,Gaze Hover,VisionOS,Elements should respond to eye tracking before pinch,Scale/highlight element on look,Static element until pinch,hoverEffect(),onTap only,High
+95,Spatial UI,Depth Layering,VisionOS,UI needs Z-depth to separate content from environment,Use glass material and z-offset,Flat opaque panels blocking view,.glassBackgroundEffect(),bg-white,Medium
+96,Sustainability,Auto-Play Video,Web,Video consumes massive data and energy,Click-to-play or pause when off-screen,Auto-play high-res video loops,playsInline muted preload='none',autoplay loop,Medium
+97,Sustainability,Asset Weight,Web,Heavy 3D/Image assets increase carbon footprint,Compress and lazy load 3D models,Load 50MB textures,Draco compression,Raw .obj files,Medium
+98,AI Interaction,Feedback Loop,All,AI needs user feedback to improve,Thumps up/down or 'Regenerate',Static output only,Feedback component,Read-only text,Low
+99,Accessibility,Motion Sensitivity,All,Parallax/Scroll-jacking causes nausea,Respect prefers-reduced-motion,Force scroll effects,@media (prefers-reduced-motion),ScrollTrigger.create(),High

package/dist/core/templates/skills/documents-skill.md

@@ -0,0 +1,114 @@
+# Skill: Documents (Cross-Cutting)
+
+## Purpose
+
+This skill is used to create documentation for both technical and end-user audiences. Ensures documentation is complete, clear, and easy to understand.
+
+## When to Use
+
+- When creating technical documentation
+- When writing user guides
+- When documenting APIs
+- When creating changelogs
+- When writing installation/setup guides
+
+## Step-by-Step Process
+
+### Step 1: Identify Document Type
+- Technical docs: For developers
+- User guide: For end-users
+- API docs: For API consumers
+- Changelog: For version releases
+
+### Step 2: Choose Appropriate Template
+- Technical: `templates/technical-doc-template.md`
+- User guide: `templates/user-guide-template.md`
+- API: `templates/api-doc-template.md`
+- Changelog: `templates/changelog-template.md`
+
+### Step 3: Gather Information
+- Features and functionality
+- Installation steps
+- Configuration options
+- Usage examples
+- Troubleshooting tips
+
+### Step 4: Write Documentation
+- Follow template structure
+- Use good examples as reference
+- Ensure code examples work
+- Include screenshots if needed
+
+### Step 5: Validate & Generate
+- Run script: `scripts/validate-docs.py`
+- Run script: `scripts/generate-docs.sh` (if available)
+- Review with good examples
+- Test with target audience
+
+## Required Input
+
+- **Document type**: Technical, user guide, API, changelog
+- **Target audience**: Developers, end-users, admins
+- **Features to document**: List of features to document
+- **Code examples**: Code samples to include
+- **Screenshots**: Images if needed
+
+## Expected Output
+
+- Complete documentation file
+- Proper formatting and structure
+- Working code examples
+- Clear instructions
+- Troubleshooting section
+
+## Tone & Rules
+
+### Writing Style
+- **Clear**: Write clearly, easy to understand
+- **Concise**: Brief, not verbose
+- **Actionable**: Can be followed
+- **Complete**: Complete necessary information
+
+### Technical Docs
+- Code examples must work
+- Include prerequisites
+- Explain "why" not just "what"
+- Link to related docs
+
+### User Guides
+- Step-by-step instructions
+- Screenshots for complex steps
+- Common issues and solutions
+- Plain language (avoid jargon)
+
+### Limitations
+- ❌ DO NOT skip prerequisites
+- ❌ DO NOT assume prior knowledge
+- ❌ DO NOT use untested code examples
+- ❌ DO NOT write too technical for user guides
+- ❌ DO NOT skip troubleshooting
+
+## Available Templates
+
+- `templates/technical-doc-template.md` - Technical documentation
+- `templates/user-guide-template.md` - User guide
+- `templates/api-doc-template.md` - API documentation
+- `templates/changelog-template.md` - Changelog template
+
+## Available Scripts
+
+- `scripts/generate-docs.sh` - Automatically generate docs from code
+- `scripts/validate-docs.py` - Validate format and completeness
+
+## Examples
+
+See `examples/` directory for reference:
+- `good-technical-doc.md` - Good technical doc example
+- `good-user-guide.md` - Good user guide example
+- `good-api-doc.md` - Good API doc example
+
+## Links to Other Skills
+
+- **module-codebase**: Document module structure
+- **ui-ux**: Document UI components and design system
+- **content-optimization**: Optimize documentation for clarity

package/dist/core/templates/skills/e2e-test-skill.md

@@ -0,0 +1,119 @@
+# Skill: End-to-End (E2E) Testing (Cross-Cutting)
+
+## Purpose
+
+This skill is used to create end-to-end tests that verify complete user workflows from start to finish. E2E tests simulate real user interactions with the application.
+
+## When to Use
+
+- When testing complete user workflows
+- When testing critical user journeys
+- When testing UI interactions
+- When verifying application behavior from user perspective
+- When testing authentication flows
+- When testing payment/transaction flows
+
+## Step-by-Step Process
+
+### Step 1: Identify User Journeys
+- Map critical user workflows
+- Identify key user scenarios
+- List user personas and their goals
+- Determine test priorities (critical paths first)
+- Document expected user behavior
+
+### Step 2: Set Up E2E Testing Framework
+- Choose E2E testing tool (Playwright, Cypress, Selenium, etc.)
+- Configure test environment
+- Set up test browser/headless mode
+- Configure test data and user accounts
+- Set up test application instance
+
+### Step 3: Write E2E Tests
+- Create test files for each user journey
+- Write tests simulating user actions (click, type, navigate)
+- Test complete workflows from start to finish
+- Verify UI elements and feedback
+- Test error scenarios and edge cases
+- Use page objects for maintainability
+
+### Step 4: Run and Verify
+- Run E2E tests
+- Verify tests pass consistently
+- Check test execution time
+- Review test failures and flakiness
+- Ensure tests are stable and reliable
+
+### Step 5: Maintain Tests
+- Update tests when UI changes
+- Keep page objects synchronized with UI
+- Document test scenarios
+- Monitor test stability
+
+## Required Input
+
+- **User journeys**: List of critical user workflows
+- **Test environment**: Application URL and test environment setup
+- **Test accounts**: User accounts for testing
+- **E2E framework**: Testing framework to use
+- **Browser**: Browser to test in (Chrome, Firefox, etc.)
+
+## Expected Output
+
+- E2E test files
+- Test scenarios covering user journeys
+- Page objects for UI elements
+- Passing E2E test suite
+- Documentation of E2E test scenarios
+
+## Tone & Rules
+
+### Test Scope
+- Focus on critical user journeys
+- Test from user perspective
+- Verify complete workflows
+- Test happy paths and error scenarios
+
+### Test Stability
+- Use reliable selectors (data-testid, stable IDs)
+- Add appropriate waits for async operations
+- Handle flaky elements (retries, explicit waits)
+- Keep tests independent and isolated
+
+### Performance
+- E2E tests are slowest (run separately)
+- Use headless mode for CI
+- Parallelize tests when possible
+- Consider test execution time
+
+### Limitations
+- ❌ DO NOT test every UI element (focus on journeys)
+- ❌ DO NOT use brittle selectors (XPath with complex paths)
+- ❌ DO NOT skip error handling
+- ❌ DO NOT write tests that depend on timing
+- ❌ DO NOT test implementation details
+
+## Available Templates
+
+- `templates/e2e-test-template.js` - JavaScript/Playwright template
+- `templates/e2e-test-template.ts` - TypeScript/Cypress template
+- `templates/e2e-test-template.py` - Python/Selenium template
+
+## Available Scripts
+
+- `scripts/setup-e2e-env.sh` - Set up E2E test environment
+- `scripts/run-e2e-tests.sh` - Run E2E test suite
+
+## Examples
+
+See `examples/` directory for reference:
+- `good-e2e-test/` - Well-structured E2E tests
+- `bad-e2e-test/` - Examples to avoid
+
+## Links to Other Skills
+
+- **unit-test**: Use for testing individual components
+- **integration-test**: Use for testing component interactions
+- **ui-ux**: Reference when testing UI interactions
+- **documents**: Use to document E2E test strategy
+

package/dist/core/templates/skills/integration-test-skill.md

@@ -0,0 +1,118 @@
+# Skill: Integration Testing (Cross-Cutting)
+
+## Purpose
+
+This skill is used to create integration tests that verify how different components work together. Integration tests check interactions between modules, services, databases, and external APIs.
+
+## When to Use
+
+- When testing component interactions
+- When testing API endpoints
+- When testing database operations
+- When testing service integrations
+- When verifying data flow between components
+- When testing with real dependencies (not mocks)
+
+## Step-by-Step Process
+
+### Step 1: Identify Integration Points
+- Map component dependencies
+- Identify external services and APIs
+- List database operations
+- Determine integration boundaries
+- Identify critical integration paths
+
+### Step 2: Set Up Test Environment
+- Configure test database
+- Set up test services/mocks for external APIs
+- Configure test environment variables
+- Prepare test data fixtures
+- Set up cleanup procedures
+
+### Step 3: Write Integration Tests
+- Create test files for integration scenarios
+- Test component interactions
+- Test API endpoints with real requests
+- Test database operations
+- Test error handling across components
+- Use test fixtures for consistent data
+
+### Step 4: Run and Verify
+- Run integration tests
+- Verify test isolation (tests don't affect each other)
+- Check test execution time
+- Ensure proper cleanup after tests
+- Verify tests pass consistently
+
+### Step 5: Maintain Tests
+- Update tests when interfaces change
+- Keep test data synchronized
+- Document test scenarios
+- Monitor test execution time
+
+## Required Input
+
+- **Components**: List of components to integrate
+- **APIs**: API endpoints to test
+- **Database schema**: Database structure for testing
+- **External services**: External services to mock or use
+- **Test data**: Sample data for testing
+
+## Expected Output
+
+- Integration test files
+- Test scenarios covering integration paths
+- Test fixtures and setup code
+- Passing integration test suite
+- Documentation of integration test scenarios
+
+## Tone & Rules
+
+### Test Scope
+- Test real interactions between components
+- Use real databases (test database)
+- Mock external services that can't be controlled
+- Test error propagation across boundaries
+
+### Test Data
+- Use consistent test fixtures
+- Clean up test data after tests
+- Use transactions for database tests when possible
+- Isolate tests to prevent interference
+
+### Performance
+- Integration tests are slower than unit tests
+- Run integration tests separately from unit tests
+- Use test database (not production)
+- Consider test execution time
+
+### Limitations
+- ❌ DO NOT use production database
+- ❌ DO NOT test with real external APIs in CI (use mocks)
+- ❌ DO NOT write tests that depend on test execution order
+- ❌ DO NOT skip cleanup (tests must be isolated)
+- ❌ DO NOT test implementation details
+
+## Available Templates
+
+- `templates/integration-test-template.js` - JavaScript integration test template
+- `templates/integration-test-template.php` - PHP integration test template
+- `templates/integration-test-template.py` - Python integration test template
+
+## Available Scripts
+
+- `scripts/setup-test-db.sh` - Set up test database
+- `scripts/seed-test-data.sh` - Seed test data
+
+## Examples
+
+See `examples/` directory for reference:
+- `good-integration-test/` - Well-structured integration tests
+- `bad-integration-test/` - Examples to avoid
+
+## Links to Other Skills
+
+- **unit-test**: Use unit tests before integration tests
+- **e2e-test**: Use for end-to-end user scenarios
+- **documents**: Use to document integration test strategy
+

package/dist/core/templates/skills/module-codebase-skill.md

@@ -0,0 +1,110 @@
+# Skill: Module Codebase (Perfex Module)
+
+## Purpose
+
+This skill is used to create and manage codebase structure for Perfex CRM modules following Perfex best practices.
+
+## When to Use
+
+- When creating a new module for Perfex CRM
+- When refactoring existing module structure
+- When ensuring module follows Perfex conventions
+- When creating standard folder and file structure for module
+
+## Step-by-Step Process
+
+### Step 1: Analyze Requirements
+- Identify main functionality of module
+- Identify required database tables
+- Identify hooks and filters to use
+- Identify permissions to create
+
+### Step 2: Scaffold Structure
+- Run script: `scripts/scaffold-module.sh <module-name>`
+- Script will create standard folder structure:
+  - `modules/<module-name>/`
+  - `modules/<module-name>/controllers/`
+  - `modules/<module-name>/models/`
+  - `modules/<module-name>/views/`
+  - `modules/<module-name>/language/`
+  - `modules/<module-name>/assets/`
+- Copy templates to correct locations
+
+### Step 3: Configure Module
+- Fill information in `module-config.php` (from template)
+- Register module in Perfex system
+- Set up permissions and menu items
+
+### Step 4: Implement Core Logic
+- Create controllers following Perfex structure
+- Create models with Eloquent patterns
+- Implement hooks and filters
+- Create database migrations
+
+### Step 5: Testing & Documentation
+- Test module with Perfex core
+- Write documentation (use documents skill)
+- Create user guide (use documents skill)
+
+## Required Input
+
+- **Module name**: Module name (kebab-case, e.g., `category-management`)
+- **Module description**: Module functionality description
+- **Database tables**: List of tables to create
+- **Hooks required**: List of hooks to implement
+- **Permissions**: List of permissions to create
+- **Menu items**: List of menu items to add
+
+## Expected Output
+
+- Complete module folder structure
+- Fully configured files
+- Database migrations
+- Module registration code
+- Basic documentation structure
+
+## Tone & Rules
+
+### Code Style
+- Follow PSR-12 coding standards
+- Use camelCase for functions
+- Use PascalCase for classes
+- Comment in English
+
+### Naming Conventions
+- Module folder: `perfex-<module-name>`
+- Class names: `Perfex<ModuleName>`
+- Function names: `perfex_<module_name>_<action>`
+- Database tables: `tbl<ModuleName>`
+
+### Limitations
+- ❌ DO NOT create global functions (except hooks)
+- ❌ DO NOT hardcode database credentials
+- ❌ DO NOT bypass Perfex permission system
+- ❌ DO NOT modify core Perfex files
+- ❌ DO NOT use deprecated Perfex APIs
+
+## Available Templates
+
+- `templates/module-structure.php` - Basic module structure
+- `templates/module-config.php` - Module configuration file
+- `templates/module-hooks.php` - Template for hooks
+- `templates/module-migration.php` - Database migration template
+
+## Available Scripts
+
+- `scripts/scaffold-module.sh` - Automatically create module structure
+
+## Examples
+
+See `examples/` directory for reference:
+- `good-module-structure/` - Example of well-organized module
+- `bad-module-structure/` - Example to avoid
+
+## Links to Other Skills
+
+- **documents**: Use to create technical docs and user guide
+- **ui-ux**: Use when module has admin interface
+- **content-optimization**: Use for module marketing pages
+- **module-registration**: Use to register module with Perfex
+- **permission-group**: Use to create permissions for module