curriculum-design
Skill1 starsChanged 7 months agoMITView on GitHub
Design curricula with scope and sequence, learning progressions, standards alignment, and assessment strategy. Trigger with "design a curriculum for", "create a course outline", "build a syllabus", "scope and sequence for", "plan a unit on", or when the user needs to structure a multi-lesson or multi-unit learning experience.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
- cheyuriy/codelabgentheir own version, first seen Oct 25, 2026
- renky1025/agent-skillstheir own version, first seen Sep 25, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- renky1025/agent-skills★ 11same name
- cheyuriy/codelabgen★ 1same name
- KMaruthi2002/universal-llm-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- incident-responseSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 42
Ask about prerequisites: what should learners already know coming in?
- Distinctive: line 44
Ask about existing curriculum: is this a new course or a revision of something in place?
- Distinctive: line 51
Write 5-8 course-level learning outcomes using measurable verbs (Bloom's Taxonomy).
- Distinctive: line 52
Ensure outcomes span cognitive levels: knowledge, comprehension, application, analysis, evaluation, and creation.
- Distinctive: line 55
Verify that outcomes are achievable within the course duration.
- Distinctive: line 71
Place cumulative assessments at natural break points.
- Distinctive: line 98
Create rubrics for major assessments with clearly defined performance levels.
- Distinctive: line 103
Ensure the curriculum serves all learners:
- Distinctive: line 109
Ensure materials are accessible (screen-reader compatible, captioned, etc.).
- Distinctive: line 176
Every unit should answer a compelling essential question that connects content to relevance.
- Distinctive: line 182
If working from existing materials, note what to keep, revise, and replace rather than starting from scratch.
- Distinctive: line 183
Ask the user about their philosophy of education (direct instruction, constructivist, inquiry-based) to align the design approach.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Curriculum Design
Design structured curricula with scope and sequence, learning progressions, standards alignment, assessment strategies, and instructional resources. Covers full courses, unit plans, and multi-week learning programs.
Workflow
Step 1: Needs Analysis
Gather the parameters that shape the curriculum:
- Confirm the subject, course level, and target audience.
- Determine the course duration and meeting frequency (daily, 2x/week, etc.).
- Identify required standards, competencies, or learning outcomes to address.
- Ask about prerequisites: what should learners already know coming in?
- Understand constraints: available technology, materials, budget, and co-curricular time.
- Ask about existing curriculum: is this a new course or a revision of something in place?
- Identify the end goal: what should a learner be able to do upon completion?
Step 2: Define Learning Outcomes
Establish the course-level outcomes that all units serve:
- Write 5-8 course-level learning outcomes using measurable verbs (Bloom's Taxonomy).
- Ensure outcomes span cognitive levels: knowledge, comprehension, application, analysis, evaluation, and creation.
- Map each outcome to relevant standards (if applicable).
- Distinguish between essential outcomes (must achieve) and enrichment outcomes (aspirational).
- Verify that outcomes are achievable within the course duration.
Step 3: Build Scope and Sequence
Organize content into a logical learning progression:
Scope: What content and skills the course covers.
- List all topics and subtopics to be taught.
- Group related topics into units (4-8 units for a semester, 8-12 for a year).
- Identify dependencies: which topics must precede others.
- Note topics that spiral (revisited at increasing depth throughout the course).
Sequence: The order in which content is taught.
- Arrange units from foundational to complex, concrete to abstract.
- Front-load prerequisite skills needed for later units.
- Alternate between skill-heavy and content-heavy units for pacing.
- Place cumulative assessments at natural break points.
- Build in review and buffer weeks (at least 1 per quarter).
Step 4: Design Unit Plans
Flesh out each unit with structure and assessments:
For each unit, define:
- Unit title and essential question: An overarching question the unit answers.
- Duration: Number of class periods or weeks.
- Learning objectives: 3-5 measurable objectives per unit, derived from course outcomes.
- Key vocabulary and concepts: Terms students must master.
- Lesson sequence: Day-by-day or topic-by-topic breakdown.
- Activities and resources: Readings, labs, projects, discussions, and technology tools.
- Assessment plan:
- Formative: Checks for understanding during the unit (quizzes, exit tickets, drafts).
- Summative: End-of-unit assessment (test, project, presentation, portfolio piece).
Step 5: Plan Assessment Strategy
Design a coherent assessment system across the course:
- Diagnostic assessments: Pre-assessments at the start of the course and each unit.
- Formative assessments: Ongoing checks (at least 2-3 per unit) to inform instruction.
- Summative assessments: End-of-unit evaluations that measure mastery of objectives.
- Culminating assessment: Final project, exam, or portfolio that integrates course-level outcomes.
- Define grading criteria and weight distribution (e.g., 40% assessments, 30% projects, 20% participation, 10% homework).
- Create rubrics for major assessments with clearly defined performance levels.
- Plan for reassessment or mastery-based grading if applicable.
Step 6: Address Differentiation and Inclusion
Ensure the curriculum serves all learners:
- Identify points where scaffolding is needed for struggling learners.
- Plan extension opportunities for advanced learners.
- Note where UDL (Universal Design for Learning) principles apply: multiple means of engagement, representation, and action/expression.
- Include culturally responsive content that reflects diverse perspectives.
- Ensure materials are accessible (screen-reader compatible, captioned, etc.).
Output Format
# Curriculum: [Course Title]
**Subject**: [Subject] | **Level**: [Grade/Audience]
**Duration**: [Semester/Year/Weeks] | **Meeting frequency**: [X times/week, Y min each]
**Standards**: [Framework]
## Course Overview
[2-3 paragraph description of the course purpose, approach, and end goals]
## Course Learning Outcomes
1. [Outcome 1] — Standards: [codes]
2. [Outcome 2] — Standards: [codes]
3. [Outcome 3] — Standards: [codes]
[...]
## Scope and Sequence
| Unit | Title | Duration | Essential Question | Key Assessments |
|------|-------|----------|-------------------|-----------------|
| 1 | [Title] | [X weeks] | [Question] | [Assessment type] |
| 2 | [Title] | [X weeks] | [Question] | [Assessment type] |
[...]
## Unit Plans
### Unit 1: [Title]
**Duration**: [X weeks / Y class periods]
**Essential question**: [Overarching question]
**Objectives**: [SWBAT statements]
**Lesson sequence**:
1. [Day/Topic 1]: [Activity and content]
2. [Day/Topic 2]: [Activity and content]
[...]
**Formative assessments**: [List]
**Summative assessment**: [Description + rubric summary]
**Differentiation**: [Scaffolds and extensions]
[Repeat for each unit]
## Assessment Strategy
- **Grading breakdown**: [Categories and weights]
- **Culminating assessment**: [Description]
- **Reassessment policy**: [If applicable]
## Required Materials and Resources
- [Textbooks, software, lab equipment, etc.]Examples
User: "Design a semester-long AP Computer Science A curriculum" Action: Build 8 units covering Java fundamentals through OOP and algorithms, align to College Board AP CSA framework, include labs, code reviews, and AP-style practice exams.
User: "Create a 6-week professional development course on data literacy for teachers" Action: Design 6 weekly modules progressing from reading data to making instructional decisions, include hands-on activities with real school data, plan peer collaboration tasks.
User: "Plan a year-long 3rd grade science curriculum aligned to NGSS" Action: Organize by NGSS disciplinary core ideas, interleave engineering practices, build scope and sequence with seasonal science connections, include hands-on investigations.
Best Practices
- Design backwards: start with end-of-course goals, then units, then lessons.
- Every unit should answer a compelling essential question that connects content to relevance.
- Build in flexibility: plan for 85% of available time, leaving room for reteaching and student interests.
- Spiral key skills across multiple units rather than teaching in isolation.
- Align assessments directly to learning outcomes — if it is assessed, it must be taught, and vice versa.
- Include at least one project-based or performance-based assessment per quarter.
- Review the sequence for cognitive load: avoid clustering the hardest topics together.
- If working from existing materials, note what to keep, revise, and replace rather than starting from scratch.
- Ask the user about their philosophy of education (direct instruction, constructivist, inquiry-based) to align the design approach.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

