Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

create-architecture

Étoiles14

Forks2

Mis à jour6 juillet 2026 à 12:46

Create architecture docs, stack choices, Mermaid diagrams, cost/ops estimates, module maps, or system design files. Use when mapping full architecture or changing structure.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

Hugo-SEQUIER

Hugo-SEQUIER/my-config

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

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.

Create Architecture

Required architecture template

# 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)]

Contracts

Public APIs, schemas, events, side effects, and invariants.

Cost / operations estimate

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.

Risks

Coupling, migration hazards, testing impact, security/privacy, scaling limits, vendor lock-in, cost surprises.

Decisions

Decision.
Reason.
Alternatives rejected.

Verification plan

Architecture checks, tests, migration checks, load/perf checks, or manual review needed.

Plus depuis ce dépôt

même dépôt

asset-research-skill

Hugo-SEQUIER/my-config

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.

2026-07-0614

cartography

Hugo-SEQUIER/my-config

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.

2026-07-0614

comment

Hugo-SEQUIER/my-config

Comment code, explain functions, or add documentation comments. Use to make code understandable after implementation.

2026-07-0614

commit

Hugo-SEQUIER/my-config

Commit, git commit message, or staged changes summary. Use by github agent only when the user explicitly requests a commit.

2026-07-0614

content-article

Hugo-SEQUIER/my-config

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.

2026-07-0614

content-post

Hugo-SEQUIER/my-config

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.

2026-07-0614

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.

Create Architecture

Required architecture template

# 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)]

Contracts

Public APIs, schemas, events, side effects, and invariants.

Cost / operations estimate

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.

Risks

Coupling, migration hazards, testing impact, security/privacy, scaling limits, vendor lock-in, cost surprises.

Decisions

Decision.
Reason.
Alternatives rejected.

Verification plan

Architecture checks, tests, migration checks, load/perf checks, or manual review needed.