PinionEducation/pinion-innovation-content
12
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: release v1.1.0 - add Support Team Guide and User Guide, update all docs to v1.1.0

Browse Source
This commit is contained in:
Alejandro Malo
2026-04-23 23:07:19 -06:00
commit 52e3613d01
85 changed files with 6522 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
modes/lx-designer/rules/1_workflow.xml Normal file
View File

@@ -0,0 +1,40 @@
<workflow>
# LX Designer Workflow
## Primary Workflow: Learning Experience Design
1. **Receive Content Package**
- Review curriculum and lesson content
- Understand learning objectives and assessments
- Identify target audience and context
- Note technical constraints and platform requirements
2. **Map Learner Journey**
- Define learner entry points
- Map progression through content
- Identify decision points and branches
- Use `journey-mapper` skill
3. **Design Engagement Strategy**
- Identify engagement opportunities
- Select appropriate gamification elements
- Design motivation and retention mechanics
- Use `engagement-analyzer` and `gamification-designer` skills
4. **Specify Interactive Elements**
- Define interaction types and behaviors
- Create UI component specifications
- Design feedback mechanisms
- Use `ui-spec-generator` skill
5. **Design Microlearning Structure**
- Chunk content into microlearning units
- Design spaced repetition schedule
- Create learning sequences
- Use `microlearning-architect` skill
6. **Document and Deliver**
- Create journey maps and specifications
- Store in `design/` and `ux/` directories
- Provide handoff notes for Content Producer
</workflow>

43
modes/lx-designer/rules/2_best_practices.xml Normal file
View File

@@ -0,0 +1,43 @@
<best_practices>
# LX Designer Best Practices
## Journey Mapping
- Start with learner goals and motivations
- Identify key milestones and checkpoints
- Map emotional journey alongside cognitive journey
- Include opportunities for reflection at key points
- Design for both linear and non-linear progression
## Gamification
- Align game elements to learning objectives, not just engagement
- Use intrinsic motivation over extrinsic rewards
- Provide meaningful choices with visible consequences
- Balance challenge and skill (flow state)
- Avoid over-gamification that distracts from learning
## Microlearning
- Keep units focused on single learning objective
- Design for 5-15 minute completion time
- Include clear entry and exit points
- Provide context between micro-units
- Use spaced repetition for retention
## UI/UX Design
- Prioritize clarity over decoration
- Use consistent navigation patterns
- Provide clear progress indicators
- Design for mobile-first where appropriate
- Include accessibility from the start, not as an afterthought
## Engagement
- Use variety to maintain attention
- Include social elements where possible
- Provide timely, specific feedback
- Create opportunities for learner agency
- Design for completion (reduce drop-off)
</best_practices>

77
modes/lx-designer/rules/3_common_patterns.xml Normal file
View File

@@ -0,0 +1,77 @@
<common_patterns>
# LX Designer Common Patterns
## Pattern: Learning Path
**Description:** Structured sequence of learning activities with clear progression.
**Structure:**
1. Entry assessment or placement
2. Core learning modules in sequence
3. Checkpoints for progress verification
4. Branching based on performance
5. Exit assessment or demonstration
**When to Use:** Structured courses, certification programs.
---
## Pattern: Badge and Achievement System
**Description:** Gamification system recognizing learner accomplishments.
**Structure:**
1. Define achievement categories (completion, mastery, participation)
2. Create badge hierarchy (bronze, silver, gold)
3. Set clear criteria for each badge
4. Design visual badge system
5. Include social sharing where appropriate
**When to Use:** Motivation, recognition of achievement, engagement.
---
## Pattern: Spaced Repetition Schedule
**Description:** Review schedule optimized for long-term retention.
**Structure:**
1. Initial learning event
2. First review: 1 day later
3. Second review: 3 days later
4. Third review: 1 week later
5. Fourth review: 2 weeks later
6. Adjust intervals based on performance
**When to Use:** Vocabulary, facts, procedures requiring long-term retention.
---
## Pattern: Progress Dashboard
**Description:** Visual display of learner progress and achievements.
**Structure:**
1. Overall progress indicator
2. Module-by-module status
3. Assessment scores and trends
4. Time spent and engagement metrics
5. Recommendations for next steps
**When to Use:** Self-paced courses, long-term programs.
---
## Pattern: Choice-Based Learning
**Description:** Learners choose their path through content.
**Structure:**
1. Present learning objectives
2. Offer multiple paths to achieve them
3. Allow learners to select preferred path
4. Track choices and outcomes
5. Provide recommendations based on choices
**When to Use:** Experienced learners, diverse backgrounds, self-directed learning.
</common_patterns>

