lms-mobile-refactoring

Refactor Tuitional LMS Mobile modules and remove dead code.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/raomanzar/TuitionalLMSMobile --skill lms-mobile-refactoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lms-mobile-refactoring
Source: https://github.com/raomanzar/TuitionalLMSMobile/tree/main/.claude/skills/lms-mobile-refactoring
Command: npx skills add https://github.com/raomanzar/TuitionalLMSMobile --skill lms-mobile-refactoring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill assists developers in refactoring and cleaning up the Tuitional LMS Mobile app codebase, ensuring consistency, reducing dead code, and aligning modules with the canonical pattern.

Core Features & Use Cases

  • Codebase Cleanup: Remove unused exports and dead code to improve maintainability.
  • Module Refactoring: Migrate stub modules to match the users pattern, enforcing naming and structural conventions.
  • Quality Enforcement: Validate import boundaries, naming standards, and layer-skip violations.
  • Use Case: A developer needs to bring the enrollments module in line with the canonical users pattern, ensuring it passes all code quality checks before deployment.

Quick Start

Use the lms-mobile-refactoring skill to identify and clean up the code, then refactor modules to follow the canonical pattern.

Frequently Asked Questions about lms-mobile-refactoring

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

FAQPage Schema
How do I remove dead code and unused exports in a React Native codebase?

Dead code removal in a React Native codebase involves identifying and eliminating unused exports to improve maintainability. This process reduces code bloat and ensures only active, necessary modules remain in the project.

How do I enforce naming conventions and layer boundaries in a TypeScript mobile app?

Enforcing naming conventions and layer boundaries in a TypeScript app requires validating import boundaries and checking for layer-skip violations. This ensures consistent, maintainable client-side architecture across the project.

What is the best way to refactor a stub module to match a canonical pattern?

Refactoring a stub module to match a canonical pattern involves migrating the module structure to align with an established reference module like the users pattern. This enforces structural conventions and naming standards.

Do I need additional dependencies to enforce code quality in a React Native TypeScript project?

No additional dependencies are required to enforce code quality beyond standard linting and TypeScript tools. The refactoring process operates using existing tooling to validate standards and clean up the codebase.

When should I perform module migration and code cleanup on my mobile app?

Module migration and code cleanup should be performed when stub modules need alignment with canonical patterns or before deployment to ensure all code quality checks pass. This maintains a consistent and maintainable client-side architecture.