「should」の検索結果

Use when deciding 'should this be a skill or a rule?', creating/improving/reviewing agent skills, SKILL.md frontmatter, or procedure sections — even without saying 'skill-writing'.

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

Use when a learning, new skill, rule improvement, or bug fix from a consumer project should be contributed back to the shared agent-config package.

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

Use when reasoning about cash runway — burn shape, fundraise triggers, layoff-vs-cut-vs-grow decisions. Triggers on 'how long do we have', 'should we raise', 'cut or grow'.

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

Use when shaping team structure — functional vs squad, span-of-control, reorg cost, Conway-aware boundaries. Triggers on 'should we reorg', 'how do we split this team'.

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

Use when a diff builds more than the task needs — code that should not exist, a dependency the platform already covers, or a clever form where a flat one reads better. Deletion-hunting, not quality.

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

Use when sequencing market entry — geo / segment / vertical, beachhead selection, regulatory-delta. Triggers on 'should we enter market X', 'which segment first'.

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

Use when designing engineering 1:1s — cadence, agenda mix, growth-vs-blocker-vs-trust shape, cancellation anti-patterns. Triggers on 'fix my 1:1s', 'should I cancel 1:1s this week'.

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

Use when a JavaScript/TypeScript package is consumed by another package — exports map, peer vs. direct dependencies, files allow-list, and whether it should be built at all.

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

Use when a repeated learning, mistake, or successful pattern should be turned into a new rule or skill. Also use after completing a task to capture learnings from the work.

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

Use to consolidate multiple already-run judge verdicts into one report — consensus, conflicts, must-fix/should-fix with per-judge provenance. Consume-only, no opaque score, never auto-gates.

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

Use when building Laravel real-time features — Broadcasting events, ShouldBroadcast, private/presence channels, Echo client. For non-Laravel WebSockets, use the stack-native skill.

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

When shaping cadence — evergreen / campaign / reactive split, beat-mapping across channel stages, content-debt management. Triggers on 'plan our content cadence', 'what should we publish'.

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

Use when qualifying or disqualifying a single deal — MEDDIC slots with evidence, inversion test, disqualification heuristic. Triggers on 'is this deal real', 'should we walk away'.

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

Use to audit a past architectural decision — did the chosen option hold up, what assumptions drifted, should the ADR be superseded? Backward review only; does not lock new choices.

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

Estimate a Jira/Linear ticket — 'estimate PROJ-123', 'wie groß ist das?', 'should we split this?' — size + risk + split + uncertainty, sibling of /refine-ticket, close-prompt.

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

Use when deciding insource vs outsource vs acquire — integration-cost analysis, dependency-risk, optionality preservation. Triggers on 'should we build', 'buy vs partner'.

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

Use when comparing this package to a peer / competitor — ours-vs-theirs verdict table, axis selection, adoption queue. Triggers on 'how do we compare to X', 'should we adopt their pattern'.

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

Coordination guidance for the narrow case of multiple desktop-backed agents active concurrently in the same desktop-backed coordination context. Use ONLY when two or more desktop peers are running at the same time; normal CLI agents and single desktop peers should ignore this skill. Read this BEFORE concurrent desktop-to-desktop handoffs to keep sender labels unique, identity routing cooperative, and material handoffs proven.

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

Combine independent work from two or more selected agents into one decision-ready research report, design, or proposal. Preserve useful complementary findings, develop stronger combined options, and present material alternatives only when they exist. Use when multiple perspectives should improve the product without forcing consensus or staging disagreement.

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

Run a two-agent independent review/redteam followed by peer collaboration to produce a consensus superset of findings and enumerated revision requests. Use when Codex 5.5 and Claude Opus 4.7 should first critique a matter independently, then exchange work, synthesize the best combined analysis, and finish with a single agreed revision list.

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

Harness-first workflow for evaluating and improving terminal UIs through real interaction. Use this whenever the user wants to review a TUI experience, compare before/after behavior, identify UX friction, validate navigation or filtering flows, inspect visual stability, or turn observed interaction problems into concrete follow-up tests and improvement recommendations. Prefer this skill any time a TUI should be exercised through a reproducible PTY/session harness instead of only reading code.

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

This skill should be used when designing terminal user interfaces, creating TUI layouts, choosing TUI color schemes, implementing keyboard navigation, building terminal dashboards, or working with any TUI framework. Activates on mentions of TUI design, terminal UI, Ratatui layout, Ink components, Textual widgets, Bubbletea views, terminal color palette, keybinding design, panel layout, split panes, terminal dashboard, box-drawing characters, sparklines, progress bars, modal dialogs, focus management, or terminal accessibility.

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

Create, edit, review, preview, and export polished Marp Markdown slide decks in Canvas Notebook. Use when the user wants Markdown-native presentations, `.marp.md` or `.slides.md` files, version-controlled decks, Marp PDF/image/PPTX/HTML export, speaker notes, dashboard-style slides, data cards, or better looking decks that should remain close to plain text.

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

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

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