菜单
Architecture knowledge reference covering API design, security architecture, cloud-native patterns, caching strategies, message queues, and data security. Use when designing system architecture, APIs, or cloud-native infrastructure.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Code relationship graph and temporal intelligence via abyss CLI. Provides caller tracing, impact analysis, hotspot detection, and file-level context gathering. Agent automatically runs abyss before modifying code to check impact. Works with any agent that has shell access.
Checks code quality metrics including complexity, duplication, naming conventions, and function length. Use when running quality gates, reviewing code smells, or checking lint rules. Automatically triggered on complex modules or post-refactor.
End-to-end change-shipping closed loop for non-trivial work — research → proposal doc → phased guarded implementation → PR self-review → harden → merge. Use when taking a substantial change from idea to merged PR, when a task needs a written proposal before code, when implementing in reversible phases behind a guarded commit chain (assert + test + verify, all green before commit), or when self-reviewing your own PR. Complements automating-devops (which is the git/CI/release knowledge reference); this skill is the orchestration spine that sequences a change from zero to merged.
AI-automated hardware product pipeline: from requirements to manufacturable Gerber + compiled firmware + cross-platform app. Orchestrates system design, ESP-IDF firmware, KiCad PCB, UniApp client, and release packaging in a zero-human-touch flow.
KiCad EDA orchestration via kicad-mcp MCP server. Routes 17 tools for schematic creation, PCB layout, autorouting, DRC, and Gerber export. Enforces serialized PCB ops, library-first lookup, and autoroute-only routing.
Systematically reduce AIGC detection rates in academic papers (Chinese/English). Analyzes detection reports, identifies high-impact sections, applies multi-layer rewriting strategies preserving formatting/footnotes, and verifies results. Supports 维普/知网/Turnitin platforms.
| name | designing-architectures |
| description | Architecture knowledge reference covering API design, security architecture, cloud-native patterns, caching strategies, message queues, and data security. Use when designing system architecture, APIs, or cloud-native infrastructure. |
| user-invocable | false |
判断先于执行：决定「是否做 / 选什么 / 如何取舍」（栈、方案、架构、权衡）前，先读领域判断内核
skills/_kernel/backend/SKILL.md——它管 judgment，本秘典管 execution；冲突时以内核判断为准。
| 意图 | 秘典 | 核心 |
|---|---|---|
| API 设计 | api-design | RESTful、GraphQL、gRPC、OpenAPI |
| 安全架构 | security-arch | 零信任、IAM、威胁建模、合规 |
| 云原生 | cloud-native | 容器、K8s、Serverless、Service Mesh |
| 消息队列 | message-queue | Kafka、RabbitMQ、事件驱动、CQRS |
| 缓存 | caching | Redis、CDN、一致性、穿透/雪崩 |
| 决策点 | 选项 A | 选项 B | 判据 |
|---|---|---|---|
| 同步 vs 异步 | REST/gRPC 同步调用 | 消息队列异步 | 延迟敏感→同步；解耦/削峰→异步 |
| 单体 vs 微服务 | 单体(模块化) | 微服务 | 团队<5→单体；独立部署需求→微服务 |
| SQL vs NoSQL | RDBMS | MongoDB/DynamoDB | 强一致/关联→SQL；灵活 schema/高吞吐→NoSQL |
| 缓存策略 | Cache-Aside | Write-Through | 读多写少→Aside；写后即读→Through |
| API 风格 | REST | GraphQL | 资源型 CRUD→REST；复杂聚合/前端驱动→GraphQL |
| 事件架构 | 事件通知 | 事件溯源(ES) | 简单解耦→通知；审计/回溯→ES+CQRS |
SOLID: S单一职责 O开闭 L里氏替换 I接口隔离 D依赖倒置
分布式: CAP定理 | BASE最终一致 | 幂等设计
安全: 纵深防御 | 最小权限 | 零信任
扩展: 水平优先 | 无状态服务 | 数据分片