Menu
Implement a piece of work based on a spec or set of tickets.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create a GitHub pull request for the current branch with `gh`. Use when the user asks to open a PR, submit changes for review, or open a pushed branch for review.
Testing Roblox/Luau code with Jest Roblox. Use when writing tests, mocking functions, asserting values, or configuring test suites in Luau with Jest Roblox. NOT JavaScript Jest — uses .never instead of .not, jest.fn() returns two values, 0 is truthy.
Use when designing components, systems, or entity structures for jecs in Roblox. Use when deciding if data should be one component or multiple, when archetype transitions seem expensive, or when choosing entity members vs relationships.
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Use when building ECS-based games in Roblox with roblox-ts using jecs for entities, components, queries, and relationships
Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides.
| name | implement |
| description | Implement a piece of work based on a spec or set of tickets. |
| disable-model-invocation | true |
Implement the work described by the user in the spec or tickets.
Errors are programmer mistakes, not recoverable conditions. Never use custom
Error classes — roblox-ts compiles throw obj to error(table), which Roblox
shows as "Error occurred, no output from Luau." assert eagerly evaluates its
second argument, so use it only for plain strings; use error for interpolation:
assert(condition, "plain message");
if (!condition) {
error(`interpolated ${value}`);
}
Use /tdd where possible, at pre-agreed seams.
Run typechecking regularly, single test files regularly, and the full test suite once at the end.
Once done, use /simplify + /code-review to review the work.
Commit your work to the current branch.
Run /create-pr to create a PR for the work when done.