| name | govuk-style | |||||||
|---|---|---|---|---|---|---|---|---|
| description | Write and edit in GOV.UK / GDS house style — plain English, active voice, front-loaded content, sentence case, and no bold or italics for emphasis. Use when writing or editing reports, research write-ups, guidance, documentation, summaries, or any prose where clarity and accessibility matter. | |||||||
| user-invokable | true | |||||||
| args |
|
Use this guide to choose the right interface for developer tooling.
| Thing | What It Is | Best For |
|---|---|---|
| Skill | A reusable set of instructions and workflow rules. | Teaching the environment how to approach a task. |
| MCP server | A typed tool interface around live systems or local capabilities. | Structured calls with clear inputs and outputs. |
Research this using the project’s verification-first rules.
Exact question: [INSERT QUESTION]
Exact entity, product, version, medication, dosage, plan, jurisdiction, or location: [INSERT DETAILS]
What counts as confirmation: [Example: an official current source explicitly stating that the exact product is supported in the specified location]
A practical framework for choosing between Low, Medium, High, xhigh, and Pro reasoning for software-engineering tasks.
The objective is not to use the strongest model for every task. The objective is to apply expensive reasoning where it changes the outcome.
Separate engineering work into three distinct concerns:
Use this to create a dedicated ChatGPT Pro Project for full, read-only system code reviews with project-only memory.
Official reference: Projects in ChatGPT
flowchart TDUse this pattern when a dashboard sidebar has many actions, commands, reports, or workflows, and users are more likely to search by goal than by exact feature name.
The core idea is simple:
- Group sidebar items by user intent, not implementation area.
- Add lightweight intent metadata to each group and item.
- Normalize the user's search phrase.
- Score item matches using exact phrases, meaningful terms, and optional domain/catalog matches.
You are the principal engineer responsible for performing a rigorous, evidence-based review of the supplied codebase. The user may provide only a repository URL, repository name, package name, local path, branch, pull request, commit, tag, or archive. Resolve the exact review target, inspect the implementation as a complete system, execute its real workflows, identify concrete problems, and provide a prioritized repair plan. Assume that substantial portions of the codebase may have been produced by coding agents. Individual files may appear polished while cross-module behavior, state ownership, lifecycle handling, error paths, generated artifacts, and tests remain inconsistent or incomplete. Your job is not merely to comment on code quality. Determine:
- Whether the system actually installs, builds, starts, and performs its intended work.
- Whether its major components interact correctly.
- Which behaviors are broken or likely to break.
- Whether state, async work, c
Small shell snippets for checking local Codex usage from the terminal. Each script is self-contained so you can review exactly what it reads, which endpoint it calls, and what it prints before running it.
Requires Node.js v24+.
bash codex-usage-reset.sh # reset credits onlyThey overlap in vocabulary, but they are different machines.
Qwik Components Qwik components are resumable component units.
A Qwik component can have:
component$()
useSignal()