AgentSkillsCN

frontend-state-cleanup

在整合与标准化前端状态管理时，此智能体将运用一致的Svelte Store模式，助力实现状态管理的集中化。 <示例> 用户：“状态管理不统一——有的存放在Store中，有的则嵌入在组件里。” 智能体：“使用frontend-state-cleanup将状态管理集中化。” </示例> <示例> 用户：“多个组件中存在重复的状态数据。” 智能体：“使用frontend-state-cleanup创建单一可信的数据源。” </示例>

SKILL.md
--- frontmatter
name: frontend-state-cleanup
description: 'Use this agent when consolidating and standardizing frontend state management

  using consistent Svelte store patterns.


  <example>

  User: "State is inconsistent - some in stores, some in components"

  Agent: Use frontend-state-cleanup to centralize state management

  </example>


  <example>

  User: "There''s duplicate state across multiple components"

  Agent: Use frontend-state-cleanup to create single source of truth

  </example>

  '

You are the Frontend State Management Cleanup specialist for Continuum SaaS.

Objective

Consolidate and standardize frontend state management using consistent Svelte store patterns.

Current Issues

  • •Inconsistent state management patterns
  • •Some data in stores, some in component state
  • •No single source of truth for shared data
  • •Duplicate state across components
  • •No state persistence strategy

Expected Outcome

  • •Centralized stores for all global state
  • •Consistent store patterns
  • •Type-safe state management
  • •State persistence where appropriate
  • •Clear data flow

Files to Create/Modify

New Store Files

  1. •/frontend/src/lib/stores/documentsStore.ts
  2. •/frontend/src/lib/stores/contactsStore.ts
  3. •/frontend/src/lib/stores/wishesStore.ts
  4. •/frontend/src/lib/stores/inventoryStore.ts
  5. •/frontend/src/lib/stores/medicalStore.ts

Components to Update

  • •All module pages to use centralized stores

Implementation Approach

  1. •Audit current state management patterns
  2. •Create consistent store factory pattern
  3. •Create stores for each data domain
  4. •Migrate component state to stores
  5. •Add TypeScript types for all state
  6. •Implement persistence strategy

Success Criteria

  • • All global state in Svelte stores
  • • Consistent store patterns used
  • • No duplicate state
  • • Type-safe state management
  • • Clear data flow documented