claude-dream-team

Plugin claude-dream-team from marketplace danniel-claude-plugins in danniel-isiah-libor/danniel-claude-plugins. Commands read from the repo's manifest — 18 days ago.

Skills (6)

• documentation

  Write clear, audience-facing documentation that ships to clients, users, and stakeholders — user guides, how-to / getting-started guides, feature documentation, FAQs, and release notes. Use when creating or improving end-user or stakeholder documentation. Primary skill of the technical-writer.

• gcp-devops

  Expert DevOps for Docker containers, industry-standard CI/CD pipelines, and Google Cloud Platform infrastructure (Cloud Run, Cloud SQL, Cloud Storage, Artifact Registry, IAM, and more). Use when building or reviewing Dockerfiles/compose files, CI/CD workflows, or GCP infra/IaC. Always optimizes for

• git-conventions

  Apply Conventional Commits 1.0.0 and Conventional Branch 1.0.0 — consistent commit messages and branch names — and derive semantic versions from them for tags and releases. Use when committing, creating or naming branches, or tagging/releasing. Used by the fullstack-developer (commits/branches) and

• project-adaptation

  Adapt to and collaborate with the project you're working in — detect its tech stack, honor its CLAUDE.md and conventions, and reuse its existing skills and agents before adding anything new. Use at the START of any claude-dream-team task (devops, development, or QA), on existing repos as well as fre

• qa-testing

  Senior QA — unit tests covering all scenarios, end-to-end testing with Playwright, security testing/VAPT (XSS, SQL injection, and more), and comprehensive code review of uncommitted changes or a PR/MR. Produces verdicts and routes each fix to the dev or devops agent. Use when verifying, testing, sec

• senior-development

  Senior fullstack engineering standards — SOLID, DRY, KISS, YAGNI, clean and highly maintainable code, security-first, no deprecated APIs, and docs-first (exhaust built-in/framework and existing-dependency capabilities before building from scratch). Use when implementing features, modules, APIs, UI,

Slash commands (1)

• /claude-dream-team:dream-team-review

  Run the dream-team review loop — QA reviews & tests the change, then routes fixes to the dev/devops agents and re-verifies until clean.

Subagents (5)

• devops-engineer

  Use for CI/CD pipeline and cloud-infrastructure work — designing, reviewing, debugging, or hardening pipelines (GitHub Actions, Cloud Build, GitLab CI) and GCP infrastructure (Cloud Run, GKE, Artifact Registry, IAM, networking, Terraform/IaC), plus deployments and observability. A senior DevOps engi

• fullstack-developer

  Use to implement features end-to-end — frontend, backend, and database — to a senior standard, strictly following the project's coding standards, CLAUDE.md, and conventions. Focused purely on feature code — test authoring belongs to the qa-engineer. A senior fullstack developer you summon to build t

• qa-engineer

  Use to own the overall testing strategy for a change or a project — unit tests, end-to-end (E2E) tests, and VAPT (vulnerability assessment & penetration testing). Designs coverage, runs or authors tests, probes for vulnerabilities, and reports verdicts. A senior QA engineer you summon to make sure i

• security-analyst

  Use to find and triage known vulnerabilities (CVEs) in any repo's dependencies, language runtimes, and container/CI base images, or to look up and explain a specific CVE and whether the project is exposed. Runs the ecosystem's native auditors, cross-checks OSV/NVD, enriches with EPSS and CISA KEV, c

• technical-writer

  Use to create clear, audience-facing project documentation to hand to clients, users, and stakeholders — user guides, how-to / getting-started guides, feature documentation, FAQs, and release notes. A senior technical writer you summon to turn a project or feature into docs people can actually follo

Similar plugins