Skip to content

zero-yx/static_flow / skills/tech-impl-deep-dive-writer

tech-impl-deep-dive-writer

Verified

Write mechanism-first technical implementation deep-dive articles for system/design/code explanations. Use when users ask for detailed implementation docs or engineering blog posts that must explain principles, data flow, trade-offs, and operations, and avoid source-location dumps or flashy/non-structured headings.

FileKindSize
SKILL.mdskill md3.3 KB
agents/openai.yamlconfig362 B
references/outline-template.mdmarkdown1.5 KB
references/style-contract.mdmarkdown1.6 KB

references/outline-template.md

View on GitHub
# Outline Template for Mechanism-First Deep-Dive

Use this template as a default structure.

## 1. Background and Goals
- State business/engineering context.
- State what cannot be solved by current observability/docs.
- Define scope and non-goals.

## 2. Model and Terminology
- Define entities and event objects.
- Define invariants and constraints.
- Define key terms once.

## 3. End-to-End Architecture
- Provide one global flow diagram.
- Explain component boundaries and responsibilities.
- Explain where data changes shape.

## 4. Core Mechanisms (repeat per mechanism)
### 4.x Mechanism Name
- Problem addressed
- Decision rationale
- Runtime execution path
- Failure modes and mitigation
- Verification signals

## 5. Query/Storage/Runtime Behavior
- Explain persistence model and write path.
- Explain query and aggregation path.
- Explain runtime controls and guardrails.

## 6. UI/Ops Integration
- Explain how users/operators consume the outputs.
- Explain drill-down workflow from overview to sample.

## 7. Trade-offs and Boundaries
- Provide at least one comparison table.
- State what the design optimizes for.
- State what the design does not solve.

## 8. Operations Playbook
- Add at least two concrete incident scenarios.
- For each scenario: symptoms -> filters -> correlation -> next action.

## 9. Code Index Appendix
- Group by subsystem.
- Keep compact; avoid turning appendix into the main body.

## 10. Summary
- Restate capability gains.
- Restate key limits.
- Suggest next evolution steps.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 197kUpdated Claude CodeCodexVerifiedInstall