heraspec 0.1.12 → 0.1.14

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

@@ -1,118 +1,118 @@
-# Skill: Feature Suggestion (Cross-Cutting)
-
-## Purpose
-
-This skill is used to analyze existing project structure and suggest new features that would integrate well with the current codebase. It helps identify opportunities for enhancements and new functionality based on existing patterns and architecture.
-
-## When to Use
-
-- When planning new features for a project
-- When identifying gaps in functionality
-- When analyzing project structure for enhancement opportunities
-- When proposing improvements based on existing patterns
-- When suggesting features that align with project architecture
-
-## Step-by-Step Process
-
-### Step 1: Analyze Project Structure
-- Read and understand `heraspec/project.md`
-- Review existing specs in `heraspec/specs/`
-- Analyze existing changes and their patterns
-- Identify project type and tech stack
-- Map current feature set
-
-### Step 2: Identify Integration Points
-- Find logical places for new features
-- Identify patterns in existing code
-- Determine appropriate project structure locations
-- Consider dependencies and relationships
-- Map feature hierarchy
-
-### Step 3: Generate Suggestions
-- Create feature suggestions based on analysis
-- Ensure suggestions align with project type
-- Consider existing patterns and conventions
-- Propose features that enhance current functionality
-- Suggest improvements and extensions
-
-### Step 4: Organize Suggestions
-- Group suggestions by category/domain
-- Prioritize based on feasibility and value
-- Create suggestion files in appropriate locations
-- Link suggestions to existing features
-- Document integration points
-
-### Step 5: Review and Refine
-- Review suggestions for consistency
-- Ensure suggestions follow project conventions
-- Verify integration points are correct
-- Refine based on project requirements
-- Prepare for implementation planning
-
-## Required Input
-
-- **Project structure**: Understanding of project organization
-- **Existing specs**: Current feature specifications
-- **Project type**: Type of project (plugin, module, app, etc.)
-- **Tech stack**: Technologies used in the project
-- **Domain context**: Business domain and requirements
-
-## Expected Output
-
-- Feature suggestion files
-- Suggestions organized by category
-- Integration points identified
-- Suggestions linked to existing features
-- Documentation of suggested enhancements
-
-## Tone & Rules
-
-### Suggestion Quality
-- Suggest features that add value
-- Align with project type and architecture
-- Consider existing patterns and conventions
-- Propose realistic and feasible features
-- Enhance rather than replace existing functionality
-
-### Integration
-- Identify appropriate locations for features
-- Consider dependencies and relationships
-- Follow existing project structure
-- Maintain consistency with current patterns
-- Document integration approach
-
-### Documentation
-- Clearly describe suggested features
-- Explain integration points
-- Link to related existing features
-- Provide context and rationale
-- Include implementation considerations
-
-### Limitations
-- ❌ DO NOT suggest features that conflict with existing architecture
-- ❌ DO NOT ignore project conventions
-- ❌ DO NOT suggest overly complex features
-- ❌ DO NOT duplicate existing functionality
-- ❌ DO NOT suggest features without considering integration
-
-## Available Templates
-
-- `templates/suggestion-template.md` - Template for feature suggestions
-- `templates/suggestion-category-template.md` - Template for organizing suggestions by category
-
-## Available Scripts
-
-- `scripts/analyze-project-structure.py` - Analyze project structure for suggestion opportunities
-
-## Examples
-
-See `examples/` directory for reference:
-- `good-suggestions/` - Well-structured feature suggestions
-- `bad-suggestions/` - Examples to avoid
-
-## Links to Other Skills
-
-- **documents**: Use to document suggestion rationale
-- **unit-test**: Consider testability when suggesting features
-- **integration-test**: Consider integration testing when suggesting features
-
+# Skill: Feature Suggestion (Cross-Cutting)
+
+## Purpose
+
+This skill is used to analyze existing project structure and suggest new features that would integrate well with the current codebase. It helps identify opportunities for enhancements and new functionality based on existing patterns and architecture.
+
+## When to Use
+
+- When planning new features for a project
+- When identifying gaps in functionality
+- When analyzing project structure for enhancement opportunities
+- When proposing improvements based on existing patterns
+- When suggesting features that align with project architecture
+
+## Step-by-Step Process
+
+### Step 1: Analyze Project Structure
+- Read and understand `heraspec/project.md`
+- Review existing specs in `heraspec/specs/`
+- Analyze existing changes and their patterns
+- Identify project type and tech stack
+- Map current feature set
+
+### Step 2: Identify Integration Points
+- Find logical places for new features
+- Identify patterns in existing code
+- Determine appropriate project structure locations
+- Consider dependencies and relationships
+- Map feature hierarchy
+
+### Step 3: Generate Suggestions
+- Create feature suggestions based on analysis
+- Ensure suggestions align with project type
+- Consider existing patterns and conventions
+- Propose features that enhance current functionality
+- Suggest improvements and extensions
+
+### Step 4: Organize Suggestions
+- Group suggestions by category/domain
+- Prioritize based on feasibility and value
+- Create suggestion files in appropriate locations
+- Link suggestions to existing features
+- Document integration points
+
+### Step 5: Review and Refine
+- Review suggestions for consistency
+- Ensure suggestions follow project conventions
+- Verify integration points are correct
+- Refine based on project requirements
+- Prepare for implementation planning
+
+## Required Input
+
+- **Project structure**: Understanding of project organization
+- **Existing specs**: Current feature specifications
+- **Project type**: Type of project (plugin, module, app, etc.)
+- **Tech stack**: Technologies used in the project
+- **Domain context**: Business domain and requirements
+
+## Expected Output
+
+- Feature suggestion files
+- Suggestions organized by category
+- Integration points identified
+- Suggestions linked to existing features
+- Documentation of suggested enhancements
+
+## Tone & Rules
+
+### Suggestion Quality
+- Suggest features that add value
+- Align with project type and architecture
+- Consider existing patterns and conventions
+- Propose realistic and feasible features
+- Enhance rather than replace existing functionality
+
+### Integration
+- Identify appropriate locations for features
+- Consider dependencies and relationships
+- Follow existing project structure
+- Maintain consistency with current patterns
+- Document integration approach
+
+### Documentation
+- Clearly describe suggested features
+- Explain integration points
+- Link to related existing features
+- Provide context and rationale
+- Include implementation considerations
+
+### Limitations
+- ❌ DO NOT suggest features that conflict with existing architecture
+- ❌ DO NOT ignore project conventions
+- ❌ DO NOT suggest overly complex features
+- ❌ DO NOT duplicate existing functionality
+- ❌ DO NOT suggest features without considering integration
+
+## Available Templates
+
+- `templates/suggestion-template.md` - Template for feature suggestions
+- `templates/suggestion-category-template.md` - Template for organizing suggestions by category
+
+## Available Scripts
+
+- `scripts/analyze-project-structure.py` - Analyze project structure for suggestion opportunities
+
+## Examples
+
+See `examples/` directory for reference:
+- `good-suggestions/` - Well-structured feature suggestions
+- `bad-suggestions/` - Examples to avoid
+
+## Links to Other Skills
+
+- **documents**: Use to document suggestion rationale
+- **unit-test**: Consider testability when suggesting features
+- **integration-test**: Consider integration testing when suggesting features
+

