jpm-voice

Enforce a human-like JPM/PJL voice with 鬼畜破腔 pressure in technical responses.

8|2|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/cuipengfei/prompts --skill jpm-voice
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jpm-voice
Source: https://github.com/cuipengfei/prompts/tree/main/plugins/jpm-voice/skills/jpm-voice
Command: npx skills add https://github.com/cuipengfei/prompts --skill jpm-voice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It fixes AI responses that sound robotic, rigid, or corporate by enforcing a more vivid, street-idiom voice with pressure tactics that prevent the model from backsliding into generic “suggestions” phrasing.

Core Features & Use Cases

  • Voice enforcement for JPM/PJL + “鬼畜破腔”: Keeps the output in a lively, human-like tone and interrupts checklist-style or客服腔 structures.
  • Technical clarity with preserved terminology: Ensures accurate use of real API/library names and avoids distorting technical terms into jokes.
  • Actionable, cause-and-effect explanations: Requires concrete diagnosis, real fixes, and explicit tradeoffs instead of vague summaries.
  • Use cases: “JPM mode” role-play style responses, improving the readability of technical explanations, and preventing overly templated answers from dominating long responses.

Quick Start

Tell your AI: “Use JPM Voice to answer my question in a vivid market-street style with ‘鬼畜破腔’ pressure whenever it starts turning into robotic corporate phrasing, while keeping technical terms accurate.”

Frequently Asked Questions about jpm-voice

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop AI responses from sounding robotic and corporate?

To stop robotic AI responses, you can enforce a human-like voice that breaks rigid checklist-style phrasing. This approach applies pressure tactics to interrupt corporate-sounding structures, forcing the AI to generate vivid, street-idiom answers instead of generic suggestions.

Can I rewrite AI technical answers to be engaging without losing accurate terminology?

Rewriting AI technical answers to be engaging preserves accurate API and library names while applying a lively tone. It requires concise action-and-cause explanations, ensuring technical clarity and explicit tradeoffs remain intact without distorting terms into jokes.

What is the best way to enforce a specific tone for AI generated content?

The best way to enforce a specific tone for AI content is using consistent enforcement triggers that prevent backsliding into generic phrasing. This method maintains the desired voice by applying pressure whenever the output turns into templated, mechanical responses.

How do I prevent checklist-style phrasing from dominating long AI responses?

Preventing checklist-style phrasing in long AI responses requires applying consistent enforcement triggers that interrupt rigid structures. This forces the model to break out of客服腔 structures and deliver concrete diagnoses with real fixes instead of vague summaries.

Does applying a creative directive to AI responses affect technical clarity?

Applying a creative directive does not affect technical clarity if it maintains correct terminology and avoids distorting technical terms. It requires actionable, cause-and-effect explanations with concrete diagnoses and explicit tradeoffs rather than vague summaries.