sourcelin-ui-refactor

Standardize refactor tasks across Sourcelin UI Platform modules, routing, and styling tokens.

9|2|Updated May 18, 2026
One-click install
npx skills add https://github.com/SourceLin/sourcelin-cloud-blog --skill sourcelin-ui-refactor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sourcelin-ui-refactor
Source: https://github.com/SourceLin/sourcelin-cloud-blog/tree/main/sourcelin-ui/sourcelin-ui-platform/skills/sourcelin-ui-refactor
Command: npx skills add https://github.com/SourceLin/sourcelin-cloud-blog --skill sourcelin-ui-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized approach to refactoring Sourcelin UI Platform modules, shared components, routing, style boundaries, and architecture documents, ensuring consistency and maintainability across the codebase.

Core Features & Use Cases

  • Standardized refactor workflow across modules, components, routing, and styling boundaries.
  • Enforces explicit architectural rules such as Naive UI placement, token-based styling, and route-driven navigation.
  • Documentation synchronization guidance, including common references like README.md, AGENTS.md, and docs/frontend-architecture.md to keep guidance aligned.

Quick Start

Begin by identifying target directories (src/app, src/modules, src/shared) to refactor, apply changes within the documented boundaries, and validate with type checks and style guards.

Frequently Asked Questions about sourcelin-ui-refactor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize UI refactoring across shared components and routing modules?▼

Standardize UI refactoring by applying explicit architectural boundaries, route-driven navigation, and token-based styling across src/app, src/modules, and src/shared directories to ensure cross-module consistency.

What is the best way to enforce style boundaries during a UI platform refactor?▼

Enforce style boundaries by adopting token-based styling and validating changes with style guards, ensuring that shared components and module-specific styles remain strictly separated during the refactor.

How do you keep frontend architecture documentation aligned when refactoring modules?▼

Keep frontend architecture documentation aligned by synchronizing updates across README.md, AGENTS.md, and docs/frontend-architecture.md whenever structural changes are made to modules or routing.

How do I validate a UI refactor for type safety and architectural compliance?▼

Validate a UI refactor by running type checks and style guards to confirm that changes within src/app, src/modules, and src/shared comply with explicit architectural boundaries and token-based styling rules.

Does this UI refactoring workflow support managing Naive UI component placement?▼

Yes, the workflow enforces explicit architectural rules including Naive UI placement, ensuring component integration follows standardized boundaries within the shared modules and routing structure.

When do I need route-driven navigation for a UI platform refactor?▼

You need route-driven navigation when refactoring src/app and src/modules to standardize navigation flows, enforce architectural boundaries, and maintain consistency across the UI platform.