LoreBook Tips: Random Draws, Nested Cards and One-Line Routines

Write important context once

When you type “go to the gym,” you may not want to explain again why you are training, which exercises you do or what progress you have made. Put that background in a LoreBook and refer to it with a short name.

For the difference between LoreBook and Portrait, read how PlanCoach manages context. This article focuses on techniques.

Start with random draws

Multiple cards can share the same name. Each time you generate a plan, the coach receives one randomly selected enabled card from that name.

Create four cards called reading, each containing a different book and a specific request: read a chapter, write three questions, continue from a named section, or apply one idea in this week’s review.

Type “read this afternoon” using the matching card name, and one book is selected. The tag above the input shows a dice symbol; tap it to inspect all cards in the draw.

• Disable a finished book rather than deleting it, then add another.
• Put light, medium and heavy workouts under one name.
• Put ten familiar dishes under dinner to reduce the “what should I cook?” decision.

Trigger a draw automatically

Set a name to trigger on every generation from the LoreBook list. You do not need to mention it in the task. Multiple cards with that name still produce a random draw.

For example, give today's style three cards: martial-arts narration, sports commentary and a short dry joke after every step. Enable automatic triggering to vary the coach’s delivery.

Nest and combine cards

A card can mention another card’s name. Define back workout and reading, then put “back workout in the morning, reading in the afternoon” inside Saturday routine.

When you mention Saturday routine, its referenced cards can be included too. Tap the tag above the input to see why it matched and inspect the content.

Example 1: save a method

A card can describe how you want the coach to help, not just a noun. For example, create show me the future:

Help the user imagine a good future after completing the current task.
Do not give generic encouragement or empty slogans.
Use the task, long-term goals and Portrait to describe a concrete, vivid scene.

Focus on:
- Positive changes in the user's life after finishing.
- New freedom, abilities or opportunities.
- How their future self might thank them for today's effort.

Humour and enthusiasm are welcome, but do not promise unrealistic results.
Connect that future to the small action the user is taking right now.

Compare asking Cool Girl to prepare a promotion-review presentation with adding show me the future to the request.

The first practical step can remain “create a file,” while the opening gives you a more personal reason to do it.

Example 2: connect small tasks to bigger goals

Put a long-term goal, its meaning and your current progress in a card. Examples include a two-month fitness goal, preparing for a postgraduate entrance exam or learning 2,000 words in a year.

In the fitness example, the coach knows it is week three and the recorded waist measurement has changed from 82 to 80, so it acknowledges progress before proposing the steps.

In the exam example, the coach knows the exam is less than two months away and the target is 370+, so it proposes bringing the relevant books and starting with 15 minutes of mathematics.

Choose three to five meaningful goals for the coming year and make cards for them. Update the current-state information as it changes.

Put the techniques together

Start Saturday routine; show me the future.

Saturday routine includes back workout, which references a fitness goal; a meal card carries food preferences; reading draws one of four books.

The example plan uses the specified exercise sets, avoids coriander and celery, draws a book and connects the work to the bigger goal. Update the underlying cards once and other routines can reuse them.

Check expansion depth

The default expands one level. Saturday routine → back workout → fitness goal needs two levels. Open Profile → Settings → Experience → Interaction and set LoreBook expansion depth to two levels.

Keep the context concise

Long cards and deep nesting can make a model overlook details. Keep one subject per card, use short sentences and lists, put details in reusable cards, and include only what this task needs.