القائمة
Use when adding or modifying system config definitions, system config schemas, or system config edit/render UI in Graft.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Repository-specific loop orchestrator for Graft multi-agent tasks. Use when one bounded task should run through repeated same-session serial worker-subagent rounds of `graft-multi-agent-task` under the default `topic-completion-loop` mode until the topic reaches `archive-ready`, becomes `blocked`, or no remaining batches stay in scope.
Repository-specific multi-agent coordination workflow for Graft. Use when the user explicitly wants subagent delegation, or when the current task cleanly splits into two or more disjoint slices across server, web, docs, or automation, and the main agent should keep ownership of review, validation, and final integration. `graft-boot` should assess whether this skill is justified before delegation starts.
Repository-specific workflow wrapper for Graft multi-agent tasks. Use when a task should be executed through `graft-multi-agent-batch`, and the slice may need `graft-task-closeout` plus `graft-commit` to finish with a safe handoff after validation.
Repository-specific end-of-task closeout workflow for Graft. Use when a task slice is ending and the agent needs to decide whether to emit only a next-step startup prompt or to commit the current validated slice first and then hand off safely. This is the default slice-end path for work started through `graft-boot`.
Manage reusable Graft AI-agent worktrees through guarded status, acquire, and release commands without treating directories or task branches as long-lived ownership.
Repository-specific Playwright browser workflow for inspecting, authenticating into, and interacting with the local Graft web UI. Use when Codex needs Graft browser screenshots, DOM text snapshots, login/auth verification with temp credentials, or simple click/fill/wait checks before normal web validation.
| name | graft-system-config-field-renderer |
| description | Use when adding or modifying system config definitions, system config schemas, or system config edit/render UI in Graft. |
Use this skill for changes that touch server system config definitions, config_schema JSON, OpenAPI/system-config
contracts, or web UI that edits or renders system config values.
Follow root AGENTS.md first. For cross-boundary work, read both server/AGENTS.md and web/AGENTS.md before
implementation.
config_schema as the first UI rendering authority.config_schema before using item.type; use item.type only as a fallback when schema is missing or unusable.x-i18n keys.Pick the editor from the effective schema first:
| Schema signal | Editor |
|---|---|
enum present | Select |
type: "boolean" | Switch |
type: "integer" or type: "number" | InputNumber |
type: "object" or type: "array" | JSON textarea |
type: "string" | Input |
If the schema is absent, malformed, or does not provide a usable type, apply the same table to item.type.
config_schema["x-i18n"] before reading schema fallback fields.x-i18n.titleKey for schema title, x-i18n.descriptionKey for schema description, and
x-i18n.placeholderKey for schema placeholder.x-i18n.enumLabels.<value>.labelKey and .descriptionKey over inline fallback copy.web/src/modules/<name>/locales/** boundary when keys are introduced.web/scripts/check-i18n-governance.ts through the documented validation entrypoint after changing schema copy or
locale keys.When changing web render or edit UI, query TDesign MCP with framework=vue-next before coding for every touched
component from the decision table: Select, Switch, InputNumber, Textarea, or Input.
Use only the needed MCP calls:
get_component_docs for props, events, slots, and supported usage.get_component_dom when style overrides, DOM assumptions, or selector work are involved.get_component_changelog only for upgrade or version-drift risk.Record the queried components and adoption decision in closeout. If the slice only changes server definitions, schemas, docs, or validation scripts, record TDesign MCP as not applicable.
Run the smallest validation that directly covers the slice:
graft validate backend --stage lint
when practical.cd web && bun run check or the narrow directly affected test command when the slice is small.cd web && bun run test:run scripts/check-i18n-governance.test.ts and
cd web && bun run lint:i18n when practical.Report any skipped validation command and the exact reason.