Skip to content
Pathrule

pathrule.iodocs

Pathrule

docs

DocsGet started

Example workspace

Create a local example workspace with a memory, a rule and a skill, then ask your coding agent to read the knowledge for a checkout change.

On this page

A small example is enough to see the difference between a decision, a constraint and a procedure. Create a local workspace, write one of each, and ask your coding agent what applies to a checkout change.

Create the project

Use an empty folder for the example:

mkdir pathrule-example
cd pathrule-example
pathrule setup --local
pathrule ui

Setup creates the local workspace and connects the clients you choose. The Local Console opens in your browser. This is your workspace: the knowledge is editable and stored on this machine.

Write three entries

Select the example workspace in the Local Console. Create these entries at the root path, /.

Memory: Why discounts belong on line items

We apply discounts to individual line items so tax and refund calculations use the same discounted amount. A total-level discount would make those calculations disagree.

A memory keeps the decision and its reason.

Rule: Keep discount calculations in one place

Checkout changes must use the shared discount calculation. Do not add a second calculation in a screen or API handler.

A rule states what the project requires. Delivery does not automatically make a prose rule a blocking check; see rules as guardrails.

Skill: Review a checkout change

1. Read the discount decision and the checkout rule.
2. Identify the calculation the change uses.
3. Check tax and refund behavior for the same discounted line item.
4. Report the verification performed and anything still uncertain.

A skill keeps a procedure the agent can invoke when you ask for it.

Ask the agent what applies

Open your connected coding agent in the example folder and ask:

Before changing checkout discounts, read the Pathrule knowledge for this workspace. Explain the decision, the requirement and the review procedure that apply. Do not implement a change yet.

The agent should distinguish the reason from the requirement and the procedure. Inspect the entries in the Local Console and use pathrule doctor if the agent cannot reach them.

Try a real scope next

In a real repository, attach checkout knowledge to its own path instead of the root. Start with Core concepts for inheritance, and Quickstart for the end-to-end setup.