package/dist/core/templates/skills/templates/accessibility-checklist.md

@@ -1,40 +1,40 @@
-# Accessibility Checklist (WCAG 2.1 AA)
-
-## Perceivable
-
-- [ ] All images have descriptive alt text
-- [ ] Color is not the only means of conveying information
-- [ ] Text contrast ratio meets 4.5:1 for normal text, 3:1 for large text
-- [ ] Content can be resized up to 200% without loss of functionality
-
-## Operable
-
-- [ ] All functionality available via keyboard
-- [ ] No keyboard traps
-- [ ] Focus indicators visible
-- [ ] Sufficient time limits (if any) can be extended
-- [ ] No content that causes seizures (flashing)
-- [ ] Touch targets at least 44x44px
-
-## Understandable
-
-- [ ] Page titles are descriptive
-- [ ] Form inputs have labels
-- [ ] Error messages are clear and helpful
-- [ ] Language of page is declared
-- [ ] Navigation is consistent
-
-## Robust
-
-- [ ] Valid HTML markup
-- [ ] ARIA attributes used correctly (if needed)
-- [ ] Screen reader compatible
-- [ ] Works with assistive technologies
-
-## Additional Best Practices
-
-- [ ] `prefers-reduced-motion` respected
-- [ ] Skip links for keyboard navigation
-- [ ] Logical tab order
-- [ ] Focus management for modals/dialogs
-
+# Accessibility Checklist (WCAG 2.1 AA)
+
+## Perceivable
+
+- [ ] All images have descriptive alt text
+- [ ] Color is not the only means of conveying information
+- [ ] Text contrast ratio meets 4.5:1 for normal text, 3:1 for large text
+- [ ] Content can be resized up to 200% without loss of functionality
+
+## Operable
+
+- [ ] All functionality available via keyboard
+- [ ] No keyboard traps
+- [ ] Focus indicators visible
+- [ ] Sufficient time limits (if any) can be extended
+- [ ] No content that causes seizures (flashing)
+- [ ] Touch targets at least 44x44px
+
+## Understandable
+
+- [ ] Page titles are descriptive
+- [ ] Form inputs have labels
+- [ ] Error messages are clear and helpful
+- [ ] Language of page is declared
+- [ ] Navigation is consistent
+
+## Robust
+
+- [ ] Valid HTML markup
+- [ ] ARIA attributes used correctly (if needed)
+- [ ] Screen reader compatible
+- [ ] Works with assistive technologies
+
+## Additional Best Practices
+
+- [ ] `prefers-reduced-motion` respected
+- [ ] Skip links for keyboard navigation
+- [ ] Logical tab order
+- [ ] Focus management for modals/dialogs
+