Updated 1d ago
by JetBrains
thinkrail
Vibe code with pi in a lightweight, real IDE that customises itself around the way you work — The Vibe You Need
518 GitHub stars (518)
+28 in 20 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 |
- 11 skills (11 skills found in its SKILL.md files)
- 42 forks (42 forks)
- 1d ago last update (Last updated 1d ago)
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/skills/asking-user-questions/SKILL.md on GitHub (opens in a new tab) -
brainstorming
Use before implementation when a request requires choosing product scope, user-visible behavior, or architecture. Not for fully specified fixes, mechanical refactors, documentation, or configuration-only changes.
packages/pi-thinkrail-workflow/skills/brainstorming/SKILL.md on GitHub (opens in a new tab) -
choosing-a-workflow
Use at the start of new project onboarding, PR lifecycle work including PR checks, or changes that require choosing product scope, user-visible behavior, or architecture. Not for continuing work already routed to a workflow, non-PR questions, checks, explanations, or localized fully specified work.
packages/pi-thinkrail-workflow/skills/choosing-a-workflow/SKILL.md on GitHub (opens in a new tab) -
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/skills/importing-a-codebase/SKILL.md on GitHub (opens in a new tab) -
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/skills/setting-up-a-project/SKILL.md on GitHub (opens in a new tab) -
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/skills/shipping-a-pr/SKILL.md on GitHub (opens in a new tab) -
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/skills/starting-a-new-project/SKILL.md on GitHub (opens in a new tab) -
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/skills/writing-specs/SKILL.md on GitHub (opens in a new tab) -
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/skills/writing-workflow-skills/SKILL.md on GitHub (opens in a new tab) -
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a user-origin 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/skills/todos/SKILL.md on GitHub (opens in a new tab) -
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/skills/spec-graph/SKILL.md on GitHub (opens in a new tab)
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.
Similar skills
-
eigentby eigent-ai Eigent: The Open Source Cowork Desktop - Local and Free Alternative to Claude Cowork and Codex
-
nexentby ModelEngine-Group Nexent is a zero-code platform for auto-generating production-grade AI agents using Harness Engineering principles — unified tools, skills,…
-
paperclipby paperclipai The open-source app everyone uses to manage agents at work
-
rufloby ruvnet 🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems.…
-
OpenMontageby calesthio World's first open-source, agentic video production system. 12 production pipelines, 100+ tools, 700+ agent skill and production-knowledge…
-
claude-code-best-practiceby shanraisshan from vibe coding to agentic engineering - practice makes claude perfect