AGENT SKILLS · ミッション装備 / pwguler

pwguler · Agent Skills

出典を確認した実質的な文書を持つ Skill が 15 件あります。カードを開くと原文、パッケージ内容、導入方法を確認できます。

pwguler
コミュニティ

core-interview

Internal support skill that runs the interview loop for other skills, until every decision is settled. Use it only when another skill or the user starts it, never on your own.

1時間の導入数
7
GitHub Stars
10
更新日
10月16日
pwguler
コミュニティ

debug

Find the root cause of a bug before you fix it. Read this skill before you fix any bug. Read it also when the fix looks obvious. Use it when the user says "fix", "broken", "not working", "error", "failing", or "bug". Use it also when a test fails unexpectedly during other work.

1時間の導入数
7
GitHub Stars
10
更新日
10月16日
pwguler
コミュニティ

drill

Question a plan or design until every decision in it is settled and agreed. Read this skill first when the user asks for a new feature, or when a design is not settled. Use it when the user wants a plan stress-tested or a design settled before building. Use it also to settle the structure of a new codebase or area. Use it when the user says \"drill this\" or \"drill me\".

1時間の導入数
7
GitHub Stars
10
更新日
10月16日
pwguler
コミュニティ

implement

Implement a settled plan test-first, one small slice at a time. Read this skill before you write code for a spec or a settled plan. Read it also when the plan is small. Use it when the user says \"implement this\" or \"build it\", or names a spec to implement.

1時間の導入数
7
GitHub Stars
10
更新日
10月16日
pwguler
コミュニティ

land

Finish a development branch with a merge, a PR, a keep, or a discard. Use it when the implementation is complete.

1時間の導入数
7
GitHub Stars
10
更新日
10月16日
pwguler
コミュニティ

parallel

Run independent tasks at once in subagents, race attempts at one task, or cover many parts of one job. Use it only when the user asks for parallel work. Use it when the user asks to run two or more independent tasks or failures in parallel. Use it also to race or compare several attempts at one task, or to cover many parts of one job.

1時間の導入数
7
GitHub Stars
10
更新日
10月16日
pwguler
コミュニティ

perf

Make code faster or find why it is slow, from measurements and not from guesses. Read this skill before you change code to make it faster or use less memory. Use it when the user reports slow code, high latency, or high memory use. Use it also to check a speed claim, or to compare the speed of two options. Use it to diagnose a slow or stuck process, a profile, or a trace file.

1時間の導入数
7
GitHub Stars
10
更新日
10月16日
pwguler
コミュニティ

prototype

Build a throwaway UI prototype for the user to react to before any real code. Read this skill when the user asks for a mockup or a prototype of a UI. Use it when a design decision depends on look, feel, or flow that text cannot settle.

1時間の導入数
7
GitHub Stars
10
更新日
10月16日
pwguler
コミュニティ

recall

Rebuild where recent work stands, from past sessions of the agent, the live repository, and the history of the project. Give back a short brief. Run it before you start or continue work, with or without a topic.

1時間の導入数
7
GitHub Stars
10
更新日
10月16日
pwguler
コミュニティ

reflect

Find the lessons in the current session of the coding agent. Put each lesson where the next agent meets it, in a check, a skill, or a project file. Run it at the end of a session that had corrections, errors, or surprises.

1時間の導入数
7
GitHub Stars
10
更新日
10月16日
pwguler
コミュニティ

research

Find out what is true about a library, service, or standard from the owner of the facts. Or find out from its history why code has its shape. Write the answer down with a citation for each claim. Read this skill when the user asks why code, a constant, or a setting has its current form. Use it when the user asks to look something up, or to check how an API or tool really behaves. Use it also to give reading to a subagent while other work continues.

1時間の導入数
7
GitHub Stars
10
更新日
10月16日
pwguler
コミュニティ

rubric

Find defects in a change with independent read-only reviewers. Judge quality that no command can settle, such as "this API design is good" or "this UI is not slop". Judge it against criteria written before anyone looks at the work. Use when the user asks for a defect review or a bug hunt on a change. Read this skill when the user asks whether a design, a UI, a name, or prose is good. Use it when a UI, public interface, name, or doc needs a quality judgment before it ships. Use it when a spec cri

1時間の導入数
7
GitHub Stars
10
更新日
10月16日
pwguler
コミュニティ

tldr

Report a finished task as its result, not its transcript. Or tell the user what happened since their last message. Read this skill before your final report on a task that changed files, made an artifact, or ran a check. Examples are a build, a workflow, a background agent, an implement or verify run, or a release. Use it also when the user asks what happened since their last message. Use it when the user asks to catch up on this session.

1時間の導入数
7
GitHub Stars
10
更新日
10月16日
pwguler
コミュニティ

verify

Prove a claim of done, fixed, or passing before you make it. Run the commands and read their output. Read this skill before you say that work is done, fixed, or tested. Read it also after a small change. Use it before a commit or a PR. Use it also when the user asks to write or update the verification recipe of the app.

1時間の導入数
7
GitHub Stars
10
更新日
10月16日
pwguler
コミュニティ

write-skill

Create or edit a document that an agent reads, and prove that it changes behavior. Put a lesson that agents keep learning again into structure. Read this skill before you write or edit a skill, AGENTS.md, CLAUDE.md, a system prompt, or other text for agents. Use it to verify such a document before it ships. Use it also when the user corrects the same agent mistake a second time.

1時間の導入数
7
GitHub Stars
10
更新日
10月16日