@mohammadhprp/system-prompt 0.12.1 → 0.12.3

package/framework/skills/great-interface/references/variable-fonts-and-opentype.md

@@ -1,105 +0,0 @@
-# Variable fonts and OpenType
-
-What a font file can do beyond drawing letters and how to reach those abilities from CSS.
-
-## Static vs variable
-
-- **Static font:** one weight and one style per file. Regular, medium and bold is three files.
-- **Variable font:** a whole range in one file. Any value in it works, such as `font-weight: 589`.
-
-A variable font is not automatically better. At one or two weights, static files can be smaller. At several weights, optical sizes, or custom axes, a variable font usually wins.
-
-## Load intended weights and styles
-
-Use a weight or style the active family does not provide and the browser may synthesize it, so load the faces the design uses. `none` disables weight, style, small-cap, superscript and subscript synthesis together and can erase distinctions when the real face is unavailable. Verify the whole fallback stack and every emphasis state before setting it.
-
-```css
-.brand-wordmark {
-  /* Safe only after this isolated treatment is verified */
-  font-synthesis: none;
-}
-```
-
-For body and interface text, keep synthesis enabled unless a verified font setup supplies every requested form. If only one mode is unwanted, use the specific longhand (`font-synthesis-weight`, `font-synthesis-style` and related properties) instead of the blanket shorthand.
-
-## Axes
-
-Variable-font controls, each with a four-letter tag. A font supports only the axes its designer included.
-
-| Axis | Tag | Controls |
-| --- | --- | --- |
-| Weight | `wght` | Stroke thickness (like `font-weight`) |
-| Optical size | `opsz` | Details and spacing tuned for the display size |
-| Width | `wdth` | Glyph width |
-| Slant | `slnt` | Slant angle |
-| Custom | e.g. `GRAD` (Roboto Flex) | Whatever the designer built |
-
-Inter's variable file exposes only `wght` and `opsz`.
-
-Optical sizes predate variable fonts, and many families still ship them as separate files. Heldane Text is sturdier and more spaced for reading sizes, Heldane Display finer for large ones.
-
-## Properties over axis tags
-
-When a property exists, use it. `font-weight` keeps working when a non-variable fallback renders, where `font-variation-settings` silently does nothing. Save raw tags for custom axes with no property of their own:
-
-```css
-/* Good: common axes use the properties */
-.heading {
-  font-weight: 650;
-  font-optical-sizing: auto;
-}
-
-/* Good: custom axis with no property of its own */
-.heading-grade {
-  font-variation-settings: "GRAD" 80;
-}
-
-/* Bad: weight via raw tag breaks on fallback fonts */
-.heading {
-  font-variation-settings: "wght" 650;
-}
-```
-
-## OpenType features
-
-OpenType is the standard behind almost every modern font. Features are extra built-in options and, unlike axes, work the same on static and variable fonts. A font ships only the features its designer included.
-
-| Tag | Feature |
-| --- | --- |
-| `tnum` | Tabular numbers: every digit the same width |
-| `zero` | Slashed zero: `0` distinct from `O` |
-| `liga` | Ligatures: joins pairs like "fi" into one shape |
-| `ss01`–`ss20` | Stylistic sets (numbered slots) |
-| `cv01`–`cv99` | Character variants (numbered slots) |
-
-Same rule as axes. Prefer the `font-variant-*` properties and reserve `font-feature-settings` for tags with no property:
-
-```css
-/* Good: common features use the properties */
-.price {
-  font-variant-numeric: tabular-nums;
-}
-
-/* Good: slashed zero via the property too */
-.id {
-  font-variant-numeric: slashed-zero;
-}
-
-/* Good: niche feature with no property of its own */
-.logo {
-  font-feature-settings: "ss01" 1;
-}
-```
-
-Tabular numbers matter for changing values. Without them each digit has a different width and the layout shifts as values update.
-
-## Small caps, superscripts, subscripts
-
-- **Small capitals:** uppercase letters drawn at a smaller size. Enable real ones with `font-variant-caps`.
-- **Superscripts** sit above the normal line, the 2 in x², and **subscripts** below it, as in H₂O. Enable proper glyphs with `font-variant-position`.
-
-Both require the font to include the glyphs.
-
-## Stylistic sets and character variants
-
-`ss01` = stylistic set, slot 01. `cv11` = character variant, slot 11. What each slot does differs font to font, which is why they are numbered, not named. Check the font's docs. In Inter, `ss01` switches to open digits and `cv11` swaps in a single-story `a`.

