All Projects

Multi-Agent Plugins

Per-stack AI engineering-lifecycle toolkits (Claude Code plugin marketplace) for the multi-agent pipeline — iOS, Android, frontend (React), and backend, each project-configurable. Enable your stack's plugin per repo.

A Claude Code plugin marketplace of per-stack engineering toolkits — each a generic, project-configurable set of skills (reference + workflow + tools + an index router) for one stack.

  • •ai-frontend-engineering-toolkit (React/TSX): reference (component, state, forms, styling/design-tokens, routing, build-and-test) + workflow (create-component from Figma, evolve-component, fix-bug, branch-and-pr) + tools (figma-utility, code-connect, component-docs)
  • •Native-React-first; framework (Next/Vite/CRA), tokens, paths, and test runner come from project config — works on any React codebase
  • •Project-scoped enablement: each repo enables its stack's plugin in .claude/settings.json; the pipeline detects the stack and uses it — no runtime toggle
  • •Companion of the corporate turkish-airlines-plugins marketplace, on the individual account. Android (Jetpack Compose) and backend (spec-driven) toolkits planned.
Private RepositoryThis is a private repository. You need collaborator access to view the source code on GitHub.
1
Plugins
14
Frontend skills
React
Stack
WIP
Status

Tech Stack

Claude CodePlugin MarketplaceReactTypeScriptFigma

Features

ai-frontend-engineering-toolkit

React/TSX engineering lifecycle: create · evolve · fix · review · ship.

  • •Reference: component architecture, state (hooks/Query), forms (RHF+Zod), styling (design tokens), routing (Next/React Router), build-and-test (Vitest+Testing Library+Storybook)
  • •Workflow: create-component (Figma→React), evolve-component (drift-heal + extend, human-gated), fix-bug, branch-and-pr
  • •Tools: figma-utility, code-connect (React), component-docs (Storybook)
  • •Generic — project config drives framework, tokens, paths, and test runner

Per-project switching

Enable a stack's plugin in the repo's .claude/settings.json.

  • •No runtime toggle needed; the multi-agent pipeline detects the stack and uses whatever is enabled
  • •Collaborators aligned with multi-agent-pipeline / dev-toolkit-mcp so access is bundled, not requested per-repo
Back to overview