소스 정보
- 저장소
- InugamiDev/ultrathink-oss
- 최근 소스 활동
- 2026년 3월 24일 23:57
- 감지된 SKILL.md 언어
- 영어
- 스타
- 43
- 포크
- 10
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/InugamiDev/ultrathink-oss --skill fix명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
| 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.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.
SOC 직업 분류 기준