65
modes/lx-designer/rules/4_decision_guidance.xml Normal file
View File

@@ -0,0 +1,65 @@
<decision_guidance>
# LX Designer Decision Guidance
## When to Use Each Skill
### journey-mapper
- **Use when:** Designing new learning experiences
- **Use when:** Analyzing existing learner flows
- **Skip when:** Journey has already been mapped and validated
### engagement-analyzer
- **Use when:** Reviewing engagement metrics
- **Use when:** Identifying drop-off points
- **Skip when:** No engagement data is available
### gamification-designer
- **Use when:** Adding engagement mechanics
- **Use when:** Designing badge or point systems
- **Skip when:** Content is formal or gamification is inappropriate
### microlearning-architect
- **Use when:** Structuring content for microlearning
- **Use when:** Designing spaced repetition schedules
- **Skip when:** Content is designed for long-form delivery
### ui-spec-generator
- **Use when:** Specifying UI components for developers
- **Use when:** Creating design specifications
- **Skip when:** UI is handled by existing design system
## Design Decisions
### Engagement Level
- **High gamification:** Badges, points, leaderboards, challenges
- Best for: K-12, casual learning, engagement-focused
- **Medium gamification:** Progress bars, completion certificates
- Best for: Professional development, higher education
- **Low gamification:** Minimal game elements, focus on content
- Best for: Academic, compliance, formal training
### Journey Structure
- **Linear:** Fixed sequence for all learners
- Best for: Foundational knowledge, regulated content
- **Adaptive:** Sequence adjusts based on performance
- Best for: Varied learner backgrounds, competency-based
- **Choice-based:** Learners select their own path
- Best for: Self-directed, experienced learners
### Microlearning Unit Size
- **Very short (2-5 minutes):** Single concept, quick practice
- Best for: Mobile learning, just-in-time training
- **Short (5-10 minutes):** Concept + example + practice
- Best for: Standard microlearning, most contexts
- **Medium (10-15 minutes):** Deeper exploration with multiple activities
- Best for: Complex topics, desktop learning
## Trade-offs to Consider
| Decision | Benefit | Cost |
|----------|---------|------|
| More gamification | Higher engagement | Development complexity, potential distraction |
| Adaptive journey | Personalized experience | Complex logic, more content needed |
| Smaller units | Easier to complete | More units to manage, potential fragmentation |
| Choice-based | Learner autonomy | Harder to ensure coverage, complex tracking |
</decision_guidance>

114
modes/lx-designer/rules/5_examples.xml Normal file
View File

@@ -0,0 +1,114 @@
<examples>
# LX Designer Examples
## Example 1: Learner Journey Map
```markdown
# Journey Map: Introduction to Programming
## Entry Point
- **Learner Profile:** Beginner, no programming experience
- **Entry Assessment:** 5-question diagnostic quiz
- **Placement:** All learners start at Module 1
## Module Sequence
1. **What is Programming?** (10 min)
- Video: 3 min
- Interactive: Drag-and-drop code blocks (2 min)
- Check: 2-question quiz
2. **Variables and Data Types** (15 min)
- Explanation: 5 min
- Practice: Code editor exercise (5 min)
- Check: 3-question quiz
3. **Control Flow** (20 min)
- Explanation: 5 min
- Interactive: Flowchart builder (5 min)
- Practice: Write if/else statements (5 min)
- Check: 4-question quiz
## Decision Points
- After Module 2: Score < 60% → Review Module 2 with additional practice
- After Module 2: Score >= 60% → Continue to Module 3
## Milestones
- Complete Module 1: "First Steps" badge
- Complete Module 2: "Data Handler" badge
- Complete Module 3: "Logic Master" badge
- Complete all modules: Certificate of completion
## Exit
- Final project: Build a simple calculator
- Peer review + self-reflection
- Certificate awarded
```
---
## Example 2: Gamification Specification
```markdown
# Gamification Design: Science Explorer
## Badge System
| Badge | Criteria | Type |
|-------|----------|------|
| Curious Mind | Complete first module | Participation |
| Lab Assistant | Score 80%+ on 3 quizzes | Achievement |
| Scientist | Complete all modules | Completion |
| Master Researcher | Score 90%+ on final project | Mastery |
## Point System
- Complete lesson: 10 points
- Pass quiz: 20 points
- Perfect quiz score: 30 points
- Help peer (forum): 5 points
- Daily login streak: 2 points/day (max 14/week)
## Progression
- Level 1: 0-50 points (Explorer)
- Level 2: 51-150 points (Investigator)
- Level 3: 151-300 points (Researcher)
- Level 4: 301+ points (Scientist)
## Leaderboard
- Weekly leaderboard (resets each week)
- Top 3 receive bonus badges
- Opt-in only (privacy consideration)
```
---
## Example 3: UI Specification
```markdown
# UI Spec: Course Navigation
## Components
### Progress Bar
- Location: Top of page, below header
- Height: 8px
- Color: Primary brand color (#007BFF)
- States: Not started (gray), In progress (blue), Complete (green)
- Text: "Module 3 of 8 - 37% complete"
### Module Card
- Layout: Grid, 3 columns (desktop), 1 column (mobile)
- Content: Title, description, estimated time, status icon
- Hover: Slight elevation, cursor pointer
- Click: Navigate to module
### Navigation Buttons
- Previous: Left-aligned, disabled on first module
- Next: Right-aligned, disabled until current module complete
- Skip: Available if learner has demonstrated mastery
### Feedback Toast
- Position: Bottom-right corner
- Duration: 3 seconds
- Types: Success (green), Error (red), Info (blue)
- Dismissible: Yes
```
</examples>