package/framework/skills/great-interface/references/variant.md

@@ -1,104 +0,0 @@
-# Variants
-
-This skill takes one described piece of UI and builds three versions that differ on purpose. They go behind a picker in the real page, so you can flip between them and choose.
-
-Every other skill here judges. This one produces candidates and hands the decision back. Reviewing existing UI is `interface-review` and `better-interface`, and it does not pick the winner.
-
-## Different answers, not different tints
-
-Three variants that differ in accent color teach nothing. You flip between them, see no real choice and the run is wasted.
-
-So each variant is a different answer to the same brief, on an axis this collection owns:
-
-| Axis | Owner | What varies |
-| --- | --- | --- |
-| Structure | `better-layout` | Grouping, order, column count, what collapses |
-| Density | `better-layout` | Spacing scale, hit areas, how much fits |
-| Emphasis | `better-colors` | Where filled color goes, what recedes |
-| Type | `better-typography` | Scale steps, weight contrast, measure |
-| Voice | `better-writing` | Labels, tone, how much copy |
-
-Pick **one primary axis** and give each variant a different position on it. Secondary choices follow from it rather than varying on their own. A dense variant may need a smaller type step, and that is coherence, not a second axis.
-
-Varying every axis at once produces three unattributable results. You learn which you liked, not what made it work, so the next piece starts from nothing.
-
-## The floor every variant clears
-
-A variant that wins on looks and fails an escalation trigger is not a candidate. It is a bug with a nice surface.
-
-Before a variant enters the picker it clears `better-interface`'s escalation triggers. Every control has an accessible name, keyboard reaches everything a pointer does, focus is visible, nothing clips at 320px and no meaning rides on color alone.
-
-That floor is identical across variants. It is not an axis and never trades against one. Where a direction can only work by breaking it, say so and drop the direction.
-
-## 1. Scope one piece
-
-One piece of UI per run. "The dashboard" is not a piece; the metric card is. Where the brief spans several, name the one the others hang off, say why and offer the rest as later runs.
-
-Restate the brief in one sentence: what the thing is, where it renders, what it has to do.
-
-## 2. Learn the ground
-
-Variants have to look like they could ship tomorrow, so read what they stand on:
-
-- The styling system, the component library and any motion library.
-- The tokens: color, spacing, radius, type scale, easing.
-- The product's density and voice. A dense professional tool bounds how far the boldest variant may go.
-- Where the piece renders: against what background, beside which neighbours, at which widths.
-
-With no project to read, use neutral grays, one accent and the system font stack, and say that is what you did.
-
-## 3. Name the axis before writing code
-
-Default to three variants. Go to five only when asked, or when the space is genuinely wide. Past five nobody compares, they scroll.
-
-Write the set down first, a name and an axis position each. Names say what the direction is, so `Quiet`, `Editorial`, `Dense`, never `Option A`.
-
-This step is done when no two variants share a position and you can state each one's axis in a phrase.
-
-## 4. Build it into the real page
-
-A variant looks fine in isolation, which is why isolation is the wrong place to judge it. Host the variants on the page that will actually contain the piece, with the real chrome, the real neighbours and realistic data.
-
-Select with a URL search param (`?variant=quiet`), so every variant is a link you can send someone. A floating control sets it; [picker.md]() holds the spec.
-
-Render one variant at a time, full size. Thumbnails distort spacing and scale, and spacing is usually the thing you are choosing between.
-
-Where no page can host it, build one self-contained HTML file and keep the same picker.
-
-Give every variant real content: product-shaped copy, plausible names and the number of items the page will really carry. Lorem ipsum and three rows make every structure look good.
-
-## 5. Present the tradeoffs and stop
-
-Flip through every variant yourself first. Each one renders, each interaction responds, the console is clean.
-
-Then hand the decision over:
-
-| Variant | Axis position | Right when | Costs |
-| --- | --- | --- | --- |
-| Quiet | Lowest visual weight | The page is used daily | Least memorable |
-| Editorial | Largest type, most space | The moment deserves weight | Eats vertical space |
-
-Say where the picker is running, which key flips it and which width you judged at. The answer can change between 375px and 1440px.
-
-Never mark a favourite in the table. Asked directly, answer from how often the piece is seen and from the product's personality, not from which one you enjoyed building.
-
-## 6. Promote one, delete the rest
-
-On a choice: build that variant properly where it belongs, following the project's own conventions, then delete the others and the harness.
-
-Asked for another round instead, keep the harness and run step 3 again, taking new positions around the direction you leaned toward.
-
-Until promotion, the harness never imports from production and production never imports from the harness.
-
-## Before you finish
-
-| Mistake | Fix |
-| --- | --- |
-| Variants differ only in accent color or copy | Move one to a different position on the primary axis, or cut it |
-| Every axis varies at once | Vary one; let the rest follow from it |
-| Judged on a blank route | Host them on the page that will contain the piece |
-| Lorem ipsum, three rows, "Jane Doe" | Real copy and the item count the page will really carry |
-| The boldest variant skips keyboard or focus | Clear the floor or drop the direction |
-| A favourite marked in the table | State each variant's cost and let the user choose |
-| Picker restyled with the project's tokens | Keep it visibly outside the design system |
-| Harness left behind after promotion | Delete it unless asked to keep it |

