SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsstudy-summary

study-summary

General & other

View repository

Updated 10-15 22:38

About this skill

study-summary - Learning Notes Generator

Learning notes generator with two modes: (skill that supports two modes)

  • Classic: concise recap for quick review
  • Mastery: detailed record with rules, misconceptions, and seed code history

Instructions

Terminology Policy (beginner-friendly terminology rules)

Use Korean-first wording in the note where possible, and keep English terms in parentheses when needed. (Write the note body in Korean first whenever possible, and when necessary, include English terms in parentheses.)

If a technical term appears for the first time in the note, add a one-line plain explanation. (When a technical term appears for the first time, add a one-line easy explanation.)

Examples: (Examples)

  • 격리 경계 (isolation boundary): actor 외부에서 내부 상태를 직접 바꾸지 못하게 하는 경계
  • 경합 상태 (data race): 동시에 같은 값을 바꿔서 결과가 꼬이는 문제

Step 0: Language Selection

Ask the user to choose a language at the start using a selection flow, not free-form text input. (At skill start, the language is received not as free-form input but as selection-based method)

  • Korean - Write the note in Korean
  • English - Write notes in English

Use platform-specific selection behavior:

  • Codex CLI: use native option selection (request_user_input with 2 options) when available. If unavailable, show numbered choices and ask for 1 or 2.
  • Claude Code: use native option selection UI when available. If unavailable, show numbered choices.
  • Gemini CLI: use native option selection UI when available. If unavailable, show numbered choices.

Choice mapping: 1 → Korean, 2 → English

Use the selected language for the note content and all communication. Code and Swift keywords stay in English. (Proceed with the note content and communication in the selected language. Code and Swift keywords remain in English.)

Study Mode Selection

Ask the user to choose a study mode using the same selection pattern: (Have them choose a study mode using the same selection method)

  • Classic (explanation-focused, recommended)

    • Suitable when you want concise notes focused on core concepts
    • Organized in a form that allows quick review
    • Good for lightly recording a topic you are learning for the first time

  • Mastery (training-focused)

    • Records in detail the learner's rules/mistakes/confusion points
    • Leaves the Core Loop seed code and gate results, which is advantageous for relearning
    • Suitable for tracking weaknesses and linking to the next session

Choice mapping: (Choice value mapping)

  • 1 -> Classic
  • 2 -> Mastery

Prompt example: (Example prompt text)

  • Korean: "Please select a study note mode. Answer with a number.\n\n1) Classic (explanation-focused, recommended)\n- Concise organization focused on key points\n- Suitable for quick review\n\n2) Mastery (training-focused)\n- Detailed recording including rules/confusion points/seed code\n- Suitable for linked learning in the next session"
  • English: "Choose a notes mode (reply with a number):\n\n1) Classic (Explanation-first, Recommended)\n- Concise notes focused on core points\n- Best for quick review\n\n2) Mastery (Practice-first)\n- Detailed notes with rules, confusion points, and seed code history\n- Best for follow-up training"

After selection, briefly confirm mode and continue. (Immediately after selection, briefly confirm the mode and proceed.)

Step 1: Analyze Conversation

Scan the current conversation to identify: (Scan the current conversation to identify the following)

If the conversation used the Core Loop format (Phase 1-3): (If it was a Core Loop format conversation)

  • Mystery Hook code and the learner's initial prediction
  • Each SEED code from the Core Loop cycles
  • 예측하기 (PREDICT) Result: which answers passed/needed improvement
  • 해설하기 (REVEAL) content and ASCII diagram
  • 한 줄 정리 (RESTATE)the sentence organized by the learner in
  • Anchor output: the learner's "if X, then Y" rules
  • Anchor output: the learner's stated misconception/confusion
  • Sources cited (SE proposals, WWDC, Apple docs)

If the conversation used the old format or free-form discussion: (If it was the previous format or free discussion)

  • Topics covered
  • Key concepts explained
  • Code examples shown
  • Questions asked and answers given
  • Areas where the learner struggled or excelled

Step 2: Confirm Topics

Use AskUserQuestion to confirm what to include: (Confirm what to include with AskUserQuestion)

  • Everything / Everything - Summarize all content learned in this conversation / Summarize all topics
  • Last topic only / Last topic only - Summarize only the most recently covered topic / Only the most recent topic

