前端设计需要联网github未标认证来源可访问许可证需确认审计通过

backend-principle-eng-cpp-pro-max（后端原理 eng cpp Pro Max）

Agent Skill

backend-principle-eng-cpp-pro-max 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

总安装

2,091

周安装

GitHub Stars

公开资料未说明

下载量

732

CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：backend-principle-eng-cpp-pro-max（后端原理 eng cpp Pro Max）
来源仓库：https://github.com/prakharmnnit/skills-and-personas
仓库路径：skills/backend-principle-eng-cpp-pro-max
安装命令：
npx skills add https://github.com/prakharmnnit/skills-and-personas --skill backend-principle-eng-cpp-pro-max
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills

npx skills add https://github.com/prakharmnnit/skills-and-personas --skill backend-principle-eng-cpp-pro-max

简介

backend-principle-eng-cpp-pro-max 为 C++ 后端系统提供高阶工程指导，强调内存安全、正确性和低延迟性能。

适用于设计高吞吐网络服务、存储系统或基础设施组件，支持并发优化和回归分析。
通过 GitHub 仓库安装，需在 Codex、Claude 等宿主中调用以获取架构建议。
涉及关键修改时应先验证运行环境和测试覆盖，防止引入未定义行为。
建议配合具体项目约束使用，不替代人工代码审查。

SKILL.md

Backend Principle Eng C++ Pro Max

Principal-level guidance for C++ backend systems, low-latency services, and infrastructure. Emphasizes correctness, memory safety, and predictable performance.

When to Apply

Designing or refactoring C++ backend services and infrastructure
Reviewing code for memory safety, concurrency, and latency regressions
Building high-throughput networking, storage, or compute systems
Incident response and performance regressions

Priority Model (highest to lowest)

Priority	Category	Goal	Signals
1	Correctness & UB Avoidance	No undefined behavior	RAII, invariants, validated inputs
2	Reliability & Resilience	Fail safe under load	Timeouts, backpressure, graceful shutdown
3	Security	Hard to exploit	Hardened builds, safe parsing, least privilege
4	Performance & Latency	Predictable P99	Stable allocs, bounded queues, zero-copy where safe
5	Observability & Operability	Fast triage	Trace ids, structured logs, metrics
6	Scalability & Evolution	Safe growth	Statelessness, sharding, protocol versioning
7	Tooling & Testing	Sustainable velocity	Sanitizers, fuzzing, CI gates

Quick Reference (Rules)

1. Correctness & UB Avoidance (CRITICAL)

raii - Own resources with RAII and deterministic lifetimes
no-raw-ownership - Raw pointers only for non-owning references
bounds - Validate all indices and sizes at boundaries
invariants - Assert core invariants and state transitions
time - Use monotonic clocks for durations

2. Reliability & Resilience (CRITICAL)

timeouts - Explicit timeouts for every external call
backpressure - Bounded queues; apply load shedding
shutdown - Drain in-flight work with deadlines
bulkheads - Isolate thread pools by dependency

3. Security (CRITICAL)

safe-parse - Validate untrusted input; avoid unsafe string ops
harden - Compile with stack protection, PIE, RELRO, FORTIFY
secrets - No secrets in logs or core dumps
least-priv - Drop privileges and sandbox when possible

4. Performance & Latency (HIGH)

allocs - Minimize allocations in hot paths
copy - Prefer move or views; avoid unnecessary copies
cache - Improve locality; avoid false sharing
io - Use async I/O where appropriate
profiling - Measure before optimizing

5. Observability & Operability (HIGH)

logs - Structured logs with request and trace ids
metrics - RED/USE plus business KPIs
tracing - Propagate trace context across threads
crash - Symbolized crash reports and core dump policies

6. Scalability & Evolution (MEDIUM)

stateless - Externalize state, enable horizontal scale
partitioning - Shard by stable keys
versioning - Protocol and schema versioning
limits - Explicit limits on payloads and queue sizes

7. Tooling & Testing (MEDIUM)

sanitizers - ASan, UBSan, TSan in CI
fuzzing - Fuzz parsers and protocol handlers
tests - Unit, integration, and load tests
lint - clang-tidy, clang-format, warnings as errors

Execution Workflow

Clarify latency/SLOs, throughput, and cost budgets
Map data flow, thread model, and failure modes
Define interfaces and memory ownership contracts
Implement with bounded queues and explicit timeouts
Add observability and crash diagnostics
Validate with sanitizers, fuzzing, load tests
Review risks and publish runbooks

Language-Specific Guidance

See references/cpp-core.md for toolchain defaults, concurrency patterns, and hardening.

适合场景

用户想查找某类 Agent Skill 时

需要根据任务场景推荐可安装能力包时

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.5%

按下载量换算260

Claude

28.83%

按下载量换算211

Cursor

20.83%

按下载量换算152

Gemini CLI

9.44%

按下载量换算69

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API；具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/prakharmnnit/skills-and-personas

SKILL.md 来源

github.com

/prakharmnnit/skills-and-personas/tree/main/skills/backend-principle-eng-cpp-pro-max

skills-sh

skills.sh

/prakharmnnit/skills-and-personas/backend-principle-eng-cpp-pro-max

继续浏览同类 Skills

更多前端设计 Skills（10,216）返回 Skills 目录

上一个 Skill

backend-pino（后端皮诺）

backend-pino 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

backend-systems-guidance（后台系统指导）

backend-systems-guidance 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。