package/framework/skills/great-interface/references/wrapping-and-punctuation.md

@@ -1,55 +0,0 @@
-# Wrapping and punctuation
-
-Where lines start, where they end, where they break and which characters they use.
-
-## Measure (line length)
-
-Long lines make it harder for the eye to find the start of the next. For long-form text, aim for 60–75 characters per line.
-
-Any unit works. `65ch` measures characters directly, one `ch` being the width of the `0` in the current font, and a pixel or rem cap is just as good. At a `16px` body size the 60–75 character range lands roughly between `560px` and `680px` depending on the font, so Tailwind's `max-w-xl` (`576px`) and `max-w-2xl` (`672px`) both fit. What matters is that a cap exists and the line length sits in range. Recheck it if the body font size changes.
-
-## Alignment
-
-`text-align` controls where each line starts and ends. `justify` stretches spaces until both edges line up, which works in specific editorial layouts and nowhere else in an interface.
-
-## Wrapping
-
-| Property | Use |
-| --- | --- |
-| `text-wrap: balance` | Distributes text evenly across multiple lines |
-| `text-wrap: pretty` | Avoids leaving a single short word on the final line |
-| `overflow-wrap: break-word` | Lets long words, links and IDs break before escaping the container |
-| `white-space: nowrap` | Keeps labels and badges on one line where a break looks broken |
-
-Use `balance` on headings and `pretty` on descriptions. Skip both in long-form text, because browsers ignore `balance` past a few lines anyway, and evening out a whole paragraph wastes space and makes it harder to read.
-
-## Truncation
-
-- Single line: `text-overflow: ellipsis`, which needs `overflow: hidden` and `white-space: nowrap`.
-- Multiple lines: `line-clamp` allows any number of lines before the ellipsis.
-
-Truncation hides content. Where the missing text matters, make the full value available in a tooltip or an expanded view.
-
-## Case
-
-`text-transform` changes how case appears without changing the underlying text. Write copy naturally and control presentation with CSS, so a redesign never means rewriting copy.
-
-## Smart punctuation
-
-Keyboard characters are not always the best characters:
-
-| Instead of | Use |
-| --- | --- |
-| Straight quotes `"..."` | Curly quotes that curve around the text (keep straight quotes in code) |
-| Hyphen in ranges | En dash: `2010–2020` |
-| Two hyphens for an aside | Em dash character |
-| Three periods `...` | The single ellipsis character `…` |
-| Regular space in `16 px` | ` ` so the value never breaks apart |
-| Uncontrolled word breaks | `­` to mark where a word may break |
-
-## Internationalization
-
-Two refinements for mixed-direction text:
-
-- **Long paragraphs align by their own language.** A one- or two-line snippet follows the surrounding UI's direction. A paragraph of three or more lines aligns to its own script instead, so an English paragraph stays start-aligned LTR even inside an RTL interface. `text-align: start` with the correct `lang`/`dir` on the paragraph element handles this.
-- **Never reverse digits.** Numbers keep their order in every direction, so a phone number or "541" reads identically in RTL. Browsers handle this through the Unicode bidi algorithm. Never fight it with manual reordering, and wrap mixed number and text values in `<bdi>` where adjacent RTL text disturbs them.

package/framework/skills/jira-mcp/SKILL.md

@@ -1,57 +0,0 @@
----
-name: jira-mcp
-description: Use this skill when working with the Jira MCP server tools for issue management, project management, comments, search, and related Jira workflows.
----
-
-# jira-mcp
-
-Jira MCP server providing 12 tools for interacting with your self-hosted Jira instance via the REST API v2.
-
-## Tools
-
-| Category           | Tools                                                                                                                                          | Default |
-|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------|---------|
-| Issues (9 tools)   | `create_issue`, `get_issue`, `update_issue`, `delete_issue`, `search_issues`, `assign_issue`, `get_issue_types`, `add_comment`, `get_comments` | yes     |
-| Projects (2 tools) | `get_projects`, `get_project`                                                                                                                  | yes     |
-| Users (1 tool)     | `get_current_user`                                                                                                                             | yes     |
-
-All tools are available by default — there are no opt-in toolsets for this server.
-
-## Key Workflows
-
-### Issue Lifecycle
-
-`search_issues` → `get_issue` → `update_issue` / `assign_issue`
-
-### Create Issue (see references/issues.md)
-
-`get_project` → `get_issue_types` → `create_issue`
-
-### Comment Thread (see references/comments.md)
-
-`add_comment` → `get_comments`
-
-### Project Discovery (see references/projects.md)
-
-`get_projects` → `get_project` → `get_issue_types`
-
-## Parameter Hints
-
-- **projectKey**: uppercase project key (e.g., `PROJ`, `SCRUM`, `SUP`). Use `get_projects` to discover available keys.
-- **issueKey**: format `PROJECT-123` (e.g., `CHI-42`, `DEV-1337`)
-- **issueType**: varies by project — use `get_issue_types` to list valid types before creating. Common types: `Bug`, `Task`, `Story`, `Epic`, `Sub-task`
-- **search_issues**: uses JQL (Jira Query Language). Complex values (spaces, special chars) must be quoted: `status = "In Progress"`, `project = PROJ`
-- **Jql**: provide a raw JQL query string (not single-quoted — use double quotes inside for string values)
-- **maxResults**: `search_issues` defaults to 50. Increase for larger result sets.
-- **assignee**: Jira username (not display name or email). Use `get_current_user` to find your own username.
-- **Custom fields**: Pass custom field values directly as parameters (e.g., `customfield_10211: "Sprint 1"`). Discover field IDs via Jira REST API.
-
-## Destructive Tools
-
-`delete_issue` — permanently deletes an issue. Cannot be undone.
-
-## Advanced
-
-- **JQL Search**: full Jira Query Language support — combine operators (`AND`, `OR`, `NOT`), functions (`currentUser()`, `now()`, `startOfDay()`), and ordering (`ORDER BY created DESC`)
-- **Status transitions**: use `update_issue` with `status` to transition issues (e.g., `"In Progress"`, `"Done"`, `"Closed"`). Valid statuses depend on the project's workflow configuration.
-- **Custom fields**: map Jira custom field IDs to values via the `customFields` object or direct parameter names

