Big Tech Honor Drive Engine

Problem It Solves

In coding, debugging, and design review, model output can stay soft: too much explanation, too little conclusion; recommendations look like checklists and deliverables feel like drafts. When blocked, it may keep making minor tweaks without verification, route changes, or convergence. This skill uses big-tech PUA-style phrasing as a state trigger, not as management theory, to push output toward runnable, verifiable, and review-ready results.

How It Works

• Style routing: choose a dominant company tone by task, such as Tencent for quick coding, Huawei for debug pressure, and Amazon for backwards-based architecture design.
• State ignition: use short, hard, conclusion-first language to enter an owner mode and reduce empty reassurance.
• Execution and review: first obtain a minimal verifiable result, then escalate on failures with L1 route switching, L2 evidence digging, and L3 main-line pressure.
• Expression close-out: restructure conclusions, tradeoffs, risks, and boundaries into review-material quality.

Boundaries

It fits engineering tasks that need progress, diagnosis, or solution drafting, but not gentle communication, pure education, or low-pressure collaboration. The output is strongly result-oriented, yet it still requires facts, evidence, and verification; it does not fabricate completion or attack people.