🎯 Fundamentals

What is
“Organize my work” describes an intention, but it doesn’t say which file should exist by the time you’re done.

Why learn
A concrete output lets you compare the request with the result. Without that comparison, a well-written response can seem complete even when important information is missing.

Key concepts
Input · Output · Unit · Scope

What is
A short sheet works like a work agreement.

Why learn
The sheet reduces back-and-forth and helps you identify scope changes. A new function enters a future list instead of silently changing the work in progress.

Key concepts
Goal · Deletion · Acceptance · Pending

What is
A good request tells which fields must be preserved, which format should be used, and how to handle missing information.

Why learn
The output quality depends on the clarity of the transformation. Specifying how to handle gaps is usually more useful than adding adjectives like perfect, complete, or professional.

Key concepts
Format · Fidelity · Gap · Separation

What is
Do a line-by-line comparison.

Why learn
Checking turns an impression into evidence. It also shows where to fix: in extraction, in the format, or in the business rule—without rebuilding the whole process.

Key concepts
Counting · Correspondence · Regression · Evidence

What is
A step ends when it delivers what was agreed and passes the checks.

Why learn
Limiting work in progress reduces the feeling of having many projects almost ready. You start accumulating small deliveries that work and can be combined.

Key concepts
Step · Limit · Blocker · Improvement

What is
Create a folder for the exercise and save the input text before using the assistant.

Why learn
Practice teaches you to close a small task and introduces a central idea of the course: vary the input to discover whether the solution understood the rule or just copied the example.

Key concepts
Common case · Incomplete case · Variation · Conclusion

What is
A skill brings together instructions and, sometimes, scripts and auxiliary files to guide a task.

Why learn
Recognizing the pieces lets you estimate effort and know where a failure happens. You avoid looking for a command that was never installed or giving a skill a capability that depends on another service.

Key concepts
Skill · CLI · MCP · Dependency

What is
Start with the description, the instruction files, and the installer.

Why learn
A small, traceable inspection is more useful than a generic approval. It links the decision to a specific review and lets you reevaluate only what changed.

Key concepts
Review · Installer · Destination · Record

What is
A useful finding includes location, evidence, impact, and context.

Why learn
Reports without context create many alarms and little guidance. Triage helps you distinguish necessary behavior from excessive permissions or an operation that requires additional care.

Key concepts
Evidence · Impact · Context · Triage

What is
Automated tools identify patterns; you need to interpret the result.

Why learn
Inspection quality isn’t measured by how many alerts you eliminate. It depends on reproducible decisions and visible limitations, even when you can’t conclude.

Key concepts
Confirmed · False positive · Inconclusive · Focused test

What is
Install only after you understand what will be changed.

Why learn
Testing reduces the cost of discovering incompatibilities. You learn how the whole setup behaves before you allow it to participate in larger tasks or use important documents.

Key concepts
Isolation · Fixture · Reversal · Promotion

What is
Use the fictional example below as if it were part of a skill.

Why learn
A well-written decision can be reviewed by someone else. It also shows that inspection isn’t a definitive stamp: new behaviors require new analysis.

Key concepts
Statement · Observation · Condition · Decision

What is
A review starts with the change you want to evaluate and with the expected behavior.

Why learn
Context reduces generic comments and prevents the reviewer from proposing changes that contradict the goal. It also limits the cost and scope of the review.

Key concepts
Contract · Diff · Hypothesis · Reproduction

What is
In a Git project, the diff shows what changed.

Why learn
A clear baseline prevents the reviewer from comparing the wrong files or treating old code as part of the current change. Checking the status also avoids accidentally publishing preparation data.

Key concepts
Baseline · Status · Scope · Local help

What is
Ask each finding to include the trigger, effect, location, and how to reproduce it.

Why learn
Actionable findings make the review a decision-making tool. You can prioritize by impact and verify whether the smallest change actually fixed the issue.

Key concepts
Trigger · Effect · Priority · Minimal fix

What is
Many errors appear on the second execution.

Why learn
These scenarios are easy to forget in demos. Testing retry and interruption reveals problems that a quick read or a single run won’t show.

Key concepts
Retry · Idempotence · Atomicity · Interruption

What is
When a fix fails repeatedly, record what you already tried and the result of each attempt.

Why learn
A minimal case reduces the number of possible explanations. It lets you distinguish a logic problem, an incompatible configuration, and an unavailable dependency.

Key concepts
Minimal case · History · Single hypothesis · Stop

What is
Imagine a fictional form that adds requests to a list.

Why learn
Practice connects review, testing, and business behavior. You learn to verify the real effect of the fix and to recognize when two seemingly identical inputs represent different situations.

Key concepts
Identifier · Duplication · Conflict · Return test