图像设计
- 作者仓库星标 1
- 许可证 MIT
- 作者更新于 实时读取
- 作者仓库 accounting-assistant
- 领域
- 通用
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 94 / 100 · 已通过审计
- 作者 / 版本 / 许可
- @hi-yuki-922 · MIT
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: i-bolder
description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases…
category: 通用
runtime: 无特殊运行时
---
# i-bolder 输出预览
## PART A: 任务判断
- 适用问题:通用任务拆解、检查和交付。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“MANDATORY PREPARATION / Context Gathering (Do This First) / Use frontend-design skill”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于通用任务拆解、检查和交付,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“MANDATORY PREPARATION / Context Gathering (Do This First) / Use frontend-design skill”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、执行终端命令、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件、执行终端命令;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件、执行终端命令。
先用一个小任务确认它会围绕“MANDATORY PREPARATION / Context Gathering (Do This First) / Use frontend-design skill”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: i-bolder
description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases…
category: 通用
source: hi-yuki-922/accounting-assistant
---
# i-bolder
## 什么时候使用
- 把通用方向的常用动作沉淀成 Agent 可调用的技能 适合处理通用任务拆解、检查、交付和复盘,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤;通常不需要额外…
- 面向通用任务拆解、检查和交付,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「MANDATORY PREPARATION / Context Gathering (Do This First) / Use frontend-design skill」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件、执行终端命令;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "i-bolder" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> MANDATORY PREPARATION / Context Gathering (Do This First) / Use frontend-design skill
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件、执行终端命令 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences.
MANDATORY PREPARATION
Context Gathering (Do This First)
You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone, and everything else that a great human designer would need as well.
Attempt to gather these from the current thread or codebase.
- If you don't find exact information and have to infer from existing design and functionality, you MUST STOP and STOP and call the AskUserQuestionTool to clarify. whether you got it right.
- Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST STOP and call the AskUserQuestionTool to clarify. clarifying questions first to complete your context.
Do NOT proceed until you have answers. Guessing leads to generic AI slop.
Use frontend-design skill
Use the i-frontend-design skill for design principles and anti-patterns. Do NOT proceed until it has executed and you know all DO's and DON'Ts.
Assess Current State
Analyze what makes the design feel too safe or boring:
Identify weakness sources:
- Generic choices: System fonts, basic colors, standard layouts
- Timid scale: Everything is medium-sized with no drama
- Low contrast: Everything has similar visual weight
- Static: No motion, no energy, no life
- Predictable: Standard patterns with no surprises
- Flat hierarchy: Nothing stands out or commands attention
Understand the context:
- What's the brand personality? (How far can we push?)
- What's the purpose? (Marketing can be bolder than financial dashboards)
- Who's the audience? (What will resonate?)
- What are the constraints? (Brand guidelines, accessibility, performance)
If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify.
CRITICAL: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos.
WARNING - AI SLOP TRAP: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the i-frontend-design skill before proceeding. Bold means distinctive, not "more effects."
Plan Amplification
Create a strategy to increase impact while maintaining coherence:
- Focal point: What should be the hero moment? (Pick ONE, make it amazing)
- Personality direction: Maximalist chaos? Elegant drama? Playful energy? Dark moody? Choose a lane.
- Risk budget: How experimental can we be? Push boundaries within constraints.
- Hierarchy amplification: Make big things BIGGER, small things smaller (increase contrast)
IMPORTANT: Bold design must still be usable. Impact without function is just decoration.
Amplify the Design
Systematically increase impact across these dimensions:
Typography Amplification
- Replace generic fonts: Swap system fonts for distinctive choices (see frontend-design skill for inspiration)
- Extreme scale: Create dramatic size jumps (3x-5x differences, not 1.5x)
- Weight contrast: Pair 900 weights with 200 weights, not 600 with 400
- Unexpected choices: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default)
Color Intensification
- Increase saturation: Shift to more vibrant, energetic colors (but not neon)
- Bold palette: Introduce unexpected color combinations—avoid the purple-blue gradient AI slop
- Dominant color strategy: Let one bold color own 60% of the design
- Sharp accents: High-contrast accent colors that pop
- Tinted neutrals: Replace pure grays with tinted grays that harmonize with your palette
- Rich gradients: Intentional multi-stop gradients (not generic purple-to-blue)
Spatial Drama
- Extreme scale jumps: Make important elements 3-5x larger than surroundings
- Break the grid: Let hero elements escape containers and cross boundaries
- Asymmetric layouts: Replace centered, balanced layouts with tension-filled asymmetry
- Generous space: Use white space dramatically (100-200px gaps, not 20-40px)
- Overlap: Layer elements intentionally for depth
Visual Effects
- Dramatic shadows: Large, soft shadows for elevation (but not generic drop shadows on rounded rectangles)
- Background treatments: Mesh patterns, noise textures, geometric patterns, intentional gradients (not purple-to-blue)
- Texture & depth: Grain, halftone, duotone, layered elements—NOT glassmorphism (it's overused AI slop)
- Borders & frames: Thick borders, decorative frames, custom shapes (not rounded rectangles with colored border on one side)
- Custom elements: Illustrative elements, custom icons, decorative details that reinforce brand
Motion & Animation
- Entrance choreography: Staggered, dramatic page load animations with 50-100ms delays
- Scroll effects: Parallax, reveal animations, scroll-triggered sequences
- Micro-interactions: Satisfying hover effects, click feedback, state changes
- Transitions: Smooth, noticeable transitions using ease-out-quart/quint/expo (not bounce or elastic—they cheapen the effect)
Composition Boldness
- Hero moments: Create clear focal points with dramatic treatment
- Diagonal flows: Escape horizontal/vertical rigidity with diagonal arrangements
- Full-bleed elements: Use full viewport width/height for impact
- Unexpected proportions: Golden ratio? Throw it out. Try 70/30, 80/20 splits
NEVER:
- Add effects randomly without purpose (chaos ≠ bold)
- Sacrifice readability for aesthetics (body text must be readable)
- Make everything bold (then nothing is bold - need contrast)
- Ignore accessibility (bold design must still meet WCAG standards)
- Overwhelm with motion (animation fatigue is real)
- Copy trendy aesthetics blindly (bold means distinctive, not derivative)
Verify Quality
Ensure amplification maintains usability and coherence:
- NOT AI slop: Does this look like every other AI-generated "bold" design? If yes, start over.
- Still functional: Can users accomplish tasks without distraction?
- Coherent: Does everything feel intentional and unified?
- Memorable: Will users remember this experience?
- Performant: Do all these effects run smoothly?
- Accessible: Does it still meet accessibility standards?
The test: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects."
Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable.
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核