使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-lessons開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
ds-lessons
An instruction an agent can skip is a wish. Make repeated mistakes fail loudly instead.
Steps
- Gather mistakes. Read the current session, recent commits, reverts, review comments, agent instruction files and workaround comments. Group them into classes. A class counts once it happened twice.
- For each class, pick the highest level that works:
- Structure: one owner per piece of state, one supported way per task, hidden internals, delete old patterns an agent would copy.
- Types: make the bad state impossible to write.
- Lint or CI check: the error message names the right file, type or function to use. If the bad pattern is already common, fail only on new additions.
- Test: checks behavior, not internals.
- Docs or agent rules: only for judgment calls that cannot be checked. Add a short example of the failure.
- Fix the most frequent classes now, one commit each.
- Prove each new check. Re-introduce a real past mistake, run the check, and show it fails. Then remove it and show it passes.
- Keep a table in the agent instruction file: rule, and what enforces it. If a rule already existed but nothing enforced it, treat it as a repeat and enforce it now.
- End-of-session reflection: list what went wrong, what took extra loops and what the user corrected. Route each item to a check, a skill edit or a rule. Drop one-off issues.
Stop when
- Each chosen class has an enforcement that you showed failing on a real mistake.
- Or you have handled the top three classes this session. Note the rest.
Rules
- If the fix is structural, do not also add prose. The prose was the symptom.
- Report each class with evidence, the level chosen, and why a higher level did not work.
