pro-skill

Pro Skill 🛠️

Ship production-grade software at a senior+ bar — no hand-holding.

Pro Skill is the inverse of noob-skill. Where Noob walks a total beginner one click at a time and explains every permission, Pro assumes you're an experienced engineer and gets out of the way: dense, high-signal, autonomous, and uncompromising on the bar.

Type /pro and you're working with a senior peer, not a tutorial.

What it does

• Operating contract, stated once — works autonomously and in batches, surfaces only the decisions that change architecture, cost, security, or public API. No per-keystroke ceremony.
• Architecture first — explicit tradeoffs, build-vs-buy, data model and contracts before code.
• Engineering rigor — TDD by default, strict types, systematic debugging, self-review.
• Security as a design input — threat-model while building, not a final rubber stamp.
• Stack & infra by constraints — picks datastore/auth/hosting/queue/observability by scale, cost, lock-in, and ops burden, then wires it to production standard.
• Design craft — UI at a senior taste bar, real type/color systems, polished states, a11y, perf.
• Max leverage — actively parallelizes, delegates to subagents, and pulls in specialist skills and MCPs (the opposite of "keep the machinery invisible").
• Ship & operate — green pipeline, reviewable diff, safe rollout, rollback path, live monitoring.
• Learns you — your stack, conventions, and taste persist to ~/.pro/preferences.md and apply in every future session.

The standard

Correctness · strict type safety · threat-modeled security · budgeted performance · real observability · maintainability · taste. Nothing is "done" until it runs (with evidence), passes the security gate, and meets the bar.

Install

Requires Claude Code. Add this repo as a plugin marketplace, then install:

claude plugin marketplace add Jumpsy/pro-skill
claude plugin install pro-skill@pro-skill

(Or clone and add the local path: claude plugin marketplace add ./pro-skill.)

Quickstart

1. Install (above).
2. Open Claude Code in your project.
3. Type /pro — or "build this properly / production-grade / like a senior engineer."
4. It states the contract once, then works.

Pro vs Noob

	Noob Skill	Pro Skill
Audience	never coded	experienced engineer
Pace	one step at a time	batched, autonomous
Permissions	explained before every popup	contract stated once, then trust
Jargon	always explained	used directly
Quality bar	held quietly	named and enforced explicitly
Helpers/agents	invisible, never required	leveraged aggressively
Ends with	👉 Next: <one click>	state + evidence + open decisions

License

MIT — see LICENSE. Built by Jacob Hurvitz.