菜单
Enforce this repository's actual coding rules and verification flow (TypeSpec -> generated artifacts -> implementation). Use when writing, modifying, refactoring, or reviewing code in this repository.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup.
Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel."
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see page-cro.
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas.
| name | coding-guardian |
| description | Enforce this repository's actual coding rules and verification flow (TypeSpec -> generated artifacts -> implementation). Use when writing, modifying, refactoring, or reviewing code in this repository. |
この skill は、このリポジトリで実際に fail する規約と検証フローから外れないようにガードします。
AGENTS.md に従うCODING_STANDARDS.md と enforcement entrypoint を読むpackages/typespec/main.tspeslint-disable や inline config で逃げない）openspec/** は現在の default pnpm lint / hooks / CI の外。明示依頼があるときだけ触る最初に次を読む。
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/.spectral.yaml, packages/typespec/spectral/path-policy.js, packages/typespec/spectral/app-security.js, packages/typespec/spectral/bearer-scheme.jspackages/backend/.golangci.yml, packages/backend/tools/analyzers/cmd/guardrails/main.go, packages/backend/internal/adapter/http/product/router_test.go, packages/backend/internal/adapter/http/admin/router_test.go, packages/backend/internal/adapter/http/openapi_contract_test.go, packages/backend/internal/app/product_runtime_test.goscripts/go/lint.sh, scripts/go/format-check.sh, scripts/go/guardrails.sh, scripts/go/verify-module.sh, scripts/security/lint-security.sh, scripts/codegen/check.shpackages/typespec/**, packages/web/admin/api/src/generated/**, packages/backend/internal/generated/**packages/web/**packages/backend/**.opencode/**固定の依存方向:
packages/web/lp -> packages/web/ui + packages/web/i18n, packages/web/admin/app -> packages/web/admin/domain + packages/web/ui + packages/web/i18n, and packages/web/admin/domain -> packages/web/admin/apipackages/backend/cmd/api -> packages/backend/internal/app -> (packages/backend/internal/adapter/http | packages/backend/internal/adapter/postgres | packages/backend/internal/adapter/valkey | packages/backend/internal/adapter/webauthn | packages/backend/internal/adapter/mailer | packages/backend/internal/application | packages/backend/internal/platform/*) -> packages/backend/internal/domainpackages/backend/internal/generated/openapi を非 generated code から import できるのは packages/backend/internal/adapter/http だけpackages/typespec/main.tsp を直し、pnpm gen と pnpm check:codegen で整合を取るpackages/typespec/openapi/openapi.json、packages/web/admin/api/src/generated/client.ts、packages/backend/internal/generated/openapi/openapi.gen.go は手で直さない@app-template/web-admin-api を直接 import しないpackages/web で axios / cross-fetch を使わないuse* export、{ data, actions } 戻り値、stateful 実装は .svelte.tspackages/web/lp の SvelteKit route/server 制約と、独立オリジンで動く Admin app の分離を維持するpackages/backend/cmd/api, packages/backend/internal/*, packages/backend/tools/analyzers の許可 layer にだけ置くpackages/backend/internal/adapter/postgres/** だけ、AutoMigrate は禁止、migration は packages/backend/db/migrations/*.sql/health または /api/v1/* の string literal だけにするfmt.Print*, print, println と host-derived URL composition を backend code に入れない変更内容に応じて、少なくとも次を実行する。
pnpm gen -> pnpm check:codegenpnpm lint -> pnpm test:runpnpm buildpnpm format:check と pnpm checkpython3 .opencode/skills/opencode-skills-devkit/scripts/validate_skills.py --root .Changed-file 向けの軽量チェック:
.opencode/skills/coding-guardian/scripts/check_changed.sh [base]@app-template/web-admin-api の直 importpackages/web での axios / cross-fetchpackages/web/admin/app への SvelteKit server route / server hook / server-only lib の持ち込みAutoMigrate、migration pair 破れpackages/backend/internal/adapter/http から packages/backend/internal/adapter/postgres / packages/backend/internal/adapter/valkey の直 importfmt.Print* や host-derived URL composition