fe-component-feature-system
Frontend Component Feature System
Use this skill when the task involves shared UI architecture, component layering, feature module boundaries, or extracting repeatable patterns from product workflows.
Use This Skill When
- The codebase needs a component system instead of isolated widgets.
- Feature code is scattered and needs better module ownership.
- The task requires deciding what belongs in primitives, composite components, domain components, or feature modules.
Inputs To Confirm Up Front
- Existing shared UI or design system structure.
- Repeated product patterns across pages.
- Stable versus volatile abstractions.
- Desired module ownership boundaries.
Execute Workflow
More from jiannx/agent-skills
nocobase-bugfix
Diagnose and fix NocoBase v2 bugs, especially flow, FlowModel, client-v2, and plugin client issues. Use for issue reproduction, root-cause analysis, targeted fixes, regression checks, or narrow v2 feature completion based on nearby v1 behavior. Default to v2-only changes unless the user explicitly asks for v1.
9nocobase-v2-flow-upgrade
Upgrade existing NocoBase v1 plugins to v2 FlowModel or field-model architecture with behavior parity. Use for migration planning, implementation, parity validation, and pitfalls around request payloads, settings ownership, i18n namespaces, roles persistence, flow variables, and editor integrations.
9fe-quality-operations
Prepare frontend projects for reliable delivery with testing, performance review, observability, release strategy, and production-readiness checks.
2fe-data-mock-state
Design frontend data layers, server-state handling, adapters, mock strategies, and state ownership with stable contracts and low integration churn.
2fe-routing-permission
Design frontend navigation, route ownership, URL state, auth boundaries, and permission systems with explicit access rules and user-state handling.
2fe-design-implementation
Implement product-grade frontend UI from design artifacts with consistent interaction patterns, theme-driven styling, responsive behavior, and design verification.
2