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

始める

explain-arch

スター3

フォーク0

更新日2026年2月8日 03:41

Explain how a specific part of the lifelog architecture works with diagrams and data flow

インストール

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

Manusで実行

ソース

MattHandzel

MattHandzel/lifelog

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

ダウンロード

Manusで実行

関連職種SOC

SOC 職業分類に基づく

ソフトウェア開発者コンピュータ・数学職·SOC 15-1252

SKILL.md

readonly

name	explain-arch
description	Explain how a specific part of the lifelog architecture works with diagrams and data flow
context	fork
agent	Explore

Explain how $ARGUMENTS works in the lifelog system.

Find relevant code: Search for the component/feature across the codebase
Draw a data flow diagram: Use ASCII art showing how data moves between components
Trace the path: Walk through the code step-by-step, referencing specific file:line locations
Key types: List the important structs, enums, and traits involved
Connection points: Where does this interact with other parts of the system? (gRPC boundaries, DB calls, proto types)
Gotchas: What's non-obvious or could trip someone up?

Keep the explanation practical. Reference specific code, not abstractions.

このリポジトリの他の Skills

同じリポジトリ

db-inspect

MattHandzel/lifelog

Inspect the PostgreSQL schema, tables, and data for a running lifelog instance

2026-03-233

commit-changes

MattHandzel/lifelog

Validate, stage, and commit current changes with a conventional commit message

2026-02-083

debug-build

MattHandzel/lifelog

Diagnose and fix build failures systematically

2026-02-083

explore-modality

MattHandzel/lifelog

Trace a data modality end-to-end from proto definition through collector, server, and storage

2026-02-083

fix-issue

MattHandzel/lifelog

Fix a GitHub issue end-to-end with tests and validation

2026-02-083

gen-test-data

MattHandzel/lifelog

Generate realistic test data fixtures for a data modality

2026-02-083

name	explain-arch
description	Explain how a specific part of the lifelog architecture works with diagrams and data flow
context	fork
agent	Explore

Explain how $ARGUMENTS works in the lifelog system.

Find relevant code: Search for the component/feature across the codebase
Draw a data flow diagram: Use ASCII art showing how data moves between components
Trace the path: Walk through the code step-by-step, referencing specific file:line locations
Key types: List the important structs, enums, and traits involved
Connection points: Where does this interact with other parts of the system? (gRPC boundaries, DB calls, proto types)
Gotchas: What's non-obvious or could trip someone up?

Keep the explanation practical. Reference specific code, not abstractions.