Training

2-Session Morning Schedule Detail

2-Session Full Day Schedule Detail

3-Session Schedule Detail

Guide Structure

The guide follows the template in references/template_guide.md:

1. Header — DNN, title, professor, format, schedule
2. Objective — Context, what they'll learn, why it matters
3. Sessions — Theory blocks with code examples and explanations
4. Autonomous work — Exercises with criteria (not just mechanical tasks)
5. Summary table — Concept / When to use / Key implementation detail

Guide-to-PPTX Mapping

PPTX Color Rules

When generating slides, follow the s2-docs:pptx color guidelines strictly:

• Agenda slides: All session and autonomous work cards use BLUE accent. Never green.
• Theory cards: Default to BLUE. Use AMBER for a second color if needed.
• Before/After code comparisons: This is the only context where RED/GREEN accents are appropriate.
• Objective text: Use BLUE or TEXT color, never red or green.

The primary palette is blue + yellow/amber. Red and green are reserved exclusively for good/bad comparisons.

Content Rules

1. Code must always be commented — every example needs inline explanations
2. Exercises require design criteria — not just "implement X", but "decide how and justify"
3. Summary table is mandatory — concept / when to use / key detail
4. Integrating exercise — final exercise uses a different domain than the session examples
5. Reflection questions — at least one per autonomous work block (written as code comment)
6. Exercise sizing must match available time — see rules below

Exercise Sizing Rules

Exercises must be realistic for the time slot they occupy. Calculate available time from the schedule and size accordingly.

Sizing guidelines

• Between-session exercises: Estimate 30-45 min of effective coding per task. A 1.5h gap means 2 tasks max. Include the reflection question time. Students also need time to read, think, and re-read session material.
• End-of-day exercises: No time cap. These are the integrating exercises where students apply the full day's learning. Can span multiple classes, require architectural decisions, and use a different domain.
• Always state estimated time per task — add (~30 min) or (~45 min) next to each task name so students can self-pace.
• If a format has no afternoon session (e.g., 2 sessions morning), the last autonomous work block after session 2 is the end-of-day block and should be sized accordingly.

Exercise Repository Integration

When the user requests an exercise repository as part of the training, the exercises from the guide's autonomous work blocks become start/solution branch pairs:

Process

1. Generate the guide first — exercises are extracted from its autonomous work blocks
2. Load the appropriate exercise-repo skill (exercise-repo-back or exercise-repo-front)
3. Propose plan and wait for professor approval before writing any code
4. Generate main + start/* + solution/* branches following the skill's conventions
5. Ensure time estimates and exercise scope are consistent between guide and repo

Available exercise-repo skills

Dependencies

• Skill s2-docs:pptx — for PPTX generation pipeline
• Skill s2-docs:branding — for corporate identity reference
• Skill s2-docs:exercise-repo-back — for Git repository structure with start/solution branches per backend exercise (Java/Spring Boot, follows s2-backend conventions)
• Skill s2-docs:exercise-repo-front — (not yet available) for frontend exercise repos

File Structure

training/
├── SKILL.md                    ← this file
└── references/
    └── template_guide.md       ← markdown template with placeholders