shared-model-refactor — community shared-model-refactor, QuickApp, community, ide skills

v1.0.0
GitHub

About this Skill

Perfect for Code Refactoring Agents needing advanced React optimization capabilities. Refactor shared server/client TypeScript contracts into a common models directory and eliminate cross-boundary imports (for example client importing server classes). Use when client code depends on se

jts599 jts599
[0]
[0]
Updated: 2/22/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
32
Canonical Locale
en
Detected Body Locale
en

Perfect for Code Refactoring Agents needing advanced React optimization capabilities. Refactor shared server/client TypeScript contracts into a common models directory and eliminate cross-boundary imports (for example client importing server classes). Use when client code depends on se

Core Value

Empowers agents to refactor code for shared contract imports, utilizing `rg` for boundary violation detection and optimizing server and client-side applications with movable symbols like interfaces and type aliases.

Ideal Agent Persona

Perfect for Code Refactoring Agents needing advanced React optimization capabilities.

↓ Capabilities Granted for shared-model-refactor

Refactoring code to import shared contracts from a single location
Identifying and resolving boundary violations between server and client-side imports
Optimizing React apps by moving pure contracts to a centralized location

! Prerequisites & Limits

  • Requires access to React application codebase
  • Limited to React applications with server and client-side components
  • Dependent on `rg` command-line tool for search functionality

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is shared-model-refactor?

Perfect for Code Refactoring Agents needing advanced React optimization capabilities. Refactor shared server/client TypeScript contracts into a common models directory and eliminate cross-boundary imports (for example client importing server classes). Use when client code depends on se

How do I install shared-model-refactor?

Run the command: npx killer-skills add jts599/QuickApp/shared-model-refactor. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for shared-model-refactor?

Key use cases include: Refactoring code to import shared contracts from a single location, Identifying and resolving boundary violations between server and client-side imports, Optimizing React apps by moving pure contracts to a centralized location.

Which IDEs are compatible with shared-model-refactor?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for shared-model-refactor?

Requires access to React application codebase. Limited to React applications with server and client-side components. Dependent on `rg` command-line tool for search functionality.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add jts599/QuickApp/shared-model-refactor. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use shared-model-refactor immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

shared-model-refactor

Install shared-model-refactor, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Shared Model Refactor

Refactor code so server and client both import shared contracts from sampleImplementation/models/ instead of importing each other.

Workflow

  1. Find boundary violations.
  • Run:
    • rg -n "from ['\"].*server/|from ['\"].*client/" sampleImplementation src test -S
  • Identify client imports from sampleImplementation/server/* and server imports from sampleImplementation/client/*.
  1. Identify movable symbols.
  • Move only pure contracts:
    • interfaces
    • type aliases
    • enums/constants used as DTO/schema contracts
  • Do not move implementation/runtime code:
    • decorated classes
    • business logic
    • DB/network utilities
  1. Create model files.
  • Place extracted contracts in sampleImplementation/models/.
  • Use feature-based files (for example sampleImplementation/models/sampleView.ts).
  • Keep files side-effect free.
  1. Update imports.
  • Update server and client to import contracts from sampleImplementation/models/*.
  • For NodeNext, use explicit .js extensions in TS imports.
  • Prefer import type for type-only imports.
  1. Update client generation templates/runtime.
  • Ensure generated client code imports contracts from models/, not server class modules.
  • If generator currently infers types via server class imports, switch generation to explicit model imports per controller.
  1. Regenerate generated client files.
  • Run generation command(s) after template changes.
  1. Validate.
  • Run:
    • npm run typecheck
    • npm test
    • cd sampleImplementation && npm run build
  • Confirm no client file imports from sampleImplementation/server/*.

File Organization Rules

  • sampleImplementation/models/ is the only shared contract boundary.
  • Server code may import from models/ and src/.
  • Client code may import from models/ and src/client runtime APIs.
  • Client code must not import from sampleImplementation/server/.

Refactor Heuristics

  • Keep model names aligned with domain language.
  • Split large contract files by feature, not by type-kind.
  • Do not duplicate contracts in both server and client.
  • If a contract is only used on one side, keep it local.

Acceptance Criteria

  • Zero cross-boundary implementation imports between server/ and client/.
  • Shared DTO/view-data/method contracts live under sampleImplementation/models/.
  • Generated client output compiles and no longer depends on server class imports.
  • Full typecheck/tests/build pass.

Related Skills

Looking for an alternative to shared-model-refactor or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer