All authors
Claude Skills by Aquaticats
github.com/Aquaticats13 skills0 installs19 views
- Android EmulatorAndroid emulator or AVD work. Use before launching, scripting or briefing an agent to use the Android emulator (device passes, screenshots, gfxinfo, adb on an emulator). Loading it is a required step before the first launch. Headless launches are banned.Votes: 0GitHub stars: 7
- Project Code ReviewReview code according to project standardsVotes: 0GitHub stars: 7
- Testing PracticesUse when writing or reviewing TypeScript tests in this monorepo using the module-test harness.Votes: 0GitHub stars: 7
- Visual Design ReviewVisual design work. Use before building or reviewing UI design variants, design matrices, HTML review forms, device mockups or frames, Android screen comparisons, a UI matched to a reference screenshot, or any custom interactive element (click or touch target size). Loading it is a required step before the first visual artifact, not an option.Votes: 0GitHub stars: 7
- Choosing TechnologySelects and vets SaaS vendors, libraries, frameworks, build tools, local executables, and replacement dependencies through hard gates, source audits, validation, and scored comparison. Use when choosing, recommending, evaluating, vetting, replacing, or comparing technologies or vendors for this repo.Votes: 0GitHub stars: 7
- CssUse when editing CSS, writing component styles, or reviewing CSS in this repo.Votes: 0GitHub stars: 7
- Dum Dum Non TsUse when writing or editing source files in non-TypeScript general-purpose languages.Votes: 0GitHub stars: 7
- Pi As SubagentUse when delegating a task to Pi as a subagent over RPC.Votes: 0GitHub stars: 7
- RunbookUse when writing manual steps a user must execute (clicks, keys) after bridges failed.Votes: 0GitHub stars: 7
- Source Audited ReportUse for cited reader-facing reports, not quick research, code work, or docs edits.Votes: 0GitHub stars: 7
- Troubleshooting DocUse when investigating an external tool's behavior, bug, quirk, capability gap, or fix difficulty; proactively write the troubleshooting doc the moment you finish diagnosing or working around one, even when the user did not ask; also use when writing or updating a doc/troubleshooting/<topic>.md file. The write-up is a required completion step, not an offer.Votes: 0GitHub stars: 7
- Planning> Scratch-path note: > `/tmp/agent` paths in this document are historical. > Use `~/temp/agent` for current work. Status: plan complete and grilled. All 13 decisions are resolved; the user confirmed shared understanding on 2026-07-09. Independent audit findings are incorporated. Final reviewer and Advisor planning audits passed against commit `0551184a6` on 2026-07-09. Implementation was authorized and completed on 2026-07-09 under the user's revised verification scope. During implementation,...Votes: 0GitHub stars: 7
- PlanningThe user requested a skill to curb failures in AI teaching and drafted teaching materials. They requested grilling to discover the failures from their experience. Repository material remains potentially relevant. Discovery is ongoing. The revised prototype has been operationally verified and visibly presented for critique. After a quick scan with no major complaints, the user obtained an independent review from Claude Fable 5.1. They supplied `promises-teaching-independent-review.md` and marked Votes: 0GitHub stars: 7