nurijanian-skills

A growing collection of Claude Code, Cursor, and Codex skills for product managers.

These skills are part of PM OS — an AI workspace for product managers built inside Cursor and Claude Code, with 190+ skills, 168 frameworks, and 7 guided workflows. If you want the full system, start there. If you want just these skills, install them below.

Install

One-liner (recommended)

npx nurijanian-skills

Installs all skills into Claude Code, Cursor, and Codex. Pass flags to pick targets:

npx nurijanian-skills --claude   # Claude Code only → ~/.claude/skills//
npx nurijanian-skills --cursor   # Cursor only      → ~/.cursor/skills//
npx nurijanian-skills --codex    # Codex only       → ~/.codex/skills//

Combine flags to target multiple tools (--claude --cursor).

From source (for development)

git clone https://github.com/gnurio/nurijanian-skills.git
cd nurijanian-skills
node bin/install.js               # copy mode
node bin/install.js --link        # symlink mode (live-edit source → changes hit Claude Code instantly)

--link applies to Claude Code, Cursor, and Codex directory-form skills.

Where things land

Uninstall

npx nurijanian-skills --uninstall

Or target a single tool: --uninstall --claude.

To wipe and reinstall fresh: npx nurijanian-skills --clean.

---

Skills

PM Alignment

PM coaching grounded in what designers and engineers actually say about their best product managers. A survey of the people closest to PMs surfaces 7 behavioral clusters that separate great from average.

Start here:

/orchestrate-pm-alignment

---

Verbalized Sampling

Implements Verbalized Sampling (Zhang et al. 2025) — a training-free technique that counteracts LLM mode collapse caused by typicality bias. Instead of asking for a single response, it prompts for a probability distribution over outputs to generate genuine diversity.

Use when the task needs real variety: creative writing, brainstorming, synthetic data generation, persona simulation, adversarial examples, or any situation where “generate 5 ideas” keeps returning the same cluster.

/verbalized-sampling

---

Tech Sensemaking

Analyzes technology announcements to surface non-obvious strategic implications using Verbalized Sampling. Works against any context — a business, product, codebase, feature branch, personal project, career, or exploratory domain. Goes beyond obvious hot takes to find new outcomes, affordances, and competitive levers a technology change creates.

Trigger on: “analyze this announcement”, “what does this mean for us”, “what can we do with this”, “strategic implications of X”.

/tech-sensemaking

---

Focal Point Finder

Find, evaluate, or create focal points in coordination and negotiation problems. Based on Thomas Schelling’s The Strategy of Conflict — the foundational game theory text on how people converge on outcomes without explicit agreement.

Use when multiple parties need to align on a single choice (a standard, a deadline, a boundary, a price, a process) and no one has the authority to dictate the answer. The skill walks through scanning for existing focal points, diagnosing why convergence is failing, and creating or proposing a focal point using 7 Schelling-grounded techniques.

Trigger on: “where should we align?”, “how do we get everyone on the same page?”, “find a focal point”, “Schelling point”, “coordination problem”, “propose a standard”, “set a default”.

/focal-point-finder

---

Rulebook for Arguments

Construct, critique, and audit arguments using the complete methodology from Weston’s A Rulebook for Arguments. Four modes: BUILD a logically sound argument from scratch, AUDIT an existing argument for validity and fallacies, ESSAY to draft or improve argumentative writing using the full extended-argument rules, or DEBATE to steelman both sides and identify the stronger position.

Covers all 45 rules, 19 common fallacies, 3 definition rules, deductive forms (modus ponens, modus tollens, disjunctive syllogism, reductio ad absurdum), causal reasoning, analogy evaluation, and source quality assessment.

/rulebook-for-arguments

---

Make Requirements Great

Review existing requirements or turn raw context into strong requirements using an 18-characteristic quality framework: unambiguous, clear, cohesive, consistent, conformant, current, modifiable, traceable, relevant, unique, categorised, complete, correct, concise, testable, implementation-independent, owned, and feasible.

Use for PRDs, specs, user stories, acceptance criteria, BRDs, FRDs, requirements catalogues, requirements traceability, requirements audits, or feature notes that need to become formal requirements.

/make-requirements-great

---

Vibe Code Leaf Finder

Audit a codebase and classify every file as LEAF (safe to vibe code freely), BRANCH (AI can draft, human reviews structural decisions), or TRUNK (human writes every line). Produces a LEAF_REPORT.md with a classification table, suggested stress tests per leaf file, and a plain-English summary for non-engineers.

Grounded in Erik Schluntz’s (Anthropic) leaf-vs-trunk framework from the Vibe coding in prod talk (Code w/ Claude, 2025): tech debt is acceptable in leaf nodes because nothing depends on them, but trunks and branches must stay protected, deeply understood, and extensible.

Use when:

• You want to know where it’s safe to let Claude rewrite code without engineer review of every line.
• You’re a PM or founder who wants to ship features without breaking core architecture.
• You’re setting up a vibe-coding session and need to scope which files are in bounds.

Trigger on: “vibe-code audit”, “leaf finder”, “where can I let Claude loose”, “which files are safe to rewrite”, “can a PM edit this”.

/vibe-code-leaf-finder

---

Workflow Trellis

Turn messy workflow evidence into a visible model of the work: durable obligations, entities, states, fragmented sources of truth, AI insertion points, and exception queues. Useful for analyzing interviews, customer research, operational workflows, vertical SaaS opportunities, PM workflows, and AI feature ideas.

The core move is to represent the work before proposing automation, so product strategy is grounded in obligations, fragments, confidence signals, and human accountability.

/workflow-trellis

---

Reasons People Buy

Ground persuasive writing in a real reason people buy before reaching for features or mechanisms. The skill uses 15 buying reasons, 8 deeper human drives, and buyer-journey checks to make copy outcome-led instead of feature-led.

Use for landing pages, ads, offers, positioning, subscription copy, or audits where the question is “why would anyone buy this?”

/reasons-people-buy

---

Contributing

To add a new skill:

1. Create skills//SKILL.md with YAML frontmatter (name, description).
2. Put any reference files or templates in skills//references/ or skills//assets/. Every skill must be self-contained — no shared top-level references.
3. Register it in skills.json (name, dir, description).
4. Add a section to this README.
5. Test locally with node bin/install.js --link so edits flow to Claude Code instantly.

License

MIT © George (gnurio)