package/framework/skills/jira-mcp/examples.md

@@ -1,31 +0,0 @@
-# Jira MCP Examples
-
-## Example 1: Create and Assign a Bug
-
-A production bug is discovered and needs to be tracked. Good agent behavior:
-
-- Use `jira_get_projects` to find the correct project key.
-- Use `jira_get_issue_types` to confirm valid types for the project.
-- Use `jira_create_issue` with project key, summary, description, priority, and labels.
-- Use `jira_assign_issue` to assign the bug to the responsible developer.
-- Use `jira_add_comment` to include reproduction steps and environment details.
-
-## Example 2: Find and Update Issues
-
-Search for all high-priority unresolved issues assigned to the user. Good agent behavior:
-
-- Use `jira_search_issues` with a JQL query like `assignee = currentUser() AND priority = High AND status != Done`.
-- Use `jira_get_issue` on each result to review full details.
-- Use `jira_update_issue` to transition the status to "In Progress".
-- Use `jira_add_comment` to log what work is being started.
-- Summarize the findings in a structured report grouped by status.
-
-## Example 3: Close a Sprint Task
-
-A task is complete and ready to close. Good agent behavior:
-
-- Use `jira_get_current_user` to verify authentication is working.
-- Use `jira_search_issues` to find the task by key or summary.
-- Use `jira_get_issue` to review current status, assignee, and description.
-- Use `jira_update_issue` to set status to "Done" and add a resolution note.
-- Use `jira_add_comment` to document what was completed and any follow-ups.

package/framework/skills/jira-mcp/references/comments.md

