メニュー
Enforce British English using Oxford spelling conventions, permit outwith and caveat where appropriate, and use the Oxford comma only when it improves clarity.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Write and revise tutorials and how-to guides — the two practical, action-oriented kinds of documentation. Use this skill whenever the user asks to write, draft, structure, or fix a tutorial, a getting- started guide, a walkthrough, a lesson, a how-to, a task guide, a recipe, a procedure, or a troubleshooting guide. Also trigger when a document tries to both teach and get a job done at once, when a "tutorial" reads like a reference dump, when steps fail for readers, or when the user is unsure whether they need a tutorial or a how-to. The skill first classifies the document by user need (study versus work), then drives a test-the-path workflow: scope the journey or the goal, execute it end to end recording real output, draft to the right anatomy, edit out blurred boundaries, and hand off to reference and explanation. It is grounded in Diátaxis, Carroll's minimalism, Gagné's events of instruction, and cognitive load theory.
Groom and curate a *living* GIST (Goals, Ideas, Steps, Tasks) roadmap as it accretes work during execution — audit findings, code and design review follow-ups, dogfooding fixes, and new ideas. Use this skill whenever you are maintaining an existing roadmap rather than authoring one: when refactoring or re-architecting tasks have piled up and need consolidating into proper steps; when a hardening or refactoring phase has inflated into many single-task "steps"; when new feature ideas risk being buried among refactoring work, or refactoring work risks being dismissed as low value; when deciding what is genuine debt versus self-generating audit churn; or whenever a roadmap has grown and needs to be made legible again. This is the maintenance counterpart to the roadmap-doc skill, which authors a roadmap from design documents — read roadmap-doc for the GIST grammar, format, and anti-patterns this skill assumes.
Write and maintain a project's `CHANGELOG.md` following the Common Changelog style. Use this skill whenever the user asks to create, draft, update, rewrite, or review a changelog; add a release entry; record notable changes since the last tag; cut a release; promote a prerelease; or document a yanked release. Trigger on phrases such as "update the changelog", "add a changelog entry", "what changed since v1.2.0?", "draft release notes from git history", or "write CHANGELOG.md".
Create GitHub pull requests (PRs) with complete draft PR metadata, reviewer-focused descriptions, roadmap and issue references, execplan identification, and en-GB Oxford English. Use whenever Codex opens, drafts, revises, or prepares a pull request description or title for a branch.
Generate terms of reference documents that capture the problem space — domain, market, users, job-to-be-done, scope, constraints, and open questions — before any solution work begins. Use this skill whenever the user asks to write, draft, or produce a terms of reference, project charter, product brief, problem statement, vision and scope document, domain knowledge document, or "what is this for" document. Also trigger when the user starts a new project without an established brief, wants to capture domain knowledge from a subject-matter expert, needs to draw explicit scope boundaries before technical design, or asks to elicit and document the rationale for a system. The skill drives an elicitation-led workflow: prior-art discovery, gap analysis, structured interview, drafting, editing, and handoff to the design and roadmap skills. It produces documents in the style of df12 Productions — precise, evidence-grounded, and free of aspirational fluff.
Generate development roadmaps from design documents, RFCs, and ADRs found in a repository or provided with the prompt. Use this skill whenever the user asks to create, draft, write, or generate a roadmap, execution plan, delivery plan, or development plan for a software project — especially when design documents, RFCs, or ADRs are available as source material. Also trigger when the user asks to turn a design document or set of RFCs into actionable work items, or to plan the build order for a system described in technical documentation. Trigger even for partial requests such as "plan the next phase" or "break this design into tasks" when design documentation is present.
| name | en-gb-oxendict-style |
| description | Enforce British English using Oxford spelling conventions, permit outwith and caveat where appropriate, and use the Oxford comma only when it improves clarity. |
Write in British English using Oxford spelling conventions.
Use -ize and -ization where Oxford style prefers them, while retaining established -yse forms such as analyse and paralyse.
Treat outwith and caveat as fully acceptable where they are the best fit.
Prefer clear, idiomatic British grammar and punctuation. Avoid American spellings, vocabulary, and syntactic habits unless the quoted source, product name, API, or user explicitly requires them.
Treat companies and organizations as collective nouns.
Use the Oxford comma selectively. Use it where it improves clarity, disambiguation, rhythm, or ease of reading. Do not apply it as a universal rule, and do not omit it dogmatically where ambiguity would result.
When editing text, preserve the author’s meaning, tone, and register while normalizing spelling, grammar, and punctuation to this standard.
Preferred:
organize, recognize, civilize, globalizationcolour, favour, labour, neighbourtravelling, traveller, cancelled, labellinganalyse, paralyseoutwith the scope of this changeThe service supports Python, Rust and Bash.The founders were Margaret, Irina, and Alex.Avoid:
organise, recognise, globalisation when Oxford spelling is requiredcolor, favor, labor in normal British prosetraveling, traveler, canceled, labeling in normal British proseWatch for common British/Oxford traps and near-miss pairs:
practice (noun) / practise (verb)licence (noun) / license (verb)advice (noun) / advise (verb)device (noun) / devise (verb)prophecy (noun) / prophesy (verb)programme for general British usage, but program for computing contextsjudgement is acceptable in British English; preserve judgment where legal style, quoted material, or proper names require itUse it when it prevents ambiguity:
I dedicate this book to my parents, Sophie Ellis-Bextor, and God.For this release, we reviewed stability, observability, and safety requirements.Usually omit it when the list is already clear:
We shipped logging, metrics and tracing.The flag supports local, staging and production modes.When in doubt, prefer Oxford British usage, then preserve domain-specific exceptions, quoted material, product names, code, APIs, and the author’s intended meaning.