القائمة
Opinionated baseline for Flutter apps: format/analyze, tests, Makefile targets, and CI wiring (no docker unless backend exists separately).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Add/extend Playwright E2E/integration specs for web use-case changes. Prefer existing repo naming conventions; include UC ID when introducing new use-case-specific specs.
Ensure GitHub Actions CI exists and is green. CI must run lint/format, build, and tests as applicable. Failing CI is blocking.
Derive comprehensive `/docs` from an existing codebase when docs are missing/stale. This is blocking work before new features.
Add docker-compose for HTTP APIs (required before implementing/changing use cases). Provide .env.example + Make targets: up/down/test/lint/build.
End-to-end Gaia SDLC workflow (Repo Explorer → drift/CI fixes → task graph → gated delivery → QA veto → MCP proof). Use for any work in a repo.
Run curl-style integration checks against the docker-compose stack for HTTP APIs. Required for use-case changes.
| name | stack-default-flutter |
| description | Opinionated baseline for Flutter apps: format/analyze, tests, Makefile targets, and CI wiring (no docker unless backend exists separately). |
Use when:
dart formatdart analyze or flutter analyzeflutter testRule: Prefer existing repo conventions if present.
Makefile.github/workflows/ci.yml/docs/testing/how-to-run.mdmake lint (format check + analyze)make test (flutter test)
Optional:make build (if CI builds artifacts)make run (if useful and stable)make lintflutter test runs via make testmake lint and make testmake build and wire inUpdate /docs/testing/how-to-run.md:
lint, ciunit