원클릭으로
coding-guardian
Enforce this repository's real React, Hono, Drizzle, and TypeSpec rules while editing code, docs, or tooling.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Enforce this repository's real React, Hono, Drizzle, and TypeSpec rules while editing code, docs, or tooling.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | coding-guardian |
| description | Enforce this repository's real React, Hono, Drizzle, and TypeSpec rules while editing code, docs, or tooling. |
この skill は、このリポジトリで実際に fail する規約と検証フローから外れないようにガードします。
AGENTS.md に従うCODING_STANDARDS.md と enforcement entrypoint を読むpackages/typespec/main.tsppackages/frontend/web や SvelteKit 前提を持ち込まないpnpm lint には OpenSpec validate と Scenario coverage check が含まれる最初に次を読む。
AGENTS.mdCODING_STANDARDS.mdCONTRIBUTING.md.opencode/skills/coding-guardian/references/repo-entrypoints.md特に重要な enforcement entrypoint:
package.json, .github/workflows/ci.yml, .husky/pre-commit, .husky/commit-msg, .lintstagedrc.json, commitlint.config.js, eslint.config.jspackages/typespec/package.json, packages/typespec/tspconfig.yaml, packages/typespec/README.md, packages/frontend/api/orval.config.tspackages/frontend/app/package.json, packages/frontend/domain/package.json, packages/frontend/ui/package.jsonpackages/backend/entry/package.json, packages/backend/app/package.json, packages/backend/http/package.json, packages/backend/persistence/package.json, packages/backend/usecases/package.json, packages/backend/domain/package.json, packages/backend/types/package.json, packages/backend/drizzle/package.json, packages/backend/http/src/contracts/openapi-contract.test.tsscripts/openspec/verify-scenario-coverage.mjspackages/typespec/**, packages/frontend/api/**packages/frontend/app/**, packages/frontend/domain/**, packages/frontend/ui/**packages/backend/**.opencode/**固定の依存方向:
packages/frontend/app -> packages/frontend/domain -> packages/frontend/api and packages/frontend/app -> packages/frontend/uipackages/backend/entry -> packages/backend/app -> (packages/backend/http | packages/backend/persistence | packages/backend/usecases) -> packages/backend/domain -> packages/backend/typespackages/backend/persistence -> packages/backend/drizzlepackages/typespec/main.tsp を直し、pnpm gen:api-sdk と pnpm check:codegen で整合を取るpackages/typespec/openapi/openapi.json と packages/frontend/api/src/generated/client.ts は手で直さないfetch, globalThis.fetch, axios, cross-fetch を直接使わない@repojiten/frontend-api を直 import しない。domain hook を経由するpackages/frontend/domain/src/hooks/** では use* export、{ data, actions } 戻り値、*Data / *Actions 型注釈を守る@repojiten/frontend-ui に寄せ、画面固有の構成だけを packages/frontend/app に置くpackages/backend/http、配線は packages/backend/app、永続化は packages/backend/persistence / packages/backend/drizzle に置くpackages/backend/http から packages/backend/persistence を直 import しない。c.env も HTTP 層で直接読まないpackages/backend/domain と packages/backend/usecases では adapter import や framework 依存を持ち込まないpackages/**/src/**/*.{ts,tsx} の export は、生成物とテストを除き TSDoc を付けるopenspec/specs/**/spec.md の Scenario ID とテストタイトルの参照を崩さない変更内容に応じて、少なくとも次を実行する。
pnpm gen:api-sdk -> pnpm check:codegenpnpm format:check -> pnpm checkpnpm lint -> pnpm test:runpnpm test:clientpnpm test:serverpnpm buildpython3 .opencode/skills/opencode-skills-devkit/scripts/validate_skills.py --root .Changed-file 向けの軽量チェック:
.opencode/skills/coding-guardian/scripts/check_changed.sh [base]packages/frontend/app から @repojiten/frontend-api の直 importfetch / axios / cross-fetch{ data, actions } を返さないpackages/backend/http から packages/backend/persistence の直 importc.env 直接参照Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Archive multiple completed changes at once. Use when archiving several parallel changes.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.