Skip to main content
Manusで任意のスキルを実行
ワンクリックで
sssstwee
GitHub クリエイタープロフィール

sssstwee

1 件の GitHub リポジトリにある 12 件の収集済み skills をリポジトリ単位で表示します。

収集済み skills
12
リポジトリ
1
更新
2026-05-30
リポジトリマップ

skills がある場所

収集済み skill 数が多いリポジトリを、このクリエイターカタログ内の比率と職業範囲とともに表示します。

リポジトリエクスプローラー

リポジトリと代表的な skills

tasted-debug
ソフトウェア開発者

Diagnose failures, broken behavior, regressions, test failures, runtime errors, stale state, rendering bugs, and repeated failed fixes. Use when something does not work, used to work, crashes, fails tests, or needs root-cause proof. Not for product planning or release readiness.

2026-05-30
tasted-design
グラフィックデザイナー

Define product direction, interaction principles, UI structure, visual execution rules, and screenshot-based polish before or during frontend implementation. Use when the task involves UI, product design, interaction behavior, visual quality, or design-system consistency. Not for backend-only logic.

2026-05-30
tasted-distill
ソフトウェア開発者

Extract reusable lessons from completed work, failed attempts, user corrections, logs, diffs, tests, project outcomes, local agent memory, and conversation history, then update durable skills or rules. Use when asked to learn from experience, personalize an agent from prior work, improve skills, refine agent behavior, audit skill health, or turn repeated mistakes into guidance.

2026-05-30
tasted-learn
ソフトウェア開発者

Research unfamiliar domains, source materials, repositories, documents, or problem spaces and turn them into structured understanding before planning or implementation. Use when the task asks for deep research, source synthesis, domain learning, evidence mapping, or study notes. Not for one-off link fetching or simple copy editing.

2026-05-30
tasted-ship
ソフトウェア開発者

Review implemented work, verify acceptance criteria, prepare delivery, inspect release readiness, handle PR or issue follow-through, and confirm shipped state. Use when work is ready for review, merge, release, publish, push, or handoff. Not for root-cause debugging.

2026-05-30
tasted-think
マネジメントアナリスト

Turn rough ideas, product questions, architecture choices, implementation options, and tradeoffs into decision-ready plans. Use when the user asks what to build, whether an approach is worth it, how to structure a solution, or what plan the agent should execute. Not for debugging an already broken behavior.

2026-05-30
debug
ソフトウェア開発者

Diagnose failures, broken behavior, regressions, test failures, runtime errors, stale state, rendering bugs, and repeated failed fixes. Use when something does not work, used to work, crashes, fails tests, or needs root-cause proof. Not for product planning or release readiness.

2026-05-29
distill
ソフトウェア開発者

Extract reusable lessons from completed work, failed attempts, user corrections, logs, diffs, tests, project outcomes, local agent memory, and conversation history, then update durable skills or rules. Use when asked to learn from experience, personalize an agent from prior work, improve skills, refine agent behavior, audit skill health, or turn repeated mistakes into guidance.

2026-05-29
このリポジトリの収集済み skills 12 件中、上位 8 件を表示しています。
1 件中 1 件のリポジトリを表示
すべてのリポジトリを表示しました