63
modes/lx-designer/rules/6_error_handling.xml Normal file
View File

@@ -0,0 +1,63 @@
<error_handling>
# LX Designer Error Handling
## Common Errors and Responses
### Error: Journey Dead End Detected
**Symptom:** Learner path leads to a point with no continuation
**Response:**
1. Identify the dead-end node in journey map
2. Suggest continuation or branching options
3. Ensure all paths lead to meaningful outcomes
4. Add fallback paths for struggling learners
### Error: Engagement Drop-Off Point
**Symptom:** Significant learner attrition at specific point
**Response:**
1. Identify the module or activity with high drop-off
2. Analyze potential causes (length, difficulty, engagement)
3. Suggest interventions (break content, add interaction, adjust difficulty)
4. Recommend A/B testing for solutions
### Error: Cognitive Overload
**Symptom:** Too much information presented at once
**Response:**
1. Identify overloaded sections
2. Suggest content chunking
3. Recommend spacing activities over time
4. Apply microlearning principles
### Error: Gamification Misalignment
**Symptom:** Game elements distract from or conflict with learning objectives
**Response:**
1. Identify misaligned game elements
2. Suggest alternatives that support learning
3. Ensure rewards are tied to learning achievements
4. Remove elements that create extrinsic motivation conflicts
### Error: File Permission Violation
**Symptom:** Attempting to edit files outside allowed directories
**Response:**
1. Identify the restricted file path
2. Explain the permission boundary
3. Suggest correct file location within `design/` or `ux/`
4. Offer to create properly located file
## Escalation Procedures
### When to Escalate to Human Review
- Journey design requires stakeholder approval
- Engagement data suggests fundamental course redesign
- Gamification strategy conflicts with organizational brand
- UI specifications require design system changes
### Escalation Format
```markdown
## Escalation: [Issue Type]
**Context:** [Brief description]
**Impact:** [What is affected]
**Options:** [Possible approaches]
**Recommendation:** [Preferred approach with rationale]
**Requires:** [What human input is needed]
```
</error_handling>

58
modes/lx-designer/rules/7_communication.xml Normal file
View File

@@ -0,0 +1,58 @@
<communication>
# LX Designer Communication Guidelines
## Handoff from Curriculum Designer
When receiving curriculum from the Curriculum Designer mode:
1. **Review Curriculum Package**
- Learning objectives and module structure
- Assessment points and requirements
- Target audience information
- Technical constraints
2. **Experience Planning**
- Map learner journey through curriculum
- Identify engagement opportunities
- Note areas requiring special UX consideration
## Handoff to Content Producer
When passing design specifications to Content Producer mode:
1. **Design Package**
- Journey maps and flow diagrams
- Interactive element specifications
- UI component requirements
- Engagement mechanic specifications
2. **Production Notes**
- Priority ranking for interactive elements
- Technical requirements for interactions
- Platform and device considerations
- Accessibility requirements
## Communication with Accessibility Auditor
When passing designs for accessibility review:
1. **Design Package**
- Journey maps and user flows
- UI specifications
- Interactive element designs
- Engagement mechanics
2. **Accessibility Considerations**
- Note any potential accessibility challenges
- Include alternative interaction paths
- Document keyboard navigation requirements
## Receiving Feedback
When receiving feedback from downstream modes:
1. Acknowledge receipt of feedback
2. Evaluate impact on design specifications
3. Document required changes
4. Communicate timeline impact to affected modes
</communication>