aicodeking/deepseek-stack

ds-design

Builds a frontend with a clear visual direction instead of the generic AI look.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-design

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Build a UI that does not look like the default output for any similar prompt.

Steps

  1. Read the brief and the project. Find the subject, the audience, the one action you want the user to take, the stack, the existing brand, and the images you actually have. If the brief is vague, write down how you interpret it in one line and continue.
  2. Write a direction note of five lines or fewer before you write code. Include the purpose, the audience, the tone, the one memorable thing, and the mode (persuade, operate, or read). Take it from the subject's own world, not the usual look of its category.
  3. Define the tokens before you write components:
  • Type: a display font and a body font that are clearly different. Do not use a default font for display. Use a 5-7 step scale, body text of 16px or more, and lines under 80 characters.
  • Color: 4-6 named hex values. Use one dominant color for large areas and one sharp accent for actions only.
  • Use a 4px or 8px spacing base, one or two radius values, and one shadow style or none.
  1. Ask: "Would I make this plan for any similar prompt?" Change each part where the answer is yes.
  2. Lay out the page with intent. Choose a density: airy for persuading, compact for tools. Use asymmetry or scale contrast where it serves the content. Use real copy and plausible data. Do not use lorem ipsum.
  3. Use motion only where it does a job. Use one orchestrated reveal, plus feedback on user actions.
  4. Build every state: hover, focus-visible, disabled, empty, loading, error, and long content.
  5. Meet the accessibility floor. Contrast must be 4.5:1, focus rings must be visible, and fields must have labels. Touch targets must be at least 44px, images need alt text, and reduced motion must be respected.
  6. Take screenshots at about 1440px and 390px wide. Check them against the banned defaults and the direction note. Fix the problems in one batch, then take new screenshots. Remove one decoration that does no work.

Banned defaults

Use one of these only if the brief asks for it:

  • Purple-blue gradients and decorative gradient washes.
  • Inter, Roboto, or the system font as the display face.
  • Emoji used as icons. Use one set of SVG icons.
  • A centered hero with three identical cards below it.
  • Glassmorphism or glow on every surface.
  • Gray text on a gray background with low contrast.
  • Stock copy such as "Unlock your potential" or "Seamless".
  • All-caps eyebrow labels above every heading.
  • The same radius and soft shadow on every card.

Stop when

  • The direction note and the tokens exist, and the code uses the tokens.
  • The screenshots at both widths show no banned default and no horizontal scroll.
  • All the states are built and the accessibility floor is met.
  • The one memorable thing is visible in the screenshot.

Rules

  • When the brief specifies a font, color, or style, use it, even if it is on the banned list.
  • A refinement keeps the identity of the UI. A redesign keeps its content and function.
同じリポジトリから

関連する Skills

すべての Skills
aicodeking
コミュニティ

ds-adopt

Takes over an existing PR, branch or agent thread and finishes its original goal while keeping credit for the first contributors. Use when the user says take over, adopt, pick up or finish this PR, or /ds-adopt.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日
aicodeking
コミュニティ

ds-best-of-n

Run N independent attempts at the same task in parallel, pick the strongest as the base, and graft the best parts of the others into it. Use when one attempt at a non-trivial artifact could land on the wrong shape, or for /ds-best-of-n, 'try a few versions', 'best of 3'.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日
aicodeking
コミュニティ

ds-blast-radius

Find what a change could break outside its own diff, then prove the key safety fact by running real code. Use before shipping a risky or untrusted change, for 'what could this break', 'blast radius of X', or /ds-blast-radius.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日
aicodeking
コミュニティ

ds-blueprint

Design the types, function signatures and module layout first, agree on that shape, then implement against it. Use when work is non-trivial and coding straight away would lock in the wrong structure, or for /ds-blueprint, 'design this first', 'architect this'.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日