Skill Claude CodeCodex
Create and execute IDE run configurations for MPS root nodes via MPS MCP — Java Application for IMainClass / ClassConcept with main, JUnit Tests for ITestCase. Use when launching DSL main-like roots, plain BaseLanguage ClassConcept mains, or MPS test cases from a node; reusing or replacing an existing run config…
Skill Claude CodeCodex
Use when writing or modifying tests inside MPS @tests models — NodesTestCase (typesystem, constraints, scopes, dataflow, generator output), EditorTestCase (intentions, actions, keystrokes, side-transforms, completion), MigrationTestCase (migration scripts), BTestCase (plain JUnit on hand-written Java/Kotlin runtime)…
Skill Claude CodeCodex
Guidelines for using the IntelliJ Registry API. Use when working with registry keys or feature flags.
Skill Claude CodeCodex
Guide for using Structural Search and Replace in IntelliJ. Use when creating or modifying SSR inspections or search patterns.
Skill Claude CodeCodex
Use when working with TeamCity CI/CD or when user provides a TeamCity build URL. Use teamcity CLI for builds, logs, jobs, queues, agents, and pipelines.
Settings file Claude Code
Agent settings configuring env.
Instructions file CodexOpenCode
Instructions for JetBrains/MPS, covering agents guide for this project, ⚠️ warning: never read raw mps model files, project nature: jvm + mps, choose tools by task and rules for java/kotlin work.
Instructions file
Instructions for JetBrains/MPS, covering agents guide for this project, ⚠️ warning: never read raw mps model files, project nature: jvm + mps, choose tools by task and rules for java/kotlin work.
Instructions file CodexOpenCode
Instructions for JetBrains/thinkrail, covering thinkrail, module structure & boundaries (top-priority requirement), engine: pi only, in-process, architecture (three rings) and repo layout.
Instructions file
Instructions for JetBrains/thinkrail, a project described as: Vibe code with pi in a lightweight, real IDE - The Vibe You Need.
Skill Claude CodeCodex
Use when composing an askuserquestion 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.
Skill Claude CodeCodex
Use this BEFORE any creative or feature work: building a new feature, adding functionality, changing behavior, or making a nontrivial design decision. Turns the user's request into a validated design — recorded as a spec-graph task-spec — before any implementation. Do not skip this because a change looks small.
Skill Claude CodeCodex
Use FIRST when any new piece of work arrives — a request, feature, change, fix, question, or idea — before starting on it or choosing an approach. Not for continuing work already routed to a workflow skill.
Skill Claude CodeCodex
Use when the repo holds real source code but no specs: the existing-codebase branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for empty workspaces (starting-a-new-project) or feature work in a specced project (brainstorming).
Skill Claude CodeCodex
Use whenever asked to set up, onboard, initialize, or spec a project — the front door when the workspace has no spec graph yet (brand-new or an existing codebase); also seeded by the app's Set-up-project card (/skill:setting-up-a-project). Not for feature work in an already-specced project — use the brainstorming…
Skill Claude CodeCodex
Use when finished work needs to ship as a pull request, or when the ask is about a PR — creating one, bringing it up to date, adding screenshots, watching its checks, or addressing its review comments. Not for reviewing a PR you are not shipping.
Skill Claude CodeCodex
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Use when a reflection package hands you another agent's review findings to verify (before they become a fix request): you are the REFLECTOR, an independent skeptic. Judge each finding against the real code and settle it with reflectfinding — kept or refuted.
Skill Claude CodeCodex
Use when a review package asks you to review a plan step's change set (todo.startReview): you are the REVIEWER, not the author. How to judge an agent-written diff, file findings with addreviewcomment, and settle with exactly one reviewverdict.
Skill Claude CodeCodex
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
Skill Claude CodeCodex
The project's specs are its ground truth: durable documents describing the architecture, decisions, contracts, and boundaries behind the code, organized as a connected graph. Read this skill and reach for the spec tools FIRST — before reading code — whenever you explore the project, plan or start a task, add or change…
Skill Claude CodeCodex
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright…