architecture-refactor
Use for folder movement, layer boundaries, and domain/application/runtime/adapters refactors in Gantry.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use for folder movement, layer boundaries, and domain/application/runtime/adapters refactors in Gantry.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Operate the Symphony Forge harness: start tasks, save approved plans, record decisions, assumptions, and client sign-off, harvest the docs/context inbox, check gate status, and review proposed skills. Invoke when the user says "start a task", "save this plan", "record a decision", "harvest context", "is this PR ready", "harness status", "what now", "create a new app", "set up a new project", "show me progress", "show the board", "review the plan", or "/forge".
Operate the Symphony Forge harness: start tasks, save approved plans, record decisions, assumptions, and client sign-off, harvest the docs/context inbox, check gate status, and review proposed skills. Invoke when the user says "start a task", "save this plan", "record a decision", "harvest context", "is this PR ready", "harness status", "what now", "show me progress", "show the board", "review the plan", "create a new app", "set up a new project", or "/forge".
Gantry self-administration reference for current host runtime operations: CLI commands, settings.yaml runtime settings, .env credential keys, agent management, scheduler tools, memory tools, browser tools, diagnostics, and service control. Use when asked to manage Gantry itself.
Drives Gantry agent-chat tests through the local Control API session path and captures assistant responses. Use when testing an agent response, permission prompt, skill behavior, or runtime chat flow without needing Telegram UI rendering.
Use for tools, permissions, risky actions, sandbox, browser, and execution safety changes in Gantry.
Use for LLM, channel, browser, sandbox, credential, and external provider adapter changes in Gantry.
| name | architecture-refactor |
| description | Use for folder movement, layer boundaries, and domain/application/runtime/adapters refactors in Gantry. |
Use this skill when a task moves files, changes layer ownership, changes imports across domain, application, runtime, or adapters, or updates architectural boundaries.
docs/architecture/codebase-refactor-principles.md, docs/architecture/codex-harness.md, and relevant docs/decisions/ records before editing.domain provider-free and channel-free. Keep provider SDKs, channel SDKs, Postgres, CLI, HTTP, browser, and sandbox implementations behind ports or adapters.gantry-change-contract when the refactor needs a Surface Impact Matrix, cleanup search, or no-legacy handoff evidence.scripts/architecture-map.json only when the desired ownership model changes, not to hide current debt.python3 scripts/check_architecture.py before final handoff when possible.