jeanblog

v0.1.0 - Check a tutorial draft against its saved plan and sketch before review. Use when a draft needs plan adherence, concept timing, code continuity, runnable snippet, and Hugo placement checks before tutorial review.

v0.1.0 - Record an approved tutorial plan into an ignored local run directory. Use when a LeetCode or algorithm tutorial plan must survive context compaction, multi-turn work, or handoff before build starts.

v0.1.0 - Create a teaching skeleton and code-growth contract from a saved tutorial plan. Use before tutorial build when concept timing, helper extraction, final-code placement, or checkpoint continuity must be made explicit.

v0.1.1 - Build exactly one planned LeetCode tutorial increment through problem pressure, naive baseline, break, change, check, freeze, and review handoff. Use when a task-first LeetCode tutorial plan is ready and the next checkpoint must be drafted without self-approval.

v0.1.0 - Build exactly one planned algorithm tutorial checkpoint and stop for review. Use when a task-first algorithm tutorial plan is ready and the next section must derive one mechanism, invariant, code fragment, or runnable checkpoint from concrete pressure without self-approval.

v0.1.0 - Deepen 1-2 selected concepts in a reviewed algorithm tutorial using PDKH standards. Use when a method tutorial needs stronger invariant, formalization, correctness, complexity, counterexample, or engineering-reality evidence without broadening into unrelated topics.

v0.1.0 - Plan one standalone algorithm, data-structure, or method tutorial as review-gated writing tasks. Use when the subject is the technique itself and the plan must preserve derivation-first construction, runnable checkpoints, invariants, correctness, complexity, counterexamples, engineering tradeoffs, deepening tasks, and publishable Hugo placement before drafting.

v0.1.0 - Plan one LeetCode or OJ-style tutorial as ordered, review-gated writing tasks before drafting. Use when a concrete problem needs a publishable guided-build tutorial with problem facts, examples, constraints, smaller subproblem, connected code checkpoints, optimization bridge, verification, and checkpoint handoff.

v0.1.0 - Review one algorithm tutorial checkpoint or full draft as an independent gate. Use when checking derivation-first structure, pressure, mechanism, invariant, evidence, code continuity, depth readiness, and final runnable demo placement before allowing the tutorial to advance.

v0.1.0 - Simplify a reviewed and sufficiently deep algorithm tutorial without weakening derivation, evidence, invariants, correctness, complexity, or final runnable demo. Use when the article is structurally accepted but too repetitive, checklist-like, or heavy.

v0.1.0 - Review one LeetCode tutorial checkpoint or full draft as an independent gate. Use when deciding whether a problem tutorial step can advance, needs revision, or must block because pressure, break, change, check evidence, code continuity, or final-code placement is weak.

v0.1.0 - Simplify a reviewed LeetCode tutorial without breaking the guided-build chain. Use when a problem tutorial has review-pass structure but needs tighter prose, less template noise, clearer transitions, or reader-facing language while preserving problem facts, step checks, checkpoints, and final runnable code.

v0.1.0 - Review teaching-first tutorial drafts for guided-build quality, structural correctness, and incremental code growth when the user wants a pass/fail verdict plus revision targets rather than a rewrite.

v0.2.0 - Enhance a stable technical post when the core tutorial and minimal publishable structure are already in place and the user now wants stronger SEO, supporting sections, title polish, multi-language code, or engineering add-ons.

v0.1.0 - Write publishable jeanblog thoughts posts for tool, workflow, and system evaluations when the user wants a conclusion-first comparison with fit/not-fit boundaries and a clear personal judgment instead of a tutorial.