2,665 件 ・ 関連度順
概要と使いどころ
Think like Fable 5 — natural, flowing, purposeful reasoning distilled from 4,665 real chain-of-thought traces with mathematical precision. Use this skill EVERY TIME before writing code, making decisions, or taking action.
日本語の概要は準備中です。原文の説明を表示しています。
Show or set NeatContext routing to auto, ask, or manual for Codex, with an optional default shared with every other NeatContext host. Use only when the user explicitly invokes this skill or clearly asks to change routing behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
日本語の概要は準備中です。原文の説明を表示しています。
Plan, order and deliver a batch of backlog items (e.g. every High item) in a Conventional Docs repo, one decision, branch, worktree, draft PR, review and merge per item. Use when asked to work through the backlog, implement all items of a priority, or sequence several backlog items end to end.
日本語の概要は準備中です。原文の説明を表示しています。
Scans CopilotKit's public product / pricing / Premium pages at the start of every weekly report to produce the authoritative list of COMMERCIAL surfaces (Premium · CopilotKit Enterprise · Intelligence Platform · paid tiers) and detect any newly-added or changed commercial feature since last week. This list defines what the report's 🏢 Enterprise section is about — CopilotKit's commercial/paid product, NOT "CopilotKit running inside an enterprise company." Emits the surface list + a free-vs-paid classifier the report uses to decide "does this issue hit a commercial surface?", plus a diff of what changed. Runs as a subagent (many web fetches) so the orchestrator's context stays small. Invoked by weekly-report (spawned at report start) and the enterprise skill; also triggers on "scan product surfaces", "what's premium", "commercial surfaces", "did we add a premium feature".
日本語の概要は準備中です。原文の説明を表示しています。
Generate the ≤10-minute Loom walkthrough script for a completed Weekly Community Signal report — a plain spoken briefing that dives straight into what the team needs to know, walking the report top to bottom (CopilotKit page first, then AG-UI in the same order). Straightforward and factual, NOT a radio show or a performance; no hype opener, no blame framing. Runs after every report (invoked by weekly-report) and on "loom script", "walkthrough script", "record the loom", "narrate the report".
日本語の概要は準備中です。原文の説明を表示しています。
Generate beautiful, on-brand HTML artifacts — reports, diagrams, diff reviews, slide decks, plans, recaps, dashboards. Loads on creation intents ("create a plan", "make me an implementation plan", "generate a diagram", "build a slide deck", "draft a recap", "visualize this", "render this as HTML", "make me a status update") and exploration intents ("show me three layouts", "explore document shapes", "compare visual treatments", "explore a new design system", "compare replacement brand directions") and iteration intents ("make this beautiful", "polish this report", "make this less generic", "design this", "theme this", "use my brand", "iterate on this design", "review this artifact", "make this bolder", "make this quieter", "simplify this design", "animate this", "improve the look of", "give this a refresh"). Captures brand from the user's codebase, asking, or live site, then applies it to every artifact.
日本語の概要は準備中です。原文の説明を表示しています。
TDD Test List Phase - Create a comprehensive test list covering every example and rule from the specification
日本語の概要は準備中です。原文の説明を表示しています。
Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.
日本語の概要は準備中です。原文の説明を表示しています。
Use for every progress update, status report, problem explanation, ETA, review, acceptance, or completion report to the operator/owner, especially when they ask “到哪了”, “什么问题”, “做了什么”, “结果呢”, “还要多久”, or “说人话”. Translate technical evidence into visible or operational outcomes before details.
日本語の概要は準備中です。原文の説明を表示しています。
Govern discovery, eligibility, and submission of a plugin or skill to official directories, registries, marketplaces, and curated GitHub lists. Use when preparing or sending plugin listings, marketplace forms, directory PRs, or repository recommendations; require current policy evidence and a final human confirmation before every external submission.
日本語の概要は準備中です。原文の説明を表示しています。
Session-start orientation for this team harness. Load first, before any work. Explains the operating contract, when each skill triggers, and how installed companion plugins supply agent-craft capabilities while this harness supplies the team contract. Trigger at the start of every session and whenever unsure which skill applies.
日本語の概要は準備中です。原文の説明を表示しています。
Use when shaping brand voice — voice attributes, tone-by-context matrix, consistency review. Triggers on 'define our voice', 'why does our copy sound different on every surface'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when stakeholders pull a decision in different directions — frames each lens, builds a trade-off matrix, surfaces the cost of every choice — even if the user just says 'PO and ops disagree'.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize prediction-pool tips (kicktipp etc.): rules + multi-book consensus odds → expected-points-max answer for every question, scores AND bonus. Triggers 'optimize my pool tips', 'predict'.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-spend contradiction gate for AI-video runs: checks every prompt in the batch, blocks on style / character / physics mismatch. Triggers 'validate the prompts', 'check the storyboard'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a diff needs a requirement review — does it satisfy every stated acceptance criterion — dispatched by /review-changes, /do-and-judge, /judge. Never infers criteria from the diff.
日本語の概要は準備中です。原文の説明を表示しています。
When setting up the legal pack — captures jurisdiction, role, escalation and playbook into a plain-prose profile every legal skill reads. Triggers on "set up legal", "legal profile".
日本語の概要は準備中です。原文の説明を表示しています。
Use BEFORE editing code that touches user data — traces the value from entry → validation → transformation → storage → egress, every hop cited with file:line.
日本語の概要は準備中です。原文の説明を表示しています。
Use BEFORE editing shared code — enumerates every call site, event consumer, queue worker, API client, migration, and test that a planned change will touch, with a file:line citation per dependency.
日本語の概要は準備中です。原文の説明を表示しています。
Development skill from everything-claude-code
日本語の概要は準備中です。原文の説明を表示しています。
Development skill from everything-claude-code
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill whenever the project contains HTML data tables (<table> elements). Under no circumstances use tables for layout purposes. Absolutely always include <th> elements with appropriate scope attributes, a <caption> or aria-labelledby, and ensure complex tables have headers associated with data cells. Apply these rules to every data table without exception.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill whenever the project uses Mermaid diagrams — flowcharts, sequence diagrams, class diagrams, Gantt charts, or any Mermaid-rendered visualization. Under no circumstances render a Mermaid diagram without an accessible title, description, and text-based alternative. Absolutely always add accTitle: and accDescr: (no %% prefix — that is the comment syntax and will be silently ignored) to every diagram.
日本語の概要は準備中です。原文の説明を表示しています。