Skip to content
Skills Library
Programming · Building & coding

fec-refactoring-api

/fec-refactoring-api

Use when behavior-preserving frontend refactoring focuses on function API shape, flags, dependencies, mutability, construction, or command/function trade-offs, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.

Licence
MIT
Last repository change
26.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when behavior-preserving frontend refactoring focuses on function API shape, flags, dependencies, mutability, construction, or command/function trade-offs, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.

Original author description

Use when behavior-preserving frontend refactoring focuses on function API shape, flags, dependencies, mutability, construction, or command/function trade-offs, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.

How it works

  1. Overview
  2. Procedure
  3. Quick Reference
  4. Common Mistakes
Original SKILL.md headings · 22 lines, 156 words
SKILL.md preview
---
name: fec-refactoring-api
description: Use when behavior-preserving frontend refactoring focuses on function API shape, flags, dependencies, mutability, construction, or command/function trade-offs, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.
---

# API Refactorings

## Overview
Use this family after evidence identifies a fitting structural transformation. Apply one primary technique at a time and verify immediately.

## Procedure
1. Confirm the selected technique and its preconditions in [API Refactorings](references/api-refactorings.md).
2. Record affected behavior and a diff budget.
3. Apply only the selected technique's smallest viable step.
4. Verify the step before composing another transformation.
5. Stop and reassess when public contracts, lifecycle, state identity, or actual scope exceed expectations.

## Quick Reference
The family reference contains 10 canonical techniques with intent, signals, avoid conditions, mechanics, preservation checkpoints, smell links, composition hints, JavaScript/TypeScript notes, React/Vue notes, adaptation guidance, and original frontend examples.

## Common Mistakes
- Choosing a technique by name without checking its preconditions.
- Combining several structural intentions in one diff.
- Assuming a classical class-based form is mandatory in modern frontend code.
- Treating passing tests as proof when the relevant behavior is not covered.
Files in this package (2)
  • SKILL.md 1 KB
  • references/api-refactorings.md 22 KB

Versions

The database has no other skills named fec-refactoring-api.

Database snapshot: 13.11.2026 · package version b40e778bd37a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100fec-refactoring-functions
    Use when behavior-preserving frontend refactoring focuses on function structure, naming, parameters, shared context, or phase boundaries, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.
  • 100fec-refactoring-move-features
    Use when behavior-preserving frontend refactoring focuses on behavior/data ownership, statement placement, loops, or dead-code knowledge, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.
  • 95vue-app
    Build and evolve modular Vue applications in JavaScript or TypeScript. Use for Vue components, composables, routes, state, forms, API integration, feature architecture, accessibility, and production verification.
  • 100vue
    Vue 3 conventions, Composition API patterns, SFC structure, reactivity, composables, and TypeScript integration. Invoke whenever task involves any interaction with Vue code — writing, reviewing, refactoring, debugging, or understanding .vue files, composables, and Vue component architecture.
  • 95design-patterns
    Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
  • 100frontend-code-review
    Use when 用户需要审查前端代码(React/Vue/Next.js/TypeScript/Tailwind等)、检查代码质量、性能问题、可维护性、安全漏洞、最佳实践落地时。触发场景:前端代码评审、前端代码优化、React/Vue代码检查、TypeScript代码审查、前端性能优化、前端安全审计、前端代码规范检查。

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.