As every discipline has different approaches to accessibility, universal learning design, and AI policies, this week is an opportunity to both build your literacy with Claude Code and think through the pragmatic implications of this work for your own courses and discipline.

There is no in-person meeting.

Asynchronous deep-dive. All three exercise options this week run in Claude Code — continue in Claude Code Desktop with the Superpowers plugin from W9, or use Claude Code Web if you prefer the browser. Pick one option; the syllabus-facing ones are the most consequential use of this week if you are revising for fall.

The Discipline-Specific Question

A psychology class’s AI policy and a creative-writing class’s AI policy are not the same document. A studio art seminar and a quantitative-methods course don’t have the same accessibility frame. The W9 workshop laid out shared axes (copyright, attribution, accessibility, equity, labor, UDL); this week is for adapting those axes to your discipline, your course size, your institutional context, your students’ likely backgrounds.

Three questions worth holding open as you work through the menu:

1. What might playful and creative approaches to agentic AI enable in your discipline? What assignments are traditional — the e-portfolio, making games or simulations, data analysis — that AI naturally fits or transforms?
2. What is appropriate documentation for AI usage in your discipline? Is there a place for formal citation (as UCF currently advises) — or is AI more likely to be present as a method or an object of study? What guidance will you give students in that usage?
3. How does AI fit into UDL approaches in your discipline? Think about some of the cases we’ve discussed — voice to text, generating alt text — and where that might fit both into your own practice and your policy.

Reading Menu

• Light Locke, Brandon. “Digital Humanities Pedagogy as Essential Liberal Education.” DHQ 11.3 (2017). (~30 min) The case for DH pedagogy as core liberal-arts work.
• Light Mollick, Ethan. “The Future of Education in a World of AI.” One Useful Thing. (~20 min) Useful for stress-testing your draft policy.
• Light Benjamin, Ruha. “The New Artificial Intelligentsia.” Los Angeles Review of Books, October 18, 2024. (~25 min) Required reading for the equity-of-access section.
• Standard Costanza-Chock, Design Justice, Chapter 1. (~75 min) Open access. Foundational text for the UDL/equity framing.
• Standard CAST. “UDL Guidelines.” The authoritative reference. Skim the three principles and the new (2024) updates.
• Standard Look up your disciplinary association’s current AI statement — MLA, AHA, AAA, ACRL, NCA, MAA, APA, ASA, etc. Most have published one in the last 18 months. Read your own and one neighbor’s.

Exercise Menu

Pick one. All three run in Claude Code — the point of the week is putting the agentic workflow from W9 to work on your own course materials.

• Light Syllabus review + policy research (~60 min). Give Claude Code your proposed or current syllabus and ask it to review it and suggest an AI policy. Have it research existing policies in your field, then compare: how does Claude frame AI usage versus how your discipline currently, generally frames it? If you already have a proposed AI policy written (your W9 Part B draft counts), give it to Claude for critique and comparison.
• Standard Teaching portfolio on GitHub Pages (~90 min). Use Claude Code to build a teaching portfolio: give it your old and current syllabi, assignments, or other materials you have control of, and ask it to build a showcase suitable for job applications while preserving all the content. Drop everything into the repository — the format is irrelevant; Claude will sort it out — and use GitHub Pages to host the result.
• Deep Course-updating tool via the Webcourses API (~3 hr). Take your old class materials or your fall syllabus, generate an API access token through Webcourses (Account → Settings → New Access Token), and ask Claude to build a tool that makes updates for you — aesthetics, accessibility, course dates, checking for broken links, and so on. Be specific about how you want your modules and assignments to work, and try to use Superpowers and planning mode in Claude Code Desktop.

What to Carry Into Workshop 6

• Bring everything you’ve built across the series: your W7 ePortfolio URL, your W9 playful tool URL, your draft AI policy, your Skill from W4 (if you built one), your image gallery from W5.
• If you have your own laptop, consider installing the Claude Code CLI — or at least Claude Code Desktop — and Ollama if you are interested in following along with the demos.
• Make an account on Hugging Face if you want to try fine-tuning or playing with models.
• Workshop 6 is a tour, not a tutorial — but the demos will pull from your artifacts where useful. Have them findable.

Cross-references

• Source materials: CriticalMaking2026/index (UDL + accessibility threading); CAST UDL Guidelines; your disciplinary association’s current AI statement.