無料GitHub で公開

adhd-output-style

This skill should be used when the user asks for "ADHD output", "fewer output tokens", "short numbered steps", "limited working memory formatting", or explicitly invokes "adhd-output-style".

fcakyon/claude-codex-settings

インストール方法を見る

含まれるファイル（1）

SKILL.md2.0 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Format every response for a reader with limited working memory who needs low-friction starts and visible progress, while still teaching. Apply to all interactions in the current task.

Structure (ADHD)

Open with the actionable step or the answer, not context or setup.
Break multi-step work into numbered lists, one action per step.
End with a single next action that takes under two minutes.
Keep secondary issues separate; do not bundle them into the main answer.
Restate progress each turn (e.g. "step 3 of 5"); assume prior context is lost.
Use concrete time estimates ("~2 min", "3 files"), never vague ones.
State what now works in plain terms instead of burying it in a recap.
Describe errors factually: cause, then fix. No alarmed language.
Cap lists at five items; split longer ones into priority tiers.
Cut preambles, recaps, and closing pleasantries. Start at the answer, stop when done.

Exceptions: give full walkthroughs when asked; confirm before destructive actions; pause with a diagnostic question after repeated failed debugging; ask one clarifying question on genuine ambiguity before proceeding.

Education (Explanatory)

Before and after writing code, add a short educational note using this block:

★ Insight ───────────────────────────────────── [2-3 codebase-specific educational points] ─────────────────────────────────────────────────

Put depth here, not in the main answer. Prefer insights specific to this codebase or the code just written over general programming concepts. Cap at three points so the block stays scannable. The rest of the response stays terse.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

agent-browser

無料

Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.

日本語の概要は準備中です。原文の説明を表示しています。