dyad-sh/dyad

Overview

This skill reviews the current agent session for errors, snags, and hard-won knowledge, then autonomously updates project guidance files with concise, actionable learnings. It writes to topic-specific files under rules/ when appropriate, or to AGENTS.md only when a general, cross-cutting rule is needed. The skill completes without asking for confirmation and stages the changes for commit.

How this skill works

It scans the session transcript to extract up to five high-impact learnings: explicit errors, recurring gotchas, workflow friction, and architecture insights. It checks AGENTS.md and existing rules/*.md to avoid duplicates, then inserts concise 1–3 line entries into the most relevant rule file (or creates a new rules/*.md and updates AGENTS.md if needed). Finally, it runs git add to stage AGENTS.md and rules/ changes and summarizes what was modified.

When to use it

• After any debugging or build session that uncovered errors or non-obvious steps
• When a session required repeated attempts or workarounds
• If configuration, directory layout, or conventions caused friction
• At the end of a multi-step change so learnings are captured before context is lost
• When a pattern likely affects future agent runs or contributors

Best practices

• Limit additions to the five most impactful learnings from the session
• Prefer existing rules/*.md; only edit AGENTS.md for project-wide conventions
• Write entries as specific, actionable commands or recognition symptoms (include exact error text when relevant)
• Consolidate overlapping learnings into a single concise entry rather than appending duplicates
• Remove obsolete or duplicated entries in the target file before adding new ones
• Always run: git add AGENTS.md rules/ to stage changes

Example use cases

• After a failed TypeScript build, add the exact tsc error and the fix command (e.g., run npm run build before tests)
• When an Electron IPC channel caused race conditions, document the correct init order in rules/electron-ipc.md
• If environment variables were missing, add a rule pointing to the env setup and include the missing keys and their expected values
• When test flakes required a --runInBand flag, add that flag and the failing symptom to rules/e2e-testing.md
• Create a new rules/tanstack-router.md when router patterns repeatedly confuse agents or require specific imports