architect-officer

Name: architect-officer
Availability: InStock
Author: sahajamoth

Analyze architectural decisions to surface design and dependency issues in multi-crate Rust projects.

Updated Aug 23, 2026

Search Tags:#architecture #code-review #api-design #dependency-analysis #trait-design #cross-crate

Ready to run

npx skills add https://github.com/sahajamoth/apex --skill architect-officer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect-officer
Source: https://github.com/sahajamoth/apex/tree/main/.agents/skills/architect-officer
Command: npx skills add https://github.com/sahajamoth/apex --skill architect-officer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions frequently drift, introducing complexity and fragile APIs across crates. This skill provides a structured Architecture Review to surface design issues, API surface concerns, and cross-crate dependency risks before they become costly changes.

Core Features & Use Cases

Evaluate public API surface for minimal, intentional exposure and backward compatibility.
Assess cross-crate dependencies, trait design, and feature flag strategy to reduce coupling.
Provide concrete, file-referenced recommendations across a multi-crate workspace.

Quick Start

Provide an architecture review for the target project, focusing on API design, cross-crate dependencies, and potential refactor opportunities.

Frequently Asked Questions about architect-officer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I review cross-crate dependencies and API surface in a multi-crate Rust project?▼

Reviewing cross-crate dependencies in a Rust project involves evaluating the public API surface for minimal exposure and assessing trait design to reduce coupling. The skill provides file-referenced recommendations to enforce justified dependencies and backward compatibility.

What is the best way to minimize public API exposure and ensure backward compatibility across crates?▼

To minimize public API exposure, evaluate your API surface for intentional, minimal exposure and backward-compatible trait changes. The skill analyzes architectural decisions to surface design issues and enforce appropriate feature-flag usage.

Can I use this architecture review for feature flag strategy and trait design decisions?▼

Yes, this architecture review assesses feature flag strategy and trait design decisions across crates. It enforces constraints such as appropriate feature-flag usage and backward-compatible trait changes to reduce coupling.

How do I get concrete recommendations for refactoring fragile APIs in a Rust workspace?▼

To get refactoring recommendations for fragile APIs, provide the target project for an architecture review. The skill analyzes architectural decisions to surface design issues and potential refactor opportunities with file-referenced recommendations.

When do I need an architecture review for cross-crate dependencies?▼

You need an architecture review when architectural decisions drift and introduce complexity or fragile APIs across crates. The skill surfaces design issues, API surface concerns, and cross-crate dependency risks before they become costly changes.