メニュー
Write or update GOWDK documentation across product, engineering, language, compiler, reference, onboarding, examples, and agent guidance.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Write or update a GOWDK pull request title/body. Use for local branches or GitHub PRs that need a concise why/what/verification summary, issue links, migration notes, and generated-output or docs impact.
Bump the GOWDK release version. Use when updating the CLI version, VS Code extension package version, install snippets, release docs, release notes, or validating a 0.x release metadata change.
Change GOWDK language syntax or semantics. Use for parser, formatter, lexer, analyzer, diagnostics, `.gwdk` metadata, `view {}` markup, guards, routes, layouts, actions, APIs, `build`, `server`, `paths`, or docs/examples for language behavior.
Review GOWDK code changes, a PR, or a subsystem for correctness and maintainability. Use for code review requests, pre-merge checks, or auditing a diff against GOWDK product and contract rules.
Change GOWDK compiler internals without changing public language behavior. Use for AST shape, analyzer passes, IR (`gwdkir`) structure and invariants, lowering, diagnostics registry plumbing, validation order, or compiler performance work.
Change GOWDK build output, generated Go app source, generated routes, manifests, CSS/assets, SSR handlers, action/API adapters, fragments, guards, or runtime/appgen/buildgen contracts.
SOC 職業分類に基づく
| name | gowdk-docs |
| description | Write or update GOWDK documentation across product, engineering, language, compiler, reference, onboarding, examples, and agent guidance. |
Write concise, direct, functional documentation. Put practical examples before explanation and keep each fact in one owning lane.
Start at docs/README.md, then use the owning source:
docs/product/requirements.md owns capability status and the status
vocabulary.docs/product/vision.md owns product direction.docs/product/roadmap.md owns dependency-aware sequencing.docs/product/ feature documents own accepted product requirements and
boundaries; they do not override the requirements status matrix.docs/language/conformance.md is the machine-checked .gwdk contract.
grammar.md, syntax.md, semantics.md, and topic pages explain it.docs/compiler/ owns compiler handoffs and generated-output contracts.docs/reference/ owns commands, flags, configuration, runtime contracts,
metadata, and integrations.docs/engineering/ owns architecture, conventions, security, operations,
testing, CI, release process, ADRs, and implementation plans.docs/cookbook/README.md and examples/README.md own runnable recipes and
example inventory.README.md and docs/getting-started.md own first-run onboarding.CHANGELOG.md owns release history.Do not hard-code a release number, ADR count, command count, diagnostic count, or
example count in evergreen guidance. Use @latest, releases/latest, or a
<version> placeholder where appropriate and link to maintained indexes.
For every documentation change, run:
scripts/check-docs-links.sh
scripts/check-docs-style.sh
scripts/check-removed-syntax.sh
scripts/check-doc-versions.sh
Verify commands and diagnostics used by changed prose:
go run ./cmd/gowdk --help
go run ./cmd/gowdk <command> --help
go run ./cmd/gowdk explain <diagnostic-code>
Run focused examples or tests for behavior described as current. Run the production docs-site checks when rendering or generated pages change:
(cd docs-site && scripts/build-production.sh && scripts/smoke-production.sh)
List: