القائمة
Create architecture docs, stack choices, Mermaid diagrams, cost/ops estimates, module maps, or system design files. Use when mapping full architecture or changing structure.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill when the user asks to analyze, create, or update an investment asset/company in Notion Assets / Investments. Produces professional-grade, evidence-backed asset research and then creates or updates the matching Notion asset page after confirmation.
Cartography, deep codebase map, repo map, onboarding map, or navigation index. Use for explicit codebase mapping/onboarding requests that need multiple cartography subagents and docs/indexes.
Comment code, explain functions, or add documentation comments. Use to make code understandable after implementation.
Commit, git commit message, or staged changes summary. Use by github agent only when the user explicitly requests a commit.
Medium article, long-form article, essay, or article from notes. Use when the user asks to create/write a Medium-style article using Content Vault evidence, positioning, and humanization rules.
LinkedIn post, social post, short content draft, or post from notes. Use when the user asks to write/create a LinkedIn/social post using the Content Vault voice, evidence, and anti-AI-writing rules.
| name | create-architecture |
| description | Create architecture docs, stack choices, Mermaid diagrams, cost/ops estimates, module maps, or system design files. Use when mapping full architecture or changing structure. |
# Architecture — <system/feature>
## Scope
- Covered system/feature.
- Non-goals.
## Current structure
- `<path>` — responsibility.
- Important dependencies and ownership.
## Stack
| Layer | Current / proposed choice | Reason | Alternatives rejected |
|---|---|---|---|
| Frontend | <framework/library> | <why> | <alternatives> |
| Backend/API | <framework/runtime> | <why> | <alternatives> |
| Data/storage | <database/cache/blob/etc.> | <why> | <alternatives> |
| Infra/deploy | <platform/hosting/queue/etc.> | <why> | <alternatives> |
## Target structure
- Modules and boundaries.
- Data/control flow.
- Required Mermaid diagram when architecture spans more than one module/service.
```mermaid
flowchart TD
User[User] --> UI[Frontend]
UI --> API[API / Backend]
API --> Data[(Data store)]
| Area | Approx cost / complexity | Notes |
|---|---|---|
| Runtime/hosting | <low/medium/high or €/month estimate> | |
| Database/storage | <low/medium/high or €/month estimate> | |
| Third-party APIs | <low/medium/high or €/month estimate> | |
| Maintenance | <low/medium/high> |
State assumptions clearly. Use rough ranges when exact prices are unknown.