media-upload
No SKILL.md available for this skill.
View on GitHubMore from inkeep/team-skills
qa
Manual QA testing — verify features end-to-end as a user would, by all means necessary. Exhausts every local tool: browser (Playwright), Docker, ad-hoc scripts, REPL, dev servers. Mock-aware — mocked test coverage does not count. Proves real userOutcome at highest achievable fidelity. Blocked scenarios flow to /pr as pending human verification. Standalone or composable with /ship. Triggers: qa, qa test, manual test, test the feature, verify it works, exploratory testing, smoke test, end-to-end verification.
61write-agent
Design and write high-quality Claude Code agents and agent prompts. Use when creating or updating .claude/agents/*.md for (1) single-purpose subagents (reviewers, implementers, researchers) and (2) workflow orchestrators (multi-phase coordinators like pr-review, feature-development, bug-fix). Covers delegation triggers, tool/permission/model choices, Task-tool orchestration, phase handoffs, aggregation, iteration gates, and output contracts. Also use when deciding between subagents vs skills vs always-on repo guidance.
50browser
Browser automation with two engines: agent-browser CLI (default for interactive work — navigate, snapshot, click, fill, screenshot, diff) and Playwright scripts (for compound operations — console/network capture, a11y audits, video recording, responsive sweeps, GIF pipeline, shadow DOM piercing). Triggers: browser automation, web test, screenshot, responsive test, test the page, automate browser, headless browser, UI test, console errors, network inspection, accessibility audit, a11y test, performance metrics, video recording, browser state, page structure, authenticated testing, annotated gif, dialog handling, tracing, pdf generation, shadow DOM, web components, DOM stabilization.
49qa-plan
Take SPEC.md + code + diff and produce a maximally ambitious, user-outcome-grounded qa-progress.json ready for /qa execution. Mock-aware coverage reality check — mocked tests don't count as real coverage. Derives scenarios directly from SPEC.md source material (user journeys, failure modes, acceptance criteria), synthesizes compositional user session scenarios, traces spec-to-code and code-to-spec, investigates code patterns, prioritizes, and writes the plan. No execution boundaries — plans everything worth testing including browser, Docker, and integration scenarios. Standalone or composable with /ship. Triggers: qa-plan, qa plan, test plan, derive qa scenarios, qa planning, plan qa, test scenarios.
12screengrabs
Capture, annotate, and include screenshots in pull requests for UI changes. Use when creating or updating PRs that touch frontend components, pages, or any web-facing surface. Also use when asked to add before/after screenshots, visual diffs, or enrich PR descriptions. Triggers on: PR screenshots, before/after, visual diff, PR description, capture screenshot, PR images, enrich PR.
9projects
Shape a strategic bet and decompose it into spec-able stories — multi-multi-dimensional value per story, dependency graphs, cross-cutting concerns, phasing with rationale. Use when: decomposing a bet into stories, structuring a product direction into workable pieces, mapping dependencies across workstreams, preparing stories for /stories or /spec.
2