Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
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.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/InugamiDev/ultrathink-oss --skill fixThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Unified design foundations — design system architecture, tokens, component specs, visual principles, creative vision, figma integration, plus brand design system loader (66 real brands via DESIGN.md). Absorbs design, design-system, design-systems, design-principles, design-router, creative-vision, figma, design-md.
Render, summarize, and present markdown documents and structured content in multiple output modes
Ultra UI skill - combines Google's DESIGN.md spec (machine-readable design tokens) with the ui-ux-pro-max knowledge base (91 styles, 161 palettes, 73 font pairings, 161 products, 104 UX guidelines, 25 chart types). Generates lint-clean DESIGN.md files, validates token references and WCAG contrast, exports Tailwind/DTCG tokens, and diffs design systems version-over-version.
Based on SOC occupation classification
| name | fix |
| description | Apply targeted, verified fixes with minimal blast radius and rollback safety |
| layer | hub |
| category | workflow |
| triggers | ["/fix","fix this","apply the fix","patch this","correct this"] |
| inputs | [{"diagnosis":"Root cause analysis (from debug skill or user-provided)"},{"target":"Specific file(s) and location(s) to modify"},{"constraints":"Any constraints on the fix approach (backwards compatibility, no new dependencies, etc.)"}] |
| outputs | [{"changes":"List of files modified with descriptions of each change"},{"verification":"Results of post-fix verification"},{"regressionRisk":"Assessment of what might break"}] |
| linksTo | ["test","code-review","debug"] |
| linkedFrom | ["debug","cook","team","ship"] |
| preferredNextSkills | ["test","code-review"] |
| fallbackSkills | ["debug","refactor"] |
| riskLevel | medium |
| memoryReadPolicy | selective |
| memoryWritePolicy | selective |
| sideEffects | ["Modifies source code files","May modify test files","May run tests to verify"] |
Apply targeted, minimal, verified code fixes. This skill takes a diagnosed problem (typically from debug) and implements the smallest correct change that resolves it. The emphasis is on precision, safety, and verification -- not on improvement or refactoring.
A fix is not a feature. A fix is not a refactor. A fix changes the minimum code necessary to make the incorrect behavior correct.
Confirm the diagnosis -- Restate the root cause. If coming from debug, validate that the diagnosis is specific enough to act on. If the diagnosis is vague (e.g., "something wrong with auth"), send back to debug.
Identify the fix location(s) -- Determine exactly which file(s) and line(s) need to change. Read each file to confirm current state.
Design the minimal fix -- What is the smallest change that corrects the behavior?
Assess blast radius
Choose fix strategy:
Read the target file(s) completely (or the relevant sections for large files).
Apply the fix using the Edit tool with precise old_string / new_string replacements.
// TODO: [description of proper fix] commentIf multiple files need changes, apply them in dependency order (shared code first, then consumers).
Self-review the changes
Run relevant tests (if they exist)
Manual verification (if applicable)
test to add regression tests, or code-review for complex fixes.# Fix Report
## Root Cause
[One sentence restating the diagnosed issue]
## Changes Made
### [filename]
- **What changed**: [description]
- **Why**: [reasoning]
- **Lines affected**: [line range]
### [filename 2] (if applicable)
- ...
## Verification
- [ ] Self-review: Changes match intent
- [ ] Tests pass: [test command and result]
- [ ] Manual check: [what was checked]
## Blast Radius
- **Direct impact**: [what is directly affected]
- **Indirect risk**: [what might be affected]
- **Confidence**: High | Medium | Low
## Regression Risk
[What could this fix break? What should be watched?]
## Recommended Follow-up
- [ ] Add regression test via `test` skill
- [ ] Review via `code-review` skill (if high risk)
/fix Apply the fix identified in the debug report
/fix The getUserById function in src/lib/users.ts returns null instead of throwing NotFoundError when the user does not exist
/fix The date parsing is wrong in the invoice generator. Must maintain backwards compatibility with existing invoices.
/fix Typo in the error message on line 42 of src/app/api/auth/route.ts: "authenication" should be "authentication"
Diagnosis: UserList component crashes because API returns { error: "..." } without items field on failure.
Fix:
// Before
const items = data.items.map(...)
// After
const items = (data.items ?? []).map(...)
Plus add proper error handling:
if (data.error) {
return <ErrorDisplay message={data.error} />
}
const items = data.items.map(...)
Diagnosis: createOrder() does not include discount in destructured input.
Fix:
// Before
const { customerId, items, total } = input
// After
const { customerId, items, total, discount } = input
And ensure discount is passed to the database create call.
Diagnosis: CORS errors in production because allowed origins list does not include the new domain.
Fix: Add the domain to the CORS configuration, not to the code. This is a configuration fix, not a code fix.
debug. Blind fixes create new bugs.