Build and wire admin features with React views, DI, and MobX.
npx skills add https://github.com/fycd2006/studio --skill admin-developer-fycd2006
Please help me install this Agent Skill. Skill: admin-developer Source: https://github.com/fycd2006/studio/tree/main/.agents/skills/admin-developer Command: npx skills add https://github.com/fycd2006/studio --skill admin-developer-fycd2006
Admin feature development often requires coordinating headless services (use cases, repositories, gateways) and presentation layers (presenters, React views) with DI wiring and MobX reactivity, all while ensuring consistent permissions handling.
Inspect the admin-developer guide and register features using createFeature in your container.
High-intent search queries and answers about installing and using this skill.
Admin-area features are structured by separating headless logic (use cases, repositories, gateways) from presentation layers (presenters, React views), using MobX for reactivity and dependency injection for wiring. This enforces clear boundaries for scalable app architecture.
The best way to wire dependency injection for admin features is registering them via createFeature in your container, applying abstractions, implementations, and decorators to ensure cohesive permissions integration and scalable DI container wiring.
A feature framework handles permissions and use cases by enforcing structured feature boundaries, separating headless services from presentation, and enabling cohesive permissions integration through scalable DI container wiring patterns.
This admin architecture pattern targets projects needing structured feature architecture with both headless services and presentation layers. Using it without a headless backend means losing the defined use cases, repositories, and gateways that provide the core separation of concerns.
Yes, MobX is required to manage reactivity in admin feature development. The architecture explicitly applies MobX reactivity alongside React views and dependency injection wiring to coordinate headless services and presentation layers.
Separating headless logic from presentation in admin applications enforces clear file layouts and abstractions, preventing tight coupling between use cases, repositories, gateways, and React views while ensuring scalable DI container wiring and consistent permissions handling.
chadanandaCreate and validate isolated Git worktrees for feature work.
danmestasBuild accessible validated forms with shadcn/ui, React Hook Form, and Zod.
webinyGuide developers in building Webiny admin features with headless and presentation layers.
TheWayWithinAutomates transactional email delivery for SaaS applications with templates and provider-agnostic interface.
