SuperAPI AI Directory

black-tortoise-agent-architecture-quality

Coding & development

View repository

Updated 10-15 10:21

About this skill

Black-Tortoise Agent Architecture & Quality Skill

When to use

  • When conducting an architecture/design review or refactoring, the layers and quality guidelines need to be confirmed.
  • Structural sanity check before a PR, focusing on high-risk violations (cross-layer dependencies, fat interfaces, duplicated abstractions, RxJS state).

Work steps (minimized)

  1. Locate the specification: according to docs/INDEX.md read the corresponding AGENTS.md / README.md, locking down layer boundaries and prohibited items.
  2. Decompose/order:sequentialthinking/* list the review items and priority order in a single pass.
  3. Verify:
    • API/framework:context7/*(resolve → get docs in one round).
    • CLI/schema:angular-cli/*。
  4. Quality scan: when necessary codacy/* retrieve critical/high-priority issues.
  5. Judgment principles:
    • High cohesion, low coupling; single responsibility; minimal interface exposure.
    • Occam's razor: remove redundant abstractions/layers; avoid over-configuration.
    • Signals-first; no RxJS state; prohibit as any。
    • Unidirectional layers: Presentation → Application → Domain → Infrastructure.
  6. Output:
    • Assumptions/risks → issue list (with file links) → minimal fix steps → verification suggestions (lint / architecture:gate / tests).

MCP loop prevention

  • For the same topic, call the same MCP only once; stop when there is no new information.
  • context7:resolve-library-id → get-library-docs complete in one pass.
  • Software-planning-mcp: use only when a plan update is needed start_planning / save_plan once.
  • sequentialthinking: use for initial decomposition/ordering, do not re-enter within the same step.
  • Do not nest or recurse agent/runSubagent。

Prohibited items

  • Deep imports across capabilities, reverse dependencies, fat interfaces, duplicated abstractions.
  • Introducing RxJS state management or as any。
  • replacing minimal fixes with a "big rewrite"; deletability must not be broken.

Example input

  • "Review the recent changes to the overview capability, list high-coupling points and minimal fixes"
  • "Refactor the tasks store to ensure Signals-first and reduce interface exposure"