SuperAPI AI Directory

qjudge-architecture-owner

Coding & development

View repository

Updated 10-15 21:36

About this skill

QJudge Architecture Owner

Quick start

  • First read references/layer-boundaries.md to determine where the code belongs.
  • For new features or major refactoring, also read references/feature-workflow.md。
  • Do responsibility separation first, then do file moves or renames.

Responsibility boundaries (Owner Scope)

  • ✅ layer directory responsibilities (features/shared/core/infrastructure/...).
  • ✅ import direction and boundary exception strategy.
  • ✅ feature workflow(spec -> shared -> feature -> wiring)。
  • ❌ Do not define PR strategy (leave it to qjudge-github-workflow-owner)。
  • ❌ Do not define UI visuals and Carbon details (leave them to qjudge-ui-carbon-owner)。
  • ❌ Do not define container execution flow (leave it to qjudge-env-compose-owner)。

Core rules

  • The Core layer stays pure: no UI, no I/O.
  • Infrastructure is the only entry point for external I/O.
  • Shared does not depend on feature runtime details.
  • Feature only assembles the workflow for that domain.

Check commands (scripts provided by the quality skill)

  • node .codex/skills/qjudge-quality-gates-owner/scripts/lint-naming.js --root frontend/src
  • node .codex/skills/qjudge-quality-gates-owner/scripts/lint-architecture.js --root frontend/src

Reference documents

  • Layer boundaries:references/layer-boundaries.md
  • New feature flow:references/feature-workflow.md

Cross-skill handoff

  • If commit/PR/release is needed, switch to qjudge-github-workflow-owner。
  • If UI specifications and Storybook are needed, switch to qjudge-ui-carbon-owner。
  • If container environment execution is needed, switch to qjudge-env-compose-owner。

Portable notes

  • Portable core: clear boundaries + one-way dependencies + an explicit composition root.
  • QJudge specialization is only in path naming and lint rules; the concepts can be reused directly.