Updated today
by JetBrains
thinkrail
Vibe code with pi in a lightweight, real IDE that customises itself around the way you work — The Vibe You Need
7.8k GitHub stars (7,753)
+7.2k in 30 days
| Period | New stars |
|---|---|
| Sep 27 | +1 |
| Sep 28 | +4 |
| Sep 29 | +2 |
| Sep 30 | +2 |
| Oct 1 | 0 |
| Oct 2 | +1 |
| Oct 3 | +4 |
| Oct 4 | +1 |
| Oct 5 | +3 |
| Oct 6 | +2 |
| Oct 7 | +1 |
| Oct 8 | +2 |
| Oct 9 | 0 |
| Oct 10 | +1 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | +3 |
| Oct 14 | 0 |
| Oct 15 | 0 |
| Oct 16 | +1 |
| Oct 17 | +118 |
| Oct 18 | +24 |
| Oct 19 | +102 |
| Oct 20 | +129 |
| Oct 21 | +78 |
| Oct 22 | +8 |
| Oct 23 | +11 |
| Oct 24 | +35 |
| Oct 25 | +77 |
| Oct 26 | +644 |
| Oct 27 | +1,161 |
| Oct 28 | +1,106 |
| Oct 29 | +1,047 |
| Oct 30 | +1,351 |
| Oct 31 | +173 |
| Nov 1 | +232 |
| Nov 2 | +138 |
| Nov 3 | +230 |
| Nov 4 | +228 |
| Nov 5 | +190 |
| Nov 6 | +153 |
- 12 skills (12 skills found in its SKILL.md files)
- 473 forks (473 forks)
- Today last update (Last updated today)
Install
Skills CLI
npx skills add JetBrains/thinkrail
Asks which skills and agents to install. Just one: npx skills add JetBrains/thinkrail --skill asking-user-questions — add -g for every project.
Claude Code
git clone https://github.com/JetBrains/thinkrailcp -r "thinkrail/packages/pi-thinkrail-workflow/skills/asking-user-questions" ~/.claude/skills/
Copies the asking-user-questions skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add JetBrains/thinkrail
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
asking-user-questions
Use when composing an ask_user_question round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.
packages/pi-thinkrail-workflow/ on GitHub (opens in a new tab)skills/ asking-user-questions/ SKILL.md -
brainstorming
Use before implementing a feature, a change in behavior, or a bug fix — however small. Not for questions, checks, or edits that change no behavior (typos, documentation or configuration only, mechanical refactors).
packages/pi-thinkrail-workflow/ on GitHub (opens in a new tab)skills/ brainstorming/ SKILL.md -
choosing-a-workflow
Use at the start of new project onboarding, PR lifecycle work including PR checks, or any change to what the product does — a feature, a behavior change, or a bug fix. Not for continuing work already routed to a workflow, non-PR questions, checks, explanations, or edits that change no behavior.
packages/pi-thinkrail-workflow/ on GitHub (opens in a new tab)skills/ choosing-a-workflow/ SKILL.md -
importing-a-codebase
Use when asked to create the initial spec graph for an existing codebase that has source code but no specs. Normally reached via setting-up-a-project.
packages/pi-thinkrail-workflow/ on GitHub (opens in a new tab)skills/ importing-a-codebase/ SKILL.md -
setting-up-a-project
Use when asked to set up, onboard, initialize, or spec a project with no spec graph, or when invoked by the app's Set-up-project card. Not for ordinary work in an already-specced project.
packages/pi-thinkrail-workflow/ on GitHub (opens in a new tab)skills/ setting-up-a-project/ SKILL.md -
shipping-a-pr
Use when finished work needs to ship as a pull request, or when creating, syncing, updating metadata, checking status, monitoring CI, or addressing review comments on a PR. Not for reviewing a PR you are not shipping.
packages/pi-thinkrail-workflow/ on GitHub (opens in a new tab)skills/ shipping-a-pr/ SKILL.md -
starting-a-new-project
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
packages/pi-thinkrail-workflow/ on GitHub (opens in a new tab)skills/ starting-a-new-project/ SKILL.md -
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
packages/pi-thinkrail-workflow/ on GitHub (opens in a new tab)skills/ writing-specs/ SKILL.md -
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
packages/pi-thinkrail-workflow/ on GitHub (opens in a new tab)skills/ writing-workflow-skills/ SKILL.md -
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
packages/pi-todos/ on GitHub (opens in a new tab)skills/ todos/ SKILL.md -
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no `pi` command to call.
packages/server/ on GitHub (opens in a new tab)skills/ managing-mcp-servers/ SKILL.md -
spec-graph
Use when locating, reading, creating, updating, or validating project specs, or when work is governed by or may alter a documented boundary, contract, invariant, behavior, or architecture decision.
packages/spec-graph/ on GitHub (opens in a new tab)skills/ spec-graph/ SKILL.md
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.