overextended-skills

Plugin overextended-skills from marketplace overextended in overextended/skills. Commands read from the repo's manifest — 26 days ago.

Skills (21)

• deslop

  Remove AI-generated slop from FiveM resource code (Lua, TypeScript, JavaScript) without changing behaviour. Use when the user asks to deslop, clean up or tidy code an agent wrote, or after finishing a change to a resource and before it is committed.

• lua-best-practices

  Lua best practices for FiveM resources built on ox_lib, the way Overextended structures its own resources. Use when reading or editing any .lua file or fxmanifest.lua, or when the user asks when to use require, lib.load or lib.loadJson, how to split a resource into modules, where config goes, or how

• resource-best-practices

  FiveM resource defaults beyond security: entity spawning and network control, cleanup, loops, network traffic, state bags and SQL. Use when writing or reviewing a resource's client or server scripts, or when a resource doubles up after a restart, hitches, or floods the network.

• tdd

  Make a bug in a TypeScript resource executable before fixing it, with a regression test that fails before the fix and passes after. Use only when the user asks for TDD, a failing test, or a regression test, or when the resource already has a test runner and the bug has an obvious cheap test target.

• typescript-best-practices

  TypeScript best practices for FiveM resources and their NUI. Use when reading or editing any .ts or .tsx file or a .svelte file with <script lang="ts">, or when the user asks how to type net events, callbacks, exports, NUI messages or state bags.

• setup-ox

  Configure the Overextended skills. Picks which model and reasoning level each subagent role uses within a budget you choose, then detects your FiveM server, its ox resources and framework. Writes `~/.config/ox/models.md` and `.ox/config.md`, which the other ox skills read.

• architect

  Sketch types, signatures and module structure before writing code, from several candidate designs on different models, then implement against the chosen sketch. Use when the user asks to architect or design something, or when a skill such as figure-it-out calls for it.

• arena

  Run several candidates at the same task on different models, pick the strongest as the base, and graft the best parts of the others into it. Use when the user asks to arena something, or when a skill such as architect calls for it.

• figure-it-out

  Design and run a bespoke, auditable workflow for a task no narrower skill fits, such as a large migration, an ambitious multi-part change, or work the user reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions. Use when the user asks you to figure it out,

• how

  Explain how a resource or subsystem works, its runtime flow across client, server and NUI, and where things live, through read-only subagents. Use when the user asks how something works, where code should live or which layer owns it, or when a skill such as architect calls for it.

• interrogate

  Adversarial multi-model review of a change. Reviewers on different models challenge it independently, then a lead judgment sorts their findings into act on, consider, noted and dismissed. Use when the user asks to interrogate, stress test, adversarially review or tear apart a change, or when a skill

• no-comments

  Delete the comments in a diff that the code should make unnecessary, through a fresh read-only reviewer, then fix the code each deleted workaround comment was excusing. Use before a change goes to review, or when the user asks to strip comments from a diff.

• ox-mode

  Work in the Overextended style. Concise replies, deliberate subagents, simple code, and work verified before it's called done, routed through a playbook per task.

• pr

  Use when writing a PR body.

• principles

  Engineering principles for building, verifying and delegating work. Use when sizing or sequencing a change, designing data or types, debugging, deciding whether work is verified, trusting a measured number, or splitting work across subagents.

• retro

  Conduct a retrospective on a coding session.

• show-me-your-work

  Keep a reviewable decision trail, a TSV log with one row per decision (what, why, evidence, result), for long-running, unattended or multi-phase work. Use when the user asks for a decision trail or will review the work after stepping away, or when a skill such as figure-it-out calls for it.

• swarm

  Fan out parallel subagents over slices of a task, or race them on the same brief, then aggregate one report. Use when the user asks to swarm something, or when a skill calls for parallel coverage, races, gauntlets or exploration.

• unslop

  Cut AI tells from any writing.

• why

  Find why code is the way it is, through read-only investigators that search git history, PRs, issues and any docs or chat the agent can reach, then return a cited, confidence-weighted answer. Use when the user asks why something works this way, why a choice was made, where a number came from, or wha

• writing-for-agents

  Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Similar plugins