Skip to main content
Create a small custom profile in a real local project. You will define issue pages, add one issue, check it, and make one controlled change to the rules.

Skill level

Beginner

Time

About 10 minutes

Result

One valid custom issue page

Before you start

Install llmwiki 1.0 or later, then check the version in any directory. Run in: any directory
Does: confirms that the CLI is available
Writes: nothing
You should see: version 1.0.0 or later
If it fails: follow Installation, then open a new terminal.

Your five steps

  1. Create an empty project and its profile.
  2. Validate and understand the generated file.
  3. Add your first issue.
  4. Check what llmwiki recognizes.
  5. Add a priority rule, see one useful warning, and repair the issue.

Step 1: Create the project

Create and enter a new folder. Keep each command separate so it is clear which step failed if your shell reports an error. Run in: the folder where you keep projects
Does: creates the tutorial project folder
Writes: issue-tracker-wiki/
Run in: the folder where you keep projects
Does: enters the project
Writes: nothing
Now create the smallest useful profile. Run in: issue-tracker-wiki/
Does: defines one kind of page called issues
Writes: .llmwiki/profile.json and wiki/issues/
You should see:
Checkpoint: both paths shown above exist.
If it fails: use an empty project. The command refuses to replace an active profile or reinterpret existing wiki content. It never offers a force option.

Step 2: Validate and understand the profile

Run in: issue-tracker-wiki/
Does: checks that every profile rule is supported and internally consistent
Writes: nothing
You should see:
Checkpoint: you can identify where issue pages belong and which information each issue must contain.

Step 3: Add your first issue

Create wiki/issues/explain-first-profile.md with the following exact content.
Run in: issue-tracker-wiki/
Does: creates the first issue page
Writes: wiki/issues/explain-first-profile.md
Checkpoint: the new Markdown file exists under wiki/issues/.
If it fails: confirm that you are inside issue-tracker-wiki/ and that Step 1 created wiki/issues/.

Step 4: Check what llmwiki recognizes

First check the page against the active profile. Run in: issue-tracker-wiki/
Does: checks existing pages against the profile rules
Writes: .llmwiki/last-lint.json
You should see:
Then open the local read-only viewer. Run in: issue-tracker-wiki/
Does: starts a local viewer and asks your operating system to open it
Writes: nothing
The port varies, so the readiness line looks like:
Open Graph and find Explain the first profile. The issue appears as a typed graph node. This proves llmwiki recognized the file under your profile; the current viewer does not open typed issue bodies as ordinary page routes. Press Ctrl+C in the terminal when you are finished.
Run llmwiki view without --open, then copy the printed loopback URL into a browser. This is the normal approach over SSH, in a container, or on a headless machine.

Step 5: Add a rule and repair one issue

Open .llmwiki/profile.json. Add priority to requiredFields, then add its definition beside title under fields. The complete result is below; the new parts are the second required field and the priority definition.
Validate the rules first.
It succeeds because the profile is valid. Now check the existing issue:
You should see:
This warning is deliberate. Profile validation checks the rules themselves; lint checks your pages against those rules. Add one line to the issue’s frontmatter:
Run both checks again:
You should see: 0 error(s), 0 warning(s), 0 info.
You created a custom profile, added a page that follows it, changed one rule, and repaired the resulting warning. Every checkpoint is an ordinary project file that you can edit and commit.

Where to go next