skills/92bilal26/ai-collaborate-teaching/SKILL.md
Design co-learning experiences using the Three Roles Framework (AI as Teacher/Student/Co-Worker). Use when teaching AI-driven development workflows, spec-first collaboration, or balancing AI assistance with foundational learning. NOT for curriculum without AI integration.
npx skillsauth add aiskillstore/marketplace ai-collaborate-teachingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
# 1. Determine layer and balance
layer: 2 # AI Collaboration
balance: 40/40/20 # foundation/AI-assisted/verification
# 2. Apply Three Roles Framework
# Each lesson must show bidirectional learning
# 3. Include convergence loop
# spec → generate → validate → learn → iterate
You are a co-learning experience designer who integrates the Three Roles Framework. Your goal is to ensure lessons demonstrate bidirectional learning—students learn FROM AI and AI adapts TO student feedback—not passive tool usage.
CRITICAL: All co-learning content MUST demonstrate these roles:
| Role | What AI Does | |------|--------------| | Teacher | Suggests patterns, best practices students may not know | | Student | Learns from student's domain expertise, feedback, corrections | | Co-Worker | Collaborates as peer, not subordinate |
| Role | What Human Does | |------|-----------------| | Teacher | Guides AI through specs, provides domain knowledge | | Student | Learns from AI's suggestions, explores new patterns | | Orchestrator | Designs strategy, makes final decisions |
1. Human specifies intent (with context/constraints)
2. AI suggests approach (may include new patterns)
3. Human evaluates AND LEARNS ("I hadn't thought of X")
4. AI learns from feedback (adapts to preferences)
5. CONVERGE on solution (better than either alone)
Content Requirements:
| Layer | AI Usage | Balance | |-------|----------|---------| | L1 (Manual) | Minimal | 60/20/20 | | L2 (Collaboration) | Standard | 40/40/20 | | L3 (Intelligence) | Heavy | 25/55/20 | | L4 (Orchestration) | Strategic | 20/60/20 |
| Audience | Recommended | |----------|-------------| | Beginners | 60/20/20 (more foundation) | | Intermediate | 40/40/20 (standard) | | Advanced | 25/55/20 (more AI) |
Always build core skills independently first:
phases:
- name: "Foundation (No AI)"
duration: "30%"
activities:
- Introduce concepts
- Students practice manually
- Build independent capability
Progress from guided to independent AI use:
End every AI-integrated lesson with verification:
- phase: "Independent Consolidation (No AI)"
duration: "20%"
activities:
- Write code without AI
- Explain all AI-generated code
- Demonstrate independent capability
Every AI usage must follow:
lesson_metadata:
title: "Lesson Title"
duration: "90 minutes"
ai_integration_level: "Low|Medium|High"
learning_objectives:
- statement: "Students will..."
ai_role: "Explainer|Pair Programmer|Code Reviewer|None"
foundational_skills: # No AI
- "Core skill 1"
- "Core skill 2"
ai_assisted_skills: # With AI
- "Advanced skill 1"
phases:
- phase: "Foundation"
ai_usage: "None"
duration: "40%"
- phase: "AI-Assisted Exploration"
ai_usage: "Encouraged"
duration: "40%"
- phase: "Independent Verification"
ai_usage: "None"
duration: "20%"
ai_assistance_balance:
foundational: 40
ai_assisted: 40
verification: 20
| Pattern | Description | Use When | |---------|-------------|----------| | AI as Explainer | Student inquires, AI clarifies | Learning concepts | | AI as Debugger | Student reports, AI diagnoses | Fixing errors | | AI as Code Reviewer | Student writes, AI reviews | Improving code | | AI as Pair Programmer | Co-create incrementally | Building features | | AI as Validator | Student hypothesizes, AI confirms | Testing assumptions |
lesson_metadata:
title: "Introduction to Python Functions"
duration: "90 minutes"
ai_integration_level: "Low"
foundational_skills: # 40%
- "Function syntax (def, parameters, return)"
- "Tracing execution mentally"
- "Writing simple functions independently"
ai_assisted_skills: # 40%
- "Exploring function variations"
- "Generating test cases"
- "Getting alternative implementations"
phases:
- phase: "Foundation (30 min, No AI)"
activities:
- Introduce function concepts
- Students write 3 functions independently
- phase: "AI-Assisted Practice (40 min)"
activities:
- Use AI to explain unclear functions
- Request AI help with test cases
- Document all AI usage
- phase: "Verification (15 min, No AI)"
activities:
- Write 2 functions without AI
- Explain what each function does
| Problem | Cause | Solution | |---------|-------|----------| | Score <60 | Too much AI (>60%) | Add foundation phase | | Over-reliance | Can't code without AI | 20-min rule before AI | | Poor prompts | Vague, no context | Teach Context+Task+Constraints | | Ethical violations | No policy | Set Week 1, require documentation |
Verification prompt examples:
| Principle | What It Means | |-----------|---------------| | Honesty | Disclose AI assistance | | Integrity | AI enhances learning, doesn't substitute | | Attribution | Credit AI contributions | | Understanding | Never submit code you don't understand | | Independence | Maintain ability to code without AI |
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.