Generates syntax-valid, render-safe Mermaid.js diagrams (flowcharts, sequence diagrams, state diagrams, ERDs, Gantt charts). Use when a user asks to draw, visualize, map out, or document systems, workflows, API sequences, database schemas, or architectures. Don't use for generic markdown tables, text-based descriptions, or non-visual data serialization.
Converts vague feature requests into structured product requirements (PRDs) and sprint-ready user stories. Use when scoping and planning a feature in a Product Manager or Scrum Master capacity. Don't use to write or modify application code.
Standardizes how agents update and manage README.md files, adopting the Deep Insight/Strands SDK documentation style. Use when creating a new README from scratch, improving an existing README, or converting technical docs to user-friendly formats. When creating or editing Mermaid diagrams in the README, load and use the `generating-mermaid-diagrams` skill. Don't use for API-only documentation or internal technical specs.
Orchestrates specialized subagents in parallel to keep the main thread idle and maximize concurrency. Use when a task can be decomposed into independent subtasks (such as concurrent code changes, parallel research, or separate validation steps), when a task is long-running and the parent thread should remain idle while waiting, or when interactive input is needed to refine features. Don't use for simple sequential tasks, single-file edits that cannot be parallelized, or when subagent support is not available in the workspace.
Provides guidelines, visual specs, and accessibility rules for Google-branded marketing websites. Use when building or modifying web pages, landing pages, or components (such as buttons, forms, carousels, or chips) to ensure they conform to Google's layout, design, accessibility, and legal standards. Don't use for mobile native app development, generic backend service design, or premium creative visual styling (micro-animations, artistic designs)—use `designing-tasteful-frontends` for that.
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
Performs a comprehensive UI/UX design audit on application screens or components. Use when a user asks to review design, audit UI/UX, improve visual hierarchy, or polish an interface. Don't use for code reviews, performance audits, or backend architecture reviews.
Identifies LLM-generated duplicate code, TODO/FIXME comments, static/lazy stubs, mock data, and placeholder files in a codebase. Use when reviewing recent LLM-generated PRs or commits, analyzing build failures due to omitted/lazy ellipses, or auditing codebases for structural duplicates. Don't use for generic dependency updates, linting formatting style, or refactoring unrelated clean code.