Step 3: Generate Note

Create a Markdown note. Use the appropriate structure based on what was found in Step 1. (Create a Markdown note. Use the appropriate structure based on what was identified in Step 1.)

File path: notes/YYYY-MM-DD-<topic-in-english>.md

Template branching criteria (Mode routing): (Template routing by mode)

  • Mastery mode: use the Core Loop detailed template below.
  • Classic mode: use the concise template below unless the user explicitly asks for detailed Core Loop format.

Mastery template (Core Loop detailed): (Mastery template: Core Loop detailed type)

# <Topic>

> Date: YYYY-MM-DD

## My Rules (from Anchor)

1. if X, then Y
2. if X, then Y
3. if X, then Y

## Where I Got Confused

- (learner's own description from Anchor phase)

## Key Mechanisms

(해설하기(REVEAL) 단계에서 사용한 ASCII 다이어그램과 쉬운 설명)

## Seed Codes (for review)

### Cycle 1 (easy)

```swift
// seed code from cycle 1

Answer: ...

Cycle 2 (medium)

// seed code from cycle 2

Answer: ...

Cycle 3 (hard)

// seed code from cycle 3

Answer: ...

Sources

  • SE-XXXX: ...
  • WWDC session: ...
  • Apple docs: ...

Review Questions

  1. (generated from the session's key concepts)
  2. ...
  3. ...

Generated by /study-summary


**Classic template (concise recap):**
(Classic 템플릿: 간결 요약형)

```markdown
# <Topic>

> Date: YYYY-MM-DD

## Key Concepts

1. **Concept 1**: one-line explanation
2. **Concept 2**: one-line explanation
3. **Concept 3**: one-line explanation

## Code Examples

```swift
// key code examples from the session

Summary

(3-5 lines summarizing the core content)

Review Questions

  1. ...
  2. ...
  3. ...

Generated by /study-summary


### Step 4: Save Note

Use the Write tool to save the note to the `notes/` directory.
(Write tool을 사용하여 `notes/` 디렉토리에 노트를 저장한다.)

### Step 5: Update Learning Progress

Record learning progress in memory using `mcp__plugin_everything-claude-code-ios_memory__add_observations` (or `create_entities` if the entity doesn't exist yet):
(memory에 학습 진도를 기록한다)

Entity: `SwiftLearningProgress`

**If mode is Mastery (or detailed Core Loop template used):**
(Mastery 모드이거나 Core Loop 상세 템플릿을 사용했으면)

Observations:

  • "YYYY-MM-DD: completed (<level: beginner/intermediate/advanced>)"
  • "YYYY-MM-DD: misconception: "
  • "YYYY-MM-DD: gates: cycle1 <pass/supplement>, cycle2 <pass/supplement>, cycle3 <pass/supplement>"

**If mode is Classic (concise template used):**
(Classic 모드의 간결 템플릿을 사용했으면)

Observations:

  • "YYYY-MM-DD: completed ()"
  • "YYYY-MM-DD: weak area: "

### Step 6: Wrap Up

After saving, inform the user:
(저장 완료 후 안내)

Notes saved: notes/YYYY-MM-DD-.md

Progress recorded:

  • Completed: ()
  • Misconception tracked:

Continue learning with /swift-study, or review with /swift-quiz.


### Rules

1. **Use the selected language** - from Step 0. Code in English. (선택한 언어로 작성)
2. **Apply mode consistently** - Classic = concise recap, Mastery = detailed training artifacts (모드 일관성 유지)
3. **Prioritize learner's own words** - Anchor rules and misconceptions should be quoted from the learner, not rewritten. (학습자 본인의 표현을 우선한다)
4. **Include seed codes in Mastery** - preserve cycle code snippets for later review. (Mastery에서는 seed 코드 포함)
5. **Specific misconception tracking** - not "weak area: concurrency" but "misconception: thought state preserved across await". (구체적인 misconception 기록)
6. **Review questions required** - at least 3 self-check questions. (복습 질문 최소 3개)
7. **Progress tracking required** - always save to memory. (진도 기록 필수)
8. **Graceful fallback** - work with old-format sessions too. (이전 형식 세션도 지원)
9. **No emojis** - clean Markdown only. (이모지 사용 금지)