Loading…
Capture a product's system architecture (the named components, the discipline that owns each, and the interfaces between them) as a reviewable block diagram in the twin before detailed design starts. Use when the user asks for a block diagram, a system breakdown, "what talks to what", an interface list or interface control table, or when a design flow phase requires a system_architecture deliverable.
define_system_architecture is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # define_system_architecture Turn the user's description of a product into a component and interface map a reviewer can check: every component named and owned b. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding define_system_architecture to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install FidelOdok/MetaForgeReview the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
# define_system_architecture Turn the user's description of a product into a component and interface map a reviewer can check: every component named and owned by a discipline, ever