engineering

Plugin engineering from marketplace frostaura in frostaura/ai.toolkit.gaia. Commands read from the repo's manifest — 1 month ago.

Skills (16)

• fa-engineering-architecture

  Provides Gaia architecture documentation guidance that keeps docs, README messaging, and design decisions aligned to the current operating model. Use it by updating the relevant files under the consuming repository's docs/architecture/ tree (system components, use cases, class diagrams, UI) before a

• fa-engineering-containerization

  Provides compose-first containerization guidance for services that expose an HTTP surface, covering the root compose file, the `.env.example` contract, the canonical `up`/`down`/`test`/`lint`/`build` task set, helper services for email and gateway flows, and runbook alignment. Use it by standing the

• fa-engineering-default-tech-stack

  Provides Gaia's default full-stack baseline with React, TypeScript, Redux Toolkit, Tailwind CSS, and shadcn/ui on the frontend plus .NET, EF Core, PostgreSQL, and MCP exposure on the backend. Use it by adopting the documented baseline (versions, scaffolds, references) for any new app or unspecified-

• fa-engineering-deploy-chain

  Provides deploy-chain activation guidance for turning a repository whose CI workflow already carries build-and-deploy jobs into one that actually publishes and redeploys. Use it by reading the secret names out of the workflow's own env block, creating the deployment target before setting its identif

• fa-engineering-e2e-testing

  Provides browser end-to-end specification guidance for user-visible behaviour changes, covering suite location, traceable test IDs carried in test titles, stable selectors, environment-driven base URLs, and CI lane placement. Use it by adding or extending browser specs whose titles carry the require

• fa-engineering-implementation

  Provides planned implementation delivery guidance that keeps a branch coherent, stabilized, and ready for testing without redefining the target solution. Use it by implementing the planned tasks against existing repo conventions, keeping diffs scoped, running lint/build locally, and keeping the todo

• fa-engineering-manual-regression

  Provides the interactive regression procedure for behaviour changes in two lanes — an API lane driven by curl-style HTTP checks and a web lane driven by browser automation — both executed against the composed stack rather than a development server. Use it by writing a compact three-to-eight check li

• fa-engineering-planning

  Provides execution planning guidance that turns approved architecture into a branch-aware plan with dependencies, QA checkpoints, release gates, and proof expectations. Use it by translating the current architecture into native todo items sequenced by branch, with explicit required gates and blocker

• fa-engineering-process

  Provides Gaia's end-to-end workflow coordination guidance for intake, routing, QA checkpoints, release gates, and proof expectations. Use it by routing every meaningful request through the intake → architecture → planning → engineering → testing → release gates — per branch, with independent branche

• fa-engineering-stack-dotnet-api

  Provides the .NET HTTP API repository baseline - an `.editorconfig` with enforced analyzers and format verification, a `dotnet test` unit lane plus HTTP-boundary integration coverage, a Dockerfile with `docker-compose.yml` and `.env.example` so the service comes up locally, and a command surface CI

• fa-engineering-stack-dotnet-maui

  Provides the .NET MAUI cross-platform client-app baseline - enforced analyzers, unit coverage of the non-UI logic that MAUI's UI automation cannot reach, per-target-framework build validation with the platform limits of CI stated honestly, a command surface CI calls verbatim, and a repeatable path f

• fa-engineering-stack-flutter

  Provides the Flutter and Dart app-repository baseline - `dart format` drift checking that actually fails, a lint rule set wired into `analysis_options.yaml` so the analyzer has something to say, `flutter test` widget and unit coverage, and a command surface CI calls verbatim. Use it by auditing a Fl

• fa-engineering-stack-python

  Provides the Python repository baseline - a single-tool `ruff` lint and format gate that fails rather than merely reports, `pytest` wired to a command CI calls verbatim, and an explicit decision about which packaging manager already owns the project. Use it by auditing a Python repository against th

• fa-engineering-stack-web-ts

  Provides the JavaScript/TypeScript web-repo baseline - ESLint and Prettier enforcement, one runnable unit lane on the repo's own runner (Vitest, Jest or equivalent), Playwright browser end-to-end coverage, and a command surface that CI calls verbatim. Use it by auditing a Node or TypeScript reposito

• fa-engineering-testing

  Provides Gaia's formal validation guidance across unit, integration, manual regression, automated regression, and evidence review. Use it by running the test layers required by each task's gates (unit → integration → e2e → manual regression), recording proof labels (e.g. 'curl', 'playwright-mcp') wh

• fa-engineering-ui

  Provides React UI implementation guidance that enforces the design system, shadcn/ui composition, semantic Tailwind tokens, and responsive layout discipline. Use it by composing shadcn/ui primitives with semantic Tailwind tokens (no raw color/spacing literals), respecting the responsive layout rules

Subagents (6)

• fa-engineering-implementation-planner

  Use for turning Gaia's approved design into an executable branch plan with dependencies, parallelism, QA checkpoints, release gates, and proof expectations, once the target solution is current. This role owns the shape of the work: branch boundaries, ordering, acceptance criteria, retry triggers, an

• fa-engineering-intake-coordinator

  Use for new requests, ambiguous follow-ups, workflow resets, or definition maintenance that touches multiple Gaia roles before there is a safe delivery owner. This role owns request framing, complexity classification, drift detection, the smallest-effective-role-set decision, and the first execution

• fa-engineering-release-engineer

  Use for final gate evaluation, CI and deployment readiness, proof recording, and ready-or-not-ready decisions once implementation and validation are far enough along to judge closure. This role owns release-facing evidence, unresolved gate status, blocker ownership at the finish line, and the final

• fa-engineering-software-engineer

  Use for planned implementation work, definition-file maintenance after the target solution is current, and fast stabilization before broader validation and release gating begin. This role owns code and configuration changes, localized cleanup needed to keep a branch coherent, and the implementation

• fa-engineering-solutions-architect

  Use for changes that affect Gaia's target operating model, architectural boundaries, documented behavior, or high-level product story before planning and delivery proceed. This role owns the consuming repository's `docs/architecture/` tree, README alignment when the system story changes, and design

• fa-engineering-tester

  Use for formal validation, regression coverage, browser-assisted checks, and pass-fail-blocked decisions after a branch is stable enough to evaluate. This role owns test artifacts, validation outcomes, QA evidence, and the authority to veto weak completion claims. Invoke it when a planned branch nee

MCP servers (1)

• playwright

  runs: npx @playwright/mcp@latest

Similar plugins