Two Paths: No-Code and Developer

You can finish this course without writing code. If you do write code, some steps get faster and more exact. Pick a path now and use it in every exercise.

No-Code Path

• Write skills as text and load them through your product's skill or custom instruction settings.
• Test by pasting the six inputs and recording results in a sheet.
• Connect tools through the product's connector settings, read only first.
• Measure with a spreadsheet and a stopwatch.

Developer Path

• Keep skills in a folder under version control, with the test table in a file next to them.
• Put any step that must be exact, such as totals or date math, in a script the skill calls.
• Run the six inputs from a test script and save the outputs for comparison.
• Log runs to a file or table, and add cost and time to the log.

What Doesn't Change

• The safety rules: draft first, read before write, a person checks before anything leaves.
• The tests: six inputs including an injection input.
• The measurement: a baseline, a target and a keep, fix or stop decision.

Common Mistakes

• Building a script when a sentence in the skill would do. Fix: add code only for steps that must be exact.
• Skipping tests on the no-code path. Fix: a sheet and six inputs is enough.
• Mixing the paths halfway through. Fix: choose one per exercise and note it.

Exercise

• Write which path you'll follow and one tool you'll use for tests.
• Pass condition: a one-line path choice and the file or sheet where your test table will live.