WillowScript (.ws) is a proposed, not-yet-implemented language. Examples and library integrations here are illustrative design exercises, not verified runnable programs.

Respond to application readiness

An event-driven script says what should happen when a particular event occurs. It should not assume that registering a callback means the callback has already run. Keep the trigger, the response, and the lifetime of the registration distinct.

1. 1

   Respond to application readiness — Discover and trace

   Make a prediction before touching the example.

   Open practice
   →
2. 2

   Respond to application readiness — Build the smallest useful slice

   Change one useful behavior while keeping the contract small.

   Open practice
   →
3. 3

   Respond to application readiness — Change one requirement

   Translate one new mod requirement into a deliberate change.

   Open practice
   →
4. 4

   Respond to application readiness — Boundary detective

   Find a case the simplest success path does not cover.

   Open practice
   →
5. 5

   Respond to application readiness — Flash-check repair

   Use a plausible mistake to show that you understand the mechanism.

   Open practice
   →
6. 6

   Respond to application readiness — Connect the previous skills

   Connect this idea with a previously learned responsibility.

   Open practice
   →
7. 7

   Respond to application readiness — Review and demonstrate

   Collect a useful learning record without pretending the code was executed.

   Open practice
   →