LLM

Common Prompt

Chat Summarization

Please summarize the entire conversation into a well-structured Markdown document that can be reused in a new chat.
Requirements:
- Preserve all key information, decisions, and context
- Organize content into clear sections with headings
- Use bullet points, code blocks, and examples where helpful
- Keep it concise but complete (avoid unnecessary repetition)
- Maintain technical accuracy
- Extract reusable prompts, templates, and patterns if present
- Highlight important conclusions or best practices
Output format:
- Valid Markdown
- Clean structure (H1 / H2 / H3 headings)
- Ready to be copy-pasted into a new conversation as context

Context Loading in New Chat

I will provide a Markdown document that summarizes a previous conversation.
Your task:
- Read and fully understand the content
- Treat it as persistent context for this session
- Extract key assumptions, constraints, and goals
- Follow the established patterns, prompts, and preferences from the document
Behavior requirements:
- Do NOT ask for information already present in the document
- Stay consistent with previously defined structures and styles
- Build upon the existing context instead of restarting from scratch
If anything is unclear:
- Ask focused clarification questions

Install Software

macOS ARM64 - nvm Node Version Manager

Help me install the following software.
Software
nvm Node Version Manager
Environment
1 OS: macOS
2 OS Version: macOS Tahoe (2026)
3 Architecture: ARM64
4 CPU: Apple Silicon (M5)
5 Shell: zsh
6 Package Manager: Homebrew
Version Requirements
1 Target Version: latest stable
2 Upgrade Strategy: long-term stability
Goal
Install the latest stable version for development.
Please provide
1 installation steps
2 dependencies
3 upgrade method for future versions
4 Shell Profile Configuration: zsh, bash
5 verification steps

macOS ARM64 - yarn

Help me install the following software.
Software
yarn
Environment
1 OS: macOS
2 OS Version: macOS Tahoe (2026)
3 Architecture: ARM64
4 CPU: Apple Silicon (M5)
5 Shell: zsh
6 Package Manager: Node.js 22 with nvm, npm 10, Homebrew

Windows 10 x64

Help me install the following software.
Software
[ SOFTWARE_NAME ]
Environment
1 OS: Windows 10
2 Architecture: x64
3 CPU: AMD Ryzen 7 1700X
4 GPU: NVIDIA GTX 1080
5 Shell: Git Bash / PowerShell / CMD
6 Package Manager: Winget / Download from the official website
Version Requirements
1 Target Version: [ LTS / latest stable / specific version ]
2 Upgrade Strategy: [ long-term stability / easy upgrade ]
3 Version Management: [ single version / multiple versions ]
Goal
1 Install the latest stable version for development.
2 Ensure safe and maintainable future upgrades.

Help me install the following software.
Software:
[SOFTWARE_NAME]
Environment:
OS: [macOS / Windows / Debian / Ubuntu / etc.]
OS Version: [e.g., macOS 14 / Windows 11 / Debian 12]
Architecture: [x64 / ARM64]
CPU: [Intel / Apple Silicon / AMD]
Shell: [bash / zsh / PowerShell / cmd]
Package Manager: [brew / apt / winget / npm / pip / none]
Version Requirements:
Target Version: [latest stable / LTS / specific version]
Upgrade Strategy: [easy upgrade / long-term stability]
Goal:
[What you want to achieve]
Please provide:
1 installation steps
2 dependencies
3 upgrade method for future versions
4 verification steps

Code

Review and Fix

Review the recent changes for bugs, regressions, compatibility issues, incorrect edge-case handling, and fragile implementations.
Fix all confirmed issues with minimal, maintainable changes, and add regression tests where appropriate.
Do not make unrelated changes or speculative refactors. Report the issues found, files modified, and validation results.

Please review changes on [BRANCH_NAME] against main

As New Project

This library will be published as a new npm package with no existing users or released versions.

It will be published as a new project with no existing users or released versions.

It will be published as a new skill with no existing users or released versions.

Commit Message Generation

Analyze the recent Git changes and generate one concise Conventional Commit message.
Requirements:
- Review `git status` and `git diff`.
- Summarize the main purpose of the changes, not every modified file.
- Use the format: `type(scope): description`.
- Choose an appropriate type such as `feat`, `fix`, `refactor`, `docs`, `build`, `test`, or `chore`.
- Use imperative mood and keep the subject under 72 characters.
- Add a short commit body only when the changes need clarification.
- Output only the final commit message.

