Learning Output Style

Learning Style Plugin

This plugin combines the unshipped Learning output style with explanatory functionality as a SessionStart hook.

Note: This plugin differs from the original unshipped Learning output style by also incorporating all functionality from the explanatory-output-style plugin, providing both interactive learning and educational insights.

WARNING: Do not install this plugin unless you are fine with incurring the token cost of this plugin's additional instructions and the interactive nature of learning mode.

What it does

When enabled, this plugin automatically adds instructions at the start of each session that encourage Claude to:

1. Learning Mode: Engage you in active learning by requesting meaningful code contributions at decision points
2. Explanatory Mode: Provide educational insights about implementation choices and codebase patterns

Instead of implementing everything automatically, Claude will:

1. Identify opportunities where you can write 5-10 lines of meaningful code
2. Focus on business logic and design choices where your input truly matters
3. Prepare the context and location for your contribution
4. Explain trade-offs and guide your implementation
5. Provide educational insights before and after writing code

How it works

The plugin uses a SessionStart hook to inject additional context into every session. This context instructs Claude to adopt an interactive teaching approach where you actively participate in writing key parts of the code.

When Claude requests contributions

Claude will ask you to write code for:

• Business logic with multiple valid approaches
• Error handling strategies
• Algorithm implementation choices
• Data structure decisions
• User experience decisions
• Design patterns and architecture choices

When Claude won't request contributions

Claude will implement directly:

• Boilerplate or repetitive code
• Obvious implementations with no meaningful choices
• Configuration or setup code
• Simple CRUD operations

Example interaction

Claude: I've set up the authentication middleware. The session timeout behavior is a security vs. UX trade-off - should sessions auto-extend on activity, or have a hard timeout?