ワンクリックでManusで任意のスキルを実行

architecture-writer

スター4

フォーク0

更新日2026年7月14日 10:37

Generate or update docs/architecture.md with responsibility split, data ownership, data flow diagrams, API contract strategy, integration modes, and explicit non-goals. Load for "write architecture doc", "document system design", "create architecture diagram", "map data flow", or "define API contracts". Skip for minor code changes that don't affect architecture.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

InNoobWeTrust

InNoobWeTrust/dotfiles

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Architecture Writer

Produce or update docs/architecture.md from the real codebase — not generic templates.

Content	Path
Phases 1–6 detail	`references/phases.md`
Stop / deliverable / anti-patterns	`references/stop-deliverable-antipatterns.md`

Phase map

Discover existing architecture docs + code layout.
Responsibility split (who owns what).
Data ownership (tables/collections → services).
Data flow (ASCII diagram).
API contract strategy + sync.
Non-goals (explicit out-of-scope).

Hard rules

Prefer evidence from code over aspirational design.
Mark unknowns; do not invent services.
Ask before overwriting a substantially different existing doc.
Link domain terms to GLOSSARY.md when present.

このリポジトリの他の Skills

同じリポジトリ

codebase-exploration

InNoobWeTrust/dotfiles

Navigate and map large unfamiliar codebases. Find where behavior lives, trace feature flow and call chains, map architecture and dependency graphs, plan migrations/refactors, or answer "where is X" and "how does this work" questions. Also use for codebase scouting, hunting for specific patterns, discovering module relationships, or code archaeology. Activate on "find the code for", "how is X implemented", "navigate the codebase", "trace this", "map the architecture", or any task in an unfamiliar repo.

2026-07-154

memory

InNoobWeTrust/dotfiles

Human-inspired working + consolidated memory for agents, and the same progressive-disclosure pattern applied to docs and code. Two-tier store: unbounded short-term notes (working memory, per-branch session state, scratchpads) and size-limited long-term memory (curated facts, decisions, constraints, corrections) reached through an INDEX. A dream cycle runs on explicit request or git commit to consolidate hot short-term entries into long-term, score existing long-term entries, and propose evictions for human approval. Session checkpoints are one kind of short-term memory entry. Trigger phrases: 'remember this', 'save memory', 'checkpoint', 'save handoff', 'save context', 'what was I working on', 'resume', 'restore', 'load context', 'consolidate memory', 'dream cycle', 'prune memory', 'forget', 'evict', 'index my notes', 'structure docs', 'shard doc', 'split module', 'progressive disclosure'.

2026-07-154

multi-perspective-deliberation

InNoobWeTrust/dotfiles

Coordinate a multi-persona deliberation session to challenge assumptions, debate architectural decisions, and perform pre-mortems. Leverages concurrent delegated agents/workers when the environment supports them, or falls back to single-context simulated dialogue. Trigger phrases: 'party mode', 'deliberation', 'multi-perspective', 'get a second opinion', 'debate this', 'challenge design'.

2026-07-154

project-foundation

InNoobWeTrust/dotfiles

Bootstrap, audit, evolve, and materialize the AI-augmented project foundation (AGENTS.md, GLOSSARY.md, .agents/rules+skills core pack, Makefile, architecture, quality gates). Load for new project setup, missing skills after bootstrap, foundation drift, sync .agents from global, evolve AGENTS/GLOSSARY/architecture to match the repo, or audit project foundation. Skip only when editing a single existing rule/skill body with no pack-level change.

2026-07-154

reviewer

InNoobWeTrust/dotfiles

Multi-lens review orchestrator for code, specs, architecture, config, docs, and infrastructure. Hybrid execution: direct technical review using sub-reviewer references, or delegate to independent agents/workers for multi-perspective, audit, or specialized reviews. Sub-lenses: code-quality, design-rigor, adversarial, security, edge-case, editorial. Activate on "review", "check", "audit", "challenge", "QA", or any explicit review request.

2026-07-154

subagent-dispatch

InNoobWeTrust/dotfiles

Construct a precise, structured delegation prompt before every delegated-agent or worker launch. Use whenever you are about to delegate work to a background agent, run a task in parallel, or spawn a worker. Injects scope constraints, a structured output contract, obstacle reporting, and allowed-action boundaries directly into the input prompt to compensate for generic or unconfigured delegated-worker descriptions. Activate on: 'delegate this', 'run this in parallel', 'use the research agent', 'background task', 'spawn a worker', 'launch a subagent', 'hand this off'.

2026-07-154

name	architecture-writer
description	Generate or update docs/architecture.md with responsibility split, data ownership, data flow diagrams, API contract strategy, integration modes, and explicit non-goals. Load for "write architecture doc", "document system design", "create architecture diagram", "map data flow", or "define API contracts". Skip for minor code changes that don't affect architecture.

Architecture Writer

Produce or update docs/architecture.md from the real codebase — not generic templates.

Content	Path
Phases 1–6 detail	`references/phases.md`
Stop / deliverable / anti-patterns	`references/stop-deliverable-antipatterns.md`

Phase map

Discover existing architecture docs + code layout.
Responsibility split (who owns what).
Data ownership (tables/collections → services).
Data flow (ASCII diagram).
API contract strategy + sync.
Non-goals (explicit out-of-scope).

Hard rules

Prefer evidence from code over aspirational design.
Mark unknowns; do not invent services.
Ask before overwriting a substantially different existing doc.
Link domain terms to GLOSSARY.md when present.