generic-automation-and-it/smooth-ai-stockanalysis / .agents/skills/create-hld
create-hld
VerifiedInvoke to author a High-Level Design (HLD) at discovery / prototyping phase. Design-only: delivers intent + spec for AI and humans to build against — no implementation plan, no code outside examples/. Trigger keywords: "HLD", "high level design", "design doc", "architecture design", "create a design". Also triggers on /create-hld.
| File | Kind | Size |
|---|---|---|
| AGENTS.md | markdown | 2.4 KB |
| SKILL.md | skill md | 6.5 KB |
| agents/openai.yaml | config | 360 B |
| assets/AGENTS.template.md | markdown | 1.3 KB |
| assets/LADR.template.md | markdown | 1.1 KB |
| assets/NFR.template.md | markdown | 1.1 KB |
| assets/README.template.md | markdown | 2.1 KB |
| assets/c4-context.template.md | markdown | 2.0 KB |
| assets/examples.README.template.md | markdown | 505 B |
| references/diagram-selection.md | markdown | 2.2 KB |
| references/status-vocabulary.md | markdown | 1.6 KB |
| scripts/hld-agents-rules.shexecutable | script | 3.3 KB |
| scripts/scaffold-hld.shexecutable | script | 4.7 KB |
assets/NFR.template.md
View on GitHub# NFR-01: <Attribute>
**Status:** Draft
<!-- One file per quality attribute (Security, Observability, Performance, Resilience,
Availability, Scalability, Compatibility, Operability, Compliance, ...). This NFR is a
horizontal concern spanning the whole HLD. Status lifecycle: Draft → Prototype → Accepted. -->
## Requirement
<The measurable target. Vague NFRs ("fast", "reliable") are forbidden — pick a number or
a binary assertion. e.g. "p95 added latency ≤ 25 ms on cache hit" / "Every internal call
carries a signed service token, never the caller's raw end-user credential".>
## Verification
<How this is proven. A mechanism, not a hope. e.g. "APM span between ingress and egress" /
"Integration test asserts 403 on missing token" / "Load test before prod".>
## Acceptance Criteria
- <Observable condition that means this NFR is satisfied — the definition-of-done.>
- <Another condition.>
## Applies To
<Which goals, containers, or flows this NFR cuts across. Reference README goals or
diagram containers by name — e.g. "Goal 1; the API-gateway container".>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |