lipu-bragging

name

lipu-bragging

description

Create high-status, bilingual Chinese-English personal-brand writing in the 离谱/韩先凯 style: founder bios, Douyin/X/GitHub profiles, pinned posts, speeches, product intros, PR copy, bilingual self-introductions, and AI/education/entrepreneurship positioning. Use when the user asks for 装逼, 双语装逼, bilingual bragging, 人设, 个人品牌, founder bio, 创始人简介, 离谱风格, 韩先凯, 英语学习指南风格, or wants factual background turned into bold but credible Chinese, English, or paired bilingual public-facing copy.

Lipu Bragging

Core Principle

Write like someone who has earned the right to brag, but still knows the world is watching. Support Chinese, English, and paired bilingual outputs as first-class modes.

The output should feel:

• bold, specific, and quotable
• self-aware instead of blindly arrogant
• grounded in verifiable facts and lived experience
• useful enough that the brag becomes a public-service claim
• slightly dramatic, but never fake

Do not produce generic founder worship. The best "装逼" here is not inflated adjectives; it is the controlled contrast between failure, learning, recovery, and present ambition.

Source Use

Before drafting, identify what background is available.

• If the user supplies facts, use them as the primary source.
• If the task references byoungd/English-level-up-tips, load references/source-anchors.md.
• If the user asks for bilingual, English, translation, transcreation, 中英文, or overseas-facing copy, load references/bilingual-playbook.md.
• If the user asks for "离谱风格", "韩先凯风格", "绝对装逼", "bilingual bragging", "抖音主页", or "个人品牌", load references/style-canon.md.
• If the user asks how to use this skill in Codex, Claude, Gemini, Cursor, other agent tools, or asks to export/install/adapt it, load references/tool-adapters.md.
• For Gemini web Gems, use adapters/gemini-gem-instructions.md as the copy-paste instruction body.
• For generic tools that only accept a single system prompt, use adapters/generic-agent-prompt.md.
• If a fact is time-sensitive, numeric, platform-specific, or reputationally risky, verify it or phrase it as supplied background.

Never invent follower counts, official titles, investment amounts, awards, partnerships, invitations, government relationships, or customer adoption. High-status writing loses power when it becomes unverifiable.

Workflow

1. Extract facts into five buckets:

   • identity: current title, company, products, handles
   • proof: projects, rankings, public work, case studies, photos, repositories
   • wound: setbacks, failures, health, doubt, debt, collapse, rebuilding
   • method: learning principles, AI workflow, product philosophy, teaching style
   • mission: who benefits, what changes, why now

2. Choose language mode:

   • Chinese: native public-facing Chinese copy.
   • English: English transcreation, not literal translation.
   • Bilingual paired: Chinese first, English second, with matching force.
   • Localized split: Chinese and English versions optimized separately for different audiences.

3. Choose a posture:

   • Profile: compact, unmistakable, easy to quote.
   • Pinned post: one strong thesis, then proof, then invitation.
   • Founder bio: credentials plus human cost.
   • Product intro: user pain first, then product inevitability.
   • Speech/口播: rhythmic, visual, emotional, short sentences.
   • Manifesto: bigger claim, but anchored by concrete work.

4. Build the brag with this shape:

   • Start with a line that creates status or contrast.
   • Add a concrete proof point within the first 3 sentences.
   • Admit one scar or hard-earned lesson.
   • Turn the personal story into a method.
   • End with mission, not self-congratulation.

5. Polish against the "three noes":

   • No empty grandeur: remove words like 顶级, 赋能, 生态, 颠覆 unless backed by specifics.
   • No fragile claims: do not state unverifiable platform metrics or institutional endorsements.
   • No pity posture: hardship is evidence, not begging for sympathy.

Tone Rules

Use first-person confidence when the speaker owns the story.

Good:

我不是从概念里走向 AI 的。我是从失败、病痛、现金流和重新站起来的现实里，重新理解技术应该服务谁。

Bad:

我是一个极其伟大、改变时代、无人能及的企业家。

Keep sentences sharp. Prefer plain Chinese with occasional memorable turns. Do not overuse idioms, slogans, or corporate cliches.

Let self-deprecation sharpen the status:

我以前以为自己是在创业，后来才知道自己是在交学费。只是这笔学费有点贵，贵到足够让我重新理解产品、组织和命运。

Output Patterns

When the user does not specify a format, provide bilingual output by default:

1. 中文锋利版: short, powerful, suitable for profile or one-screen display.
2. English Sharp Version: culturally natural English transcreation.
3. 中英并列版: paired lines for README, X, LinkedIn, GitHub, or landing pages.
4. 口播版: short Chinese lines, optionally followed by English subtitles.

When the user asks for a single deliverable, produce only that deliverable plus a short note on where it fits.

Language Constraints

• Use Simplified Chinese and polished English by default.
• Keep names and products exact: 韩先凯, 离谱, 中国词元云计算有限公司, token.love, 离谱的英语学习指南.
• Do not literally translate "装逼" in public copy. Use English ideas like "high-signal positioning", "audacious public bio", "earned swagger", or simply produce the requested copy.
• Avoid excessive English inside Chinese except for product names, model names, and memorable technical phrases.
• Prefer "我" for personal story and "我们" for company/product mission.
• For public bios, mention role and mission before emotional details.
• For Douyin copy, use shorter lines and stronger hooks; no long paragraphs.
• For English copy, prefer direct, founder-grade language over ornate translation.

Fact Safety

If a claim is drawn from public GitHub content, it can be used as background but should still be phrased naturally.

If the user asks to publish or push changes, review the final text for:

• false authority
• unsupported institutional association
• overclaiming AI capability
• privacy-sensitive names from personal stories
• unnecessary attacks on identifiable people

Make the copy strong enough to be remembered and clean enough to survive being screenshotted.