Add community skills, agents, system prompts from 22+ sources

Community Skills (32):
- jat: jat-start, jat-verify, jat-complete
- pi-mono: codex-cli, codex-5.3-prompting, interactive-shell
- picoclaw: github, weather, tmux, summarize, skill-creator
- dyad: 18 skills (swarm-to-plan, multi-pr-review, fix-issue, lint, etc.)
- dexter: dcf valuation skill

Agents (23):
- pi-mono subagents: scout, planner, reviewer, worker
- toad: 19 agent configs (Claude, Codex, Gemini, Copilot, OpenCode, etc.)

System Prompts (91):
- Anthropic: 15 Claude prompts (opus-4.6, code, cowork, etc.)
- OpenAI: 49 GPT prompts (gpt-5 series, o3, o4-mini, tools)
- Google: 13 Gemini prompts (2.5-pro, 3-pro, workspace, cli)
- xAI: 5 Grok prompts
- Other: 9 misc prompts (Notion, Raycast, Warp, Kagi, etc.)

Hooks (9):
- JAT hooks for session management, signal tracking, activity logging

Prompts (6):
- pi-mono templates for PR review, issue analysis, changelog audit

Sources analyzed: jat, ralph-desktop, toad, pi-mono, cmux, pi-interactive-shell,
craft-agents-oss, dexter, picoclaw, dyad, system_prompts_leaks, Prometheus,
zed, clawdbot, OS-Copilot, and more

skills/community/dyad/e2e-rebase/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: dyad:e2e-rebase
+description: Rebase E2E test snapshots based on failed tests from the PR comments.
+---
+
+# E2E Snapshot Rebase
+
+Rebase E2E test snapshots based on failed tests from the PR comments.
+
+## Instructions
+
+1. Get the current PR number using `gh pr view --json number --jq '.number'`
+
+2. Fetch PR comments and look for the Playwright test results comment. Parse out the failed test filenames from either:
+   - The "Failed Tests" section (lines starting with `- \`filename.spec.ts`)
+   - The "Update Snapshot Commands" section (contains `npm run e2e e2e-tests/filename.spec.ts`)
+
+3. If no failed tests are found in the PR comments, inform the user and stop.
+
+4. **Build the application binary:**
+
+   ```
+   npm run build
+   ```
+
+   **IMPORTANT:** E2E tests run against the built binary. If any application code (anything outside of `e2e-tests/`) has changed, you MUST run this build step before running E2E tests, otherwise you'll be testing the old version.
+
+5. For each failed test file, run the e2e test with snapshot update:
+
+   ```
+   PLAYWRIGHT_HTML_OPEN=never npm run e2e e2e-tests/<testFilename>.spec.ts -- --update-snapshots
+   ```
+
+6. After updating snapshots, re-run the same tests WITHOUT `--update-snapshots` to verify they pass consistently:
+
+   ```
+   PLAYWRIGHT_HTML_OPEN=never npm run e2e e2e-tests/<testFilename>.spec.ts
+   ```
+
+   If any test fails on this verification run, inform the user that the snapshots may be flaky and stop.
+
+7. Show the user which snapshots were updated using `git diff` on the snapshot files.
+
+8. Review the snapshot changes to ensure they look reasonable and are consistent with the PR's purpose. Consider:
+   - Do the changes align with what the PR is trying to accomplish?
+   - Are there any unexpected or suspicious changes?
+
+9. If the snapshots look reasonable, commit and push the changes:
+
+   ```
+   git add e2e-tests/snapshots/
+   git commit -m "Update E2E snapshots"
+   git push
+   ```
+
+10. Inform the user that the snapshots have been updated and pushed to the PR.