Index of every page on this site: llms.txt
All skills
dominiktobureto avatar

/architecture-review

@9125e02
Run it yourself

Use for clean architecture, modular monoliths, hexagonal boundaries, service boundaries, data flow, dependency direction, ADRs, or large feature planning.

Use this Skill: https://skilld.dev/gh/dominiktobureto/awesome-grok-build/architecture-review

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈44 tokens for metadata: the name and description. ≈397 when used: this file.

Description uses 2.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈176 characters, or 2.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Architecture Review

Design the smallest architecture that can survive the next real change.

Grok Build Mode

  • Start in Plan Mode. Architecture work should not begin with edits.
  • Use subagents for parallel discovery:
    • domain: core entities, use cases, invariants.
    • data: persistence, schemas, migrations, ownership.
    • interfaces: APIs, UI boundaries, jobs, integrations.
    • risk: coupling, circular dependencies, deployment constraints.
  • Arena-style design: compare 2-3 architecture options and rank by reversibility, simplicity, and testability.
  • Human-in-the-loop: ask for approval before introducing new layers, packages, services, or dependencies.

Workflow

  1. Clarify the product/job-to-be-done.
  2. Map current modules and data flow.
  3. Identify constraints: runtime, team, deploy, scale, compliance.
  4. Propose options:
    • minimal change;
    • modular boundary;
    • larger redesign if justified.
  5. Recommend one path with migration steps.
  6. Define tests and observability needed.

Architecture Rules

  • Prefer modular boundaries over premature microservices.
  • Keep dependency direction explicit.
  • Put business rules where they can be tested without infrastructure.
  • Avoid abstract factories/layers unless they remove real coupling.
  • Write an ADR for major choices.

Example Prompts

Use architecture-review. Compare clean/hexagonal/modular approaches for this feature and recommend the smallest reversible plan.
Map the current data flow with subagents, identify coupling risks, and propose an ADR before edits.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts4mo3 checks · Risk SAFE
  • Gen Agent Trust Hub4mo

    The skill provides instructional guidelines for architectural reviews and system design. It does not execute code, access external networks, or handle sensitive credentials.

  • Socket4mo

    No alerts

  • Snyk4mo

    Risk: LOW · No issues

Signed by skilld at 9125e02. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 6 months ago
version
1.0.0
author
awesome-grok-build

README badge

README badge for dominiktobureto/awesome-grok-build/architecture-review