@@ -1,27 +0,0 @@
-# Comments
-
-## Add Comment
-
-```
-add_comment
-  issueKey: "PROJ-123"
-  comment: "Fixed in latest deployment (v2.4.1)"
-```
-
-Adds a text comment to a Jira issue. No support for rich text or attachments via this server.
-
-## Read Comments
-
-```
-get_comments
-  issueKey: "PROJ-123"
-```
-
-Returns all comments on an issue, ordered by creation date (ascending). Each comment includes `body`, `author`, `created`, and `updated` timestamps.
-
-## Limitations
-
-- **No edit/update** — the current Jira MCP server does not provide an edit-comment tool
-- **No delete** — comments cannot be removed via this server
-- **No threading/replies** — comments are flat (Jira Cloud's threading is not exposed via this API)
-- **No rich text** — plain text only; HTML/markdown in bodies may be rendered by Jira's API

package/framework/skills/jira-mcp/references/issues.md

@@ -1,97 +0,0 @@
-# Issue Management
-
-## Create
-
-```
-create_issue
-  projectKey: "PROJ"
-  summary: "Login page returns 500"
-  issueType: "Bug"
-  description: "Steps to reproduce..."
-  priority: "High"
-  labels: ["bug", "critical"]
-  assignee: "john.doe"
-  components: ["frontend"]
-  customfield_10211: "Sprint 1"    # optional custom fields
-```
-
-Always verify project and issue types first:
-
-1. `get_projects` → find project key
-2. `get_issue_types` with `projectKey: "PROJ"` → find valid types
-3. `create_issue` with valid `projectKey` and `issueType`
-
-## Read
-
-```
-get_issue
-  issueKey: "PROJ-123"
-```
-
-Returns full issue details: summary, description, status, priority, assignee, reporter, labels, components, custom fields, timestamps.
-
-## Search (JQL)
-
-```
-search_issues
-  jql: "project = PROJ AND status = Open"
-  maxResults: 50
-```
-
-### Common JQL Patterns
-
-| Purpose | JQL |
-| ------- | --- |
-| My open issues | `assignee = currentUser() AND status != Done` |
-| High priority recent | `priority = High AND created >= -7d` |
-| By status | `status IN (Open, "In Progress", "Reopened")` |
-| By label | `labels = "bug" OR labels = "critical"` |
-| By reporter | `reporter = john.doe AND status NOT IN (Closed, Done)` |
-| Unassigned | `assignee IS NULL AND status NOT IN (Closed, Done, Resolved)` |
-| Sprints (custom field) | `cf[10211] = "Sprint 1"` |
-| Date range | `created >= "2025-01-01" AND created <= "2025-06-01"` |
-| Order by | `project = PROJ ORDER BY priority DESC, created ASC` |
-| Text search | `text ~ "error message"` |
-| Across all projects | `status = Open AND assignee = currentUser()` |
-
-`search_issues` defaults to showing issues across **all projects** the user has access to. Scope to a specific project with `project = KEY`.
-
-## Update
-
-```
-update_issue
-  issueKey: "PROJ-123"
-  summary: "Updated title"
-  description: "New description"
-  priority: "Low"
-  assignee: "jane.doe"
-  labels: ["bug", "resolved"]
-  status: "In Progress"           # transition to new status
-  customfield_10211: "Sprint 2"
-```
-
-### Status Transitions
-
-- Issue workflow statuses depend on the project's configuration
-- Common transitions: `Open → "In Progress" → "In Review" → "Done" | "Closed"`
-- Use `get_issue` to check current status and `update_issue` with `status` to transition
-- Invalid transitions return an error — check the project's available workflow transitions in Jira
-
-## Assign
-
-```
-assign_issue
-  issueKey: "PROJ-123"
-  assignee: "john.doe"
-```
-
-`assign_issue` is a dedicated tool. You can also assign via `update_issue` with `assignee`.
-
-## Delete
-
-```
-delete_issue
-  issueKey: "PROJ-123"
-```
-
-**Warning**: `delete_issue` is destructive — permanently deletes the issue. Cannot be undone.

package/framework/skills/jira-mcp/references/projects.md

@@ -1,39 +0,0 @@
-# Project Management
-
-## List Projects
-
-```
-get_projects
-```
-
-Returns all Jira projects the authenticated user can access. Each entry includes `key`, `name`, `projectTypeKey`, `lead`, and `avatarUrls`.
-
-Use this to discover available `projectKey` values for issue operations.
-
-## Project Details
-
-```
-get_project
-  projectKey: "PROJ"
-```
-
-Returns detailed information: name, key, description, lead, components, versions (releases), project type, and category.
-
-Verify a project exists and inspect its components/versions before creating issues:
-
-1. `get_project` → check components, versions
-2. `get_issue_types` → check valid issue types
-3. `create_issue` with verified data
-
-## Issue Types
-
-```
-get_issue_types
-  projectKey: "PROJ"
-```
-
-Returns available issue types for a project. Each type includes `name`, `id`, `description`, `iconUrl`, and `subtask` flag.
-
-Common types across most projects: `Bug`, `Task`, `Story`, `Epic`, `Sub-task`, `Improvement`, `New Feature`.
-
-Always call this **before** creating an issue to ensure the `issueType` value is valid for the target project.

package/framework/skills/learning-opportunities/SKILL.md

@@ -1,140 +0,0 @@
----
-name: learning-opportunities
-description: Facilitates deliberate skill development during AI-assisted coding. Offers interactive learning exercises after architectural work (new files, schema changes, refactors). Use when completing features, making design decisions, or when user asks to understand code better. Triggers on "learning exercise", "help me understand", "teach me", "why does this work", or after creating new files/modules. Do NOT use for urgent debugging, quick fixes, or when user says "just ship it".
-license: CC-BY-4.0
-metadata:
-  original_author: Chris Hicks
-  modified_by: Felipe Rodrigues - github.com/felipfr
-  source: https://www.fightforthehuman.com
-  version: 1.1.0
----
-
-# Learning Opportunities
-
-Facilitate deliberate skill development during AI-assisted coding sessions. Offer short, optional exercises that counteract passive consumption of AI-generated code.
-
-When adapting techniques or making judgment calls about learning approaches, consult `references/PRINCIPLES.md` for the underlying learning science.
-
-## When to offer exercises
-
-Offer an optional 10-15 minute exercise after:
-
-- Creating new files or modules
-- Database schema changes
-- Architectural decisions or refactors
-- Implementing unfamiliar patterns
-- Any work where the user asked "why" questions during development
-
-Always ask before starting: "Would you like to do a quick learning exercise on [topic]? About 10-15 minutes."
-
-## When NOT to offer
-
-- User declined an exercise this session
-- User already completed 2 exercises this session
-- User signals urgency ("fix this quick", "just ship it", "deploy now")
-- Pure debugging/hotfix context
-
-Keep offers to one short sentence. Do not repeat or insist.
-
-## Core principle: Pause for input
-
-This is the most important rule. After posing a question:
-
-1. **Stop generating immediately.** Do not continue after the question mark.
-2. Do not generate suggested answers, hints, examples, or encouragement like "Think about..." or "Consider..."
-3. Wait for the user's actual response before continuing.
-
-Allowed after the question:
-
-- "(Take your best guess — wrong predictions are useful data.)"
-- "(Or we can skip this one.)"
-
-After their response:
-
-- If correct: confirm and deepen ("Exactly. And what would change if [variation]?")
-- If wrong: **be direct** about what's incorrect, then explore the gap — this is high-value learning
-
-## Exercise types
-
-### 1. Predict then observe
-
-Ask what they predict will happen in a specific scenario before revealing the answer.
-
-```
-Example:
-User just created auth middleware.
-
-Agent: "Would you like a quick learning exercise on middleware patterns?"
-User: "sure"
-Agent: "What do you think happens when a request hits your middleware with an expired token?
-
-(Take your best guess — wrong predictions are useful data.)"
-
-[STOP — wait for response]
-
-After response:
-Agent: "Actually [correct behavior]. The key difference is [explanation].
-What surprised you about that?"
-
-[STOP — wait for response]
-```
-
-### 2. Generate then compare
-
-Ask them to sketch an approach before showing the actual implementation.
-
-```
-Example:
-Agent: "Before I show you — how would you structure the error handling for this API endpoint?"
-
-[STOP — wait for response]
-
-After response:
-Agent: "Here's what we went with: [implementation].
-What's similar to your approach? What's different, and why do you think we chose this direction?"
-
-[STOP — wait for response]
-```
-
-### 3. Teach it back
-
-Ask them to explain a component as if to a new team member.
-
-```
-Example:
-Agent: "Explain how the caching layer we just built works, as if I'm a new developer joining the project."
-
-[STOP — wait for response]
-
-After response:
-Agent: "You nailed [specific part]. One thing to refine: [specific gap]."
-```
-
-## Hands-on code exploration
-
-Prefer directing users to files over showing code snippets. Having learners locate code themselves builds codebase familiarity.
-
-**Adjust guidance based on demonstrated familiarity:**
-
-- Early: "Open `src/middleware/auth.ts`, around line 45. What does `validateToken` return?"
-- Later: "Find where we handle token refresh."
-- Eventually: "Where would you look to change how session expiry works?"
-
-After they locate code, prompt self-explanation:
-
-"You found it. Before I say anything — what do you think this line does?"
-
-## Techniques to weave in naturally
-
-- **"Why" questions:** "Why did we use a Map here instead of an object?"
-- **Transfer prompts:** "This is the strategy pattern. Where else in this codebase might it apply?"
-- **Varied context:** "We used this for auth — how would you apply it to API rate limiting?"
-- **Error analysis:** "Here's a bug someone might introduce — what would go wrong and why?"
-
-## Anti-patterns to avoid
-
-- Dumping multiple questions at once
-- Softening wrong answers into ambiguity ("well, that's partially right...")
-- Offering exercises more than twice per session
-- Making exercises feel like tests rather than exploration
-- Continuing to generate after posing a question