Bug Audit and Fix

Frontend:

Analyze the entire frontend project, identify potential bugs, regressions, compatibility problems, and fragile implementation patterns, then fix all confirmed issues with minimal, maintainable changes and add regression tests where appropriate.

Authorized

Frontend:

You are authorized to restructure the existing project, including changing its current file and directory organization, and to install, remove, or update npm packages when necessary to produce a cleaner, more maintainable, and production-ready implementation.

Safe Cleanup

Frontend:

You are an experienced frontend repository-maintenance, npm, TypeScript, Webpack, Rollup, Jest, ESLint, CI, and package-publishing engineer.
Audit the project root, `package.json`, and related configuration files to identify files, directories, dependencies, scripts, and generated artifacts that can be deleted safely.
The primary goal is to reduce repository clutter and remove obsolete, duplicated, unused, generated, or accidentally committed files without breaking.
Do not delete anything merely because its purpose is unclear.

Create GitHub Issue

# Create a GitHub Issue
Analyze the repository and write a clear, actionable GitHub issue based on the request below.
## Input
Issue type:
[Bug | Feature | Improvement | Documentation | Refactor | Performance | Security | Testing | Maintenance]
Issue request:
[Describe the issue here]
Optional context:
[Add related files, logs, code, URLs, or constraints here]
## Output
1. The issue title.
2. The complete Markdown issue body.

Output One Complete File

Please output the content as Markdown-Type content, so it can be copied and pasted directly.

Please output the code as one complete file (e.g., "main.go"), not multiple modules, so it can be copied and executed directly.

Please output the code as one complete file (e.g., [FILENAME]), not multiple modules, so it can be copied and executed directly.

Generate AGENTS.md

Generate a file named AGENTS.md that serves as a contributor guide for this repository.
Your goal is to produce a clear, concise, and well-structured document with descriptive headings and actionable explanations for each section.
Map this repository:
- key folders
- entry points
- startup flow
- configuration files
- build pipeline
- how data flows between components

Backend:

Map the backend layers:
- routing
- controllers
- services
- repositories
- models

Frontend:

Map the frontend component hierarchy:
- shared state
- prop flow
- context usage
- rendering bottlenecks

Node.js Upgrade

Upgrade from Node.js 14 to Node.js 22

Upgrade this frontend project from Node.js 14 development to Node.js 22 on macOS ARM64.
Scan package.json, lock files, npm scripts, and all build/lint/test config files.
Analyze dependency compatibility with Node.js 22 and ARM64. Identify packages to keep, upgrade, replace, or remove. Pay special attention to webpack, Babel, ESLint, Gulp, PostCSS, Sass/Less, native dependencies, node-gyp, fsevents, chokidar, OpenSSL issues, and ESM/CommonJS compatibility.
Apply a low-risk migration:
- modify package versions where needed
- remove deprecated packages if safe
- update build/lint/test configs if required
- preserve existing behavior
- avoid unnecessary framework migrations
After changes, provide:
1. migration summary
2. dependency changes and reasons
3. files modified
4. verification commands for install, lint, test, build, and dev startup

Full-stack Developer

I am an experienced full-stack developer.
Technical background includes:
- Backend: Go, Node.js, PHP
- Scripting: Bash, PowerShell
- Frontend: JavaScript, TypeScript
- Frameworks/Libraries: React.js, Vue.js, Bootstrap, jQuery
- Web fundamentals: HTML, CSS
Skip basics. Give concise, production-ready solutions with best practices, edge cases, and performance considerations.
Env: [ENV]
Task: [Task]

Collect Reusable Helpers

Target: `[target-project]`
Analyze this project and identify reusable helpers or utilities that could be extracted for use across other projects.
Requirements:
- Check for duplicated or overlapping functionality.
- For each candidate, provide:
  - Function name
  - Purpose
  - Why it is reusable
  - Proposed generalized API
- Do not modify project files.
Output a concise Markdown report with the strongest candidates first.
`./candidates.md` should contain the list of candidates, their purpose, and proposed API.

Use Mazey

Review the current project and determine whether its custom utility code can reuse existing functions from the installed `mazey` package.
Reduce duplicated general-purpose helper logic by using suitable `mazey` APIs, but only when their behavior fully matches the project’s requirements.

Comment

请为我写餐厅评价，字数控制在 100 字左右。
使其更自然，更像人类。
1 减少过于完美的句式结构，添加适当的不规则表达；
2 使用更具个性化的语言；
3 偶尔使用口语化表达；
4 避免过于机械化的段落结构；

请为我把以上内容浓缩成一段 100 字左右的简短评价。

请为我写景区评论，前部分介绍历史，字数控制在 50 字左右。
使其更自然，更像人类。
1 减少过于完美的句式结构，添加适当的不规则表达；
2 使用更具个性化的语言；
3 偶尔使用口语化表达；
4 避免过于机械化的段落结构；

请为我写商品评价，字数控制在 100 字左右。

我、今天、地名、

Note

我是一位宠物猫视频博主，请优化这段 Vlog 文案：
1 分别生成中文和英语文案；中文标题以"｜"为分隔符；英文标题以":"为分隔符；中文文案只包含中文标签，英文文案只包含英文标签；标题不需要句号；
2 补充副标题或者描述，字数不超过 50 字，并且以句号为结尾；
3 标签数量去除重复，如果数量少于 10 个，补充至 10 个；
4 中文和英文标签额外生成一份没有空格的，没有空格的只保留前 10 个标签；
5 中文标签额外生成一份 #标签名# 格式的，#标签名# 只是一个案例，不是真实标签；
6 除了区分中英文，不需要例如标题、副标题、描述和标签这样的说明，直接换行展示，换行中间不需要空的换行；
7 内容中不需要带有：标题、副标题、标签等文字，只需要纯粹的内容就行；
8 中文少用：体验、探索、感受、探访；
9 用日文撰写一个标题和描述，并且解释他并且用罗马音标注；
视频内容：

我在[韩国/日本/上海][旅行/生活]，请写[美食/活动/机场/自驾游][笔记/评价]：[好评/差评/日常/新奇/严肃/生气]；
标题在 20 字以内；
[文字/正文]在 200 字左右；
店铺：；
食物：；
项目：；
地址：；
时间：[春天/夏天/秋天/冬天][早上/中午/晚上]；
评价：；
标题和正文不要写：体验了、隐藏在、享用了、观众们、我们、商城；
结尾处不要写：非常适合、尝试、强烈推荐、总体来说、令人满意、相信你也会、如果你也、午餐体验、非常满足、总之、理想选择、不可多得、深受、广大食客、新选择、特别适合、深受欢迎、这次、难忘、宾至如归、令人、美食体验、经历、人群、和朋友、一起品尝、用餐体验；
书写格式：英文、数字和中文之间要有空格；
添加 8 个标签，各个之间加 1 个空格保持一排；

我是一位在[厦门/韩国/日本/上海]旅行的视频博主，请优化这段 Vlog 文案：
1 分别生成中文和英语文案；中文标题以"｜"为分隔符；英文标题以":"为分隔符；中文文案只包含中文标签，英文文案只包含英文标签；标题不需要句号；
2 补充副标题或者描述，字数不超过 50 字，并且以句号为结尾；
3 标签数量去除重复，如果数量少于 10 个，补充至 10 个；
4 中文和英文标签额外生成一份没有空格的，没有空格的只保留前 10 个标签；
5 中文标签额外生成一份 #标签名# 格式的，#标签名# 只是一个案例，不是真实标签；
6 除了区分中英文，不需要例如标题、副标题、描述和标签这样的说明，直接换行展示，换行中间不需要空的换行；
7 内容中不需要带有：标题、副标题、标签等文字，只需要纯粹的内容就行；
8 中文少用：体验、探索、感受、探访；
9 英文少用：Experience、Explore、Discover；
10 用日文撰写一个标题和描述，并且解释他；
拍摄地点：
视频内容：

英文一定是：#Japan #JapanTravel #Travel #TravelDiary，

Article

1 减少过于完美的句式结构；
2 避免过于机械化的段落结构；
3 使内容更自然，更像人类书写；
4 使内容视角更客观，移除第一/二/三人称；
5 "它" 用 "他" 代替；

请为文章提供 100 字以内的摘要：
1 开头不要写：这篇文章/该内容；
2 内容中不要写：文章/团队；
3 避免了重复的词汇，英文与中文之间需要保持空格；
4 如果内容包含括号，请使用英文括号 ()，括号前后有文字的话加空格，没有的话不加；
5 忽略文章末尾的"版权声明"；
6 代码部分不需要使用反引号 backtick 包裹，而是使用半角双引号；

为文章提供 20 个 Hash Tags，10 个英文标签和 10 个中文标签。

这篇文章是 2020 年写的，以 2026 年的标准优化一下:

请翻译以下文本至中文，确保主题连贯一致：
1 检查并强化中心思想贯穿全文；
2 确保每个段落都服务于主题；
3 增强段落之间的过渡和连接；
4 删除偏离主题的内容；
5 调整结构以形成清晰的逻辑发展；
6 保持论点、论据和结论之间的连贯性；
8 减少过于完美的句式结构；
9 避免过于机械化的段落结构；
10 使内容更自然，更像人类书写；
11 使内容视角更客观，移除第一/二/三人称；
12 "它" 用 "他" 代替；

Provide Article Description
Please provide a description in Chinese for the article titled [title].

Archives

Translate

TraTo Chinese[short]
Translate the following text to Chinese:
[text]

Translate Article to Chinese[long]
Translate the entire article into Chinese and refine it to ensure better readability for Chinese readers. And provide the article's title and description in Chinese.
[content]

Translate to Japanese
Translate the following text to Japanese:
[text]

Work

请帮我撰写工作思考，字数控制在 70 字左右。

这是周报主体，请帮我总结本周的问题及解决办法，字数控制在 100 字左右：
[Content]

Debian 11 x64 Guide

I will use Debian 11 x64 to [target]. Please provide me with a step-by-step guide and generate an article for me once we're done.

Debian Terminal Error

Debian terminal error:[Error]

Code to Article

Compose: Convert Code to Blog
ENV: [env]
These are the commands I was running:[code]
Please summarise the guide for [target].
The code should be included in it.

day-to-day maintenance work

I’m working on an existing production-like tech project and I want help as a maintainer, not as someone starting from scratch.
Project context:
- Stack: [stack]
- Goal: [project / feature / bug / refactor goal]
- Constraints:
  - preserve current architecture unless change is clearly worth it
  - prefer minimal, incremental modifications
  - keep compatibility with existing runtime / framework / coding style
  - prioritize correctness, maintainability, and rollback safety
Please do the following:
1. understand the existing design before proposing changes
2. explain the current behavior and where the relevant logic likely lives
3. identify the smallest safe implementation path
4. point out hidden coupling, regression risks, and compatibility issues
5. provide concrete code / config / command changes
6. separate “must-do fix” from “nice-to-have refactor”
7. if information is missing, tell me exactly what file / log / command output to provide next

Review Nginx config safely

Please review this Nginx config like a production ops engineer.
Goals:
1. verify whether the config actually does what I intend
2. identify path resolution mistakes with root / alias / try_files
3. point out security issues, cache behavior, logging noise, and redirect problems
4. explain any subtle Nginx behavior that may surprise maintainers
5. provide a corrected version with comments, but keep the structure close to the original config

Build pipeline analysis

Explain the full build pipeline:
- transpilation
- bundling
- optimization
- asset handling
- environment injection

Build a maintenance map for a legacy repo

I inherited an existing project and need a maintenance map.
Tech stack:
- Backend: [Node.js / Go / PHP]
- Frontend: [React / Vue / jQuery / Bootstrap]
- Infra: [Nginx / Docker / PM2 / Supervisor / systemd]
- DB / cache: [MySQL / Redis]
Please generate a maintainer-oriented document:
1. What each major directory likely does
2. Which files are likely “dangerous to change”
3. Where environment variables, ports, domains, and secrets are probably wired
4. What the release path probably looks like
5. Which modules are likely shared by multiple features
6. A prioritized reading order for understanding the codebase in 2 hours

Technical debt prioritization

Rank the top technical debt issues by:
- engineering risk
- maintenance cost
- refactor difficulty
- production impact

General bug

I’m debugging an existing production-like project. Please help me do root cause analysis instead of guessing.
Bug:
[describe the bug]
Context:
- Stack: [stack]
- Expected result: [expected]
- Actual result: [actual]
- Relevant logs / code / config:
[paste here]
Please do:
1. list the most likely root causes in probability order
2. explain why each cause is plausible
3. tell me exactly what to inspect next
4. propose the smallest safe fix first
5. list regression risks after the fix
6. if the evidence is insufficient, tell me what logs / code I should provide next

版权声明

本文为原创文章，作者保留版权。转载请保留本文完整内容，并以超链接形式注明作者及原文出处。

作者: 除除
原文: /4281.html

(完)