workflow

Plugin workflow from marketplace agilbertdev in AGilbertDev/claude-plugins. Commands read from the repo's manifest — 1 month ago.

Skills (8)

• commit

  Commit and open a pull request the AGilbertDev way. Use when reviewed work is ready to land, at the last stage of the pipeline, or when the user says commit, push, or open a PR.

• compliance

  AGilbertDev's universal privacy, security, and minimum-legal baseline for every project — Québec Law 25 + Charter of the French Language (Law 101/96), PIPEDA, GDPR/UK GDPR, US state laws, COPPA, CASL/CAN-SPAM, consumer protection, accessibility (WCAG/EAA), IP & asset licensing, and digital-sales tax

• new-project

  Start a new personal project from the right template. Use when creating a new repo or bootstrapping a project from scratch.

• pipeline

  Build one feature through the spec-driven pipeline. Use for any feature, page, route, or non-trivial fix in a personal project. Spec approved in plan mode, then tests first, a hands-off build, browser verification, review, and an open pull request. Not for small fixes.

• quebec-french

  Rules for writing Québécois French copy, including the U+00A0 no-break space before ? ! : ; and how to check it. Use before writing or reviewing any French UI copy, locale file, or French prose.

• spec

  How to write and maintain a feature spec, with the template and the design principles every spec must check. Use at the spec stage of the pipeline, when the user asks for a spec, or when a feature changes and its spec must follow.

• test-patterns

  How to write a good test once you already know what to test. Craft rules for pure data versus computed logic, one fact per case, and comment discipline in test files. Use before writing or reviewing any unit test, alongside workflow:spec for what the test should check.

• tutorial-mode

  Collaboration mode for learning-by-building. Use when AGilbertDev wants to learn a project rather than have it built for him. Teach step by step, point at the right tools, and do NOT write or edit the code for the user. This is an opt-in per-project mode, not an always-on convention.

Subagents (1)

• unit-test

  Writes unit tests from a feature spec, independently of the implementation. Use proactively at the test stage of the pipeline, before the code is written, and whenever tests must validate intent rather than confirm what the code already does.

Hooks (5)

• SessionStart

  cat "${CLAUDE_PLUGIN_ROOT}/core.md"

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/git-identity-guard.sh"

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/secrets-guard.sh"

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/tests-before-commit.sh"

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/secrets-guard.sh"

Similar plugins