joao-aires/development-workflow

Create or review CI/CD, Dockerfiles and GitHub Actions for application verification, artifact promotion, deployment and rollback or roll-forward. Apply when delivery infrastructure changes, within the requested repository and environment scope.

Develop a feature in an isolated Git worktree, make Conventional Commits and publish a concise pull request to the correct repository. Apply by default when starting feature work, continuing a feature branch, committing changes or preparing a PR; respect plan-only requests and existing contribution conventions.

Implement, review and prepare application changes for delivery with focused verification, practical CI/CD and operational evidence. Use for feature implementation, bug fixes, PR preparation, pipeline changes and deployment readiness.

Design, implement or review features with security and privacy built into data flows, authorization and integrations. Apply to changes involving identities, user data, external inputs, dependencies or new trust boundaries; revisit protections as the application evolves.

Organize application knowledge and update affected PRDs, architecture, schemas, plans, decisions and runbooks when implementation or accepted decisions change. Use during planning, feature changes, migrations, deployment changes or documentation reviews.

Establish or maintain an application repository's structure, stack constraints, scoped AGENTS.md, local setup and delivery conventions. Use when explicitly asked to start, organize or review a project, or when the requested change affects those foundations; keep ordinary feature work within existing conventions.

Plan, write, run or debug Playwright end-to-end tests for important user journeys. Use for changes spanning UI/API/database behavior, persistence, authentication, authorization or critical browser interactions, and to investigate failing journey tests.