用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/InugamiDev/ultrathink-oss --skill ut-remember命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
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 职业分类
正在显示 SKILL.md
| name | ut-remember |
| version | 1.0.0 |
| layer | utility |
| triggers | ["/ut-remember","remember this","save to memory","persist this"] |
| description | Explicitly save a memory to the UltraThink persistent brain |
| linksTo | ["ut-recall"] |
| linkedFrom | ["cook","plan"] |
| preferredNextSkills | ["ut-recall"] |
Save a specific piece of information to the UltraThink persistent brain. This is the manual override for the auto-memory system — use it when you want to ensure something specific is remembered.
/ut-remember <what to remember>
preference, decision, pattern, solution, convention, architecture, insight/tmp/ultrathink-memories/The Stop hook will automatically flush it to the database.
Write to /tmp/ultrathink-memories/<timestamp>-<short-slug>.json:
{
"content": "User prefers bun over npm for all package management",
"category": "preference",
"importance": 8,
"confidence": 1.0,
"scope": "global",
"tags": ["#preference", "#tooling"]
}
| Category | When to Use | Example |
|---|---|---|
preference | User explicitly states a preference | "Always use bun" |
decision | Architectural or tech choice made | "Chose Drizzle over Prisma" |
pattern | Recurring code/workflow pattern | "Uses barrel exports in /lib" |
solution | Bug fix or workaround found | "Fix: pgvector needs CREATE EXTENSION" |
convention | Project naming/structure convention | "Components use PascalCase" |
architecture | System design choice | "Microservices with event bus" |
insight | General observation | "Build takes 45s on this project" |
| Score | Meaning | Example |
|---|---|---|
| 9-10 | Critical — affects every session | "User is building a SaaS product" |
| 7-8 | Important — affects many sessions | "Always use TypeScript strict mode" |
| 5-6 | Useful — affects some sessions | "Project uses Tailwind v4" |
| 3-4 | Minor — occasionally relevant | "Prefers 2-space indentation" |
| 1-2 | Trivial — rarely needed | "Tested on Chrome 120" |
After saving, confirm briefly:
Saved to memory: "[content summary]" (category: preference, importance: 8)
Do NOT be verbose about it. One line is enough.