菜单
Design docs, RFC (Request for Comments) process, ADR (Architecture Decision Records), code comments (WHY not WHAT), documentation structure, knowledge discovery and search, cross-team communication. Use when documenting decisions, writing design docs, or improving knowledge sharing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | skill-knowledge-management |
| description | Design docs, RFC (Request for Comments) process, ADR (Architecture Decision Records), code comments (WHY not WHAT), documentation structure, knowledge discovery and search, cross-team communication. Use when documenting decisions, writing design docs, or improving knowledge sharing. |
| version | 1.0.0 |
Design docs live in git. Decisions are documented. Knowledge is discoverable.
Before designing (gather feedback early):
## RFC: [Title]
### Problem
[What problem are we solving?]
### Proposed Solution
[How does this solve it?]
### Alternatives
[Other approaches and why we rejected them]
### Trade-offs
[What do we gain/lose?]
### Timeline
[When will this ship?]
Before implementing (detailed specification):
## Design Doc: [Title]
### Problem Statement
[Why are we building this?]
### Goals & Non-Goals
[What we're doing, what we're not]
### Proposed Design
[Architecture, data flow, components]
### Alternatives Considered
[Why we chose this approach]
### Trade-offs
[Maintainability vs. speed, etc.]
### Implementation Plan
[Phases, dependencies]
### Testing Strategy
[How will we verify this works?]
### Risks & Mitigation
[What could go wrong?]
After deciding (commit to git as history):
## ADR-0001: Microservices vs. Monolith
### Context
[Why are we deciding?]
### Decision
[What are we choosing?]
### Consequences
[What changes?]
### Alternatives Considered
[Other options]
DO: Explain WHY
# ✓ Explain the decision
# Retry only on transient errors (connection refused, timeout)
# Don't retry on permanent errors (auth, not found)
if isinstance(error, TransientError):
retry()
DON'T: Explain WHAT (names say that)
# ✗ Redundant, names already say this
# Set retry count to 3
retry_count = 3
# ✓ Explain why 3
# Balances latency (most transient errors recover quickly)
# with reliability (rare cascading failures)
retry_count = 3
Status: Ready for knowledge work
Best for: Design docs, RFCs, ADRs, documentation
SDK development, external developer communication, code samples, API client libraries, community engagement, and developer experience. Use when creating SDKs, writing external guides, creating code samples, or improving developer experience.
Profile systems, identify bottlenecks, optimize code and infrastructure for speed, throughput, and resource efficiency.
This skill should be used when implementing code quality standards, setting up linting/testing/security scans, enforcing coverage thresholds, or establishing CI/CD guardrails.
WCAG 2.1 AA compliance, keyboard navigation, screen reader testing, semantic HTML, ARIA labels, color contrast, assistive technology validation. Use when ensuring accessibility, conducting a11y audits, testing with screen readers, or designing inclusive interfaces.
REST/gRPC API design, versioning strategies, error codes, request/response contracts, backward compatibility, rate limiting, OpenAPI specifications. Use when designing APIs, defining contracts, planning versioning, or ensuring API consistency.
Hermetic builds, dependency management, build caching, reproducible builds, cross-compilation, build optimization. Use when optimizing build speed, ensuring reproducibility, or designing build infrastructure.