select-package

Name: select-package
Availability: InStock
Author: Wayne

Classifies requests by runtime and domain to select the fe-tools package directory before coding.

207|39|Updated Aug 29, 2017

Search Tags:#workflow #multi-runtime #fe-tools #select-package #package-routing #runtime-classification

Ready to run

npx skills add https://github.com/MichealWayne/fe-tools --skill select-package

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: select-package
Source: https://github.com/MichealWayne/fe-tools/tree/main/utils/skills/select-package
Command: npx skills add https://github.com/MichealWayne/fe-tools --skill select-package

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classify requests by runtime and domain to determine the correct fe-tools package, reducing misrouting and refactoring time.

Core Features & Use Cases

Classify by runtime and domain to map to the correct package directory (e.g., packages/utils, packages/web-utils, packages/node-utils).
Split cross-runtime requests into per-package functions and ensure explicit selection before coding.
Support multi-package requests by proposing parallel workflows with clear packaging.

Quick Start

Analyze a user request and route it to the correct fe-tools package directory before implementation.

Frequently Asked Questions about select-package

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

FAQPage Schema

How do I route front-end utility requests to the correct package directory?▼

Cross-runtime requests are split into per-package functions, ensuring explicit selection before coding and proposing parallel workflows with clear packaging to handle multi-package requirements effectively.

Why does my multi-runtime feature implementation cause package misrouting?▼

Multi-runtime feature implementation causes package misrouting when explicit selection is skipped; classifying the requirement by runtime and domain first enforces choosing the correct package path and documents it to reduce refactoring time.

What is the best way to split cross-runtime requests into per-package functions?▼

The best way to split cross-runtime requests is to classify them by domain and runtime, routing each part to the correct package directory and enforcing explicit selection before coding to ensure clear packaging.

Can I use package routing for multi-package feature requests?▼

Yes, you can use package routing for multi-package requests by proposing parallel workflows that classify the requirement by runtime and domain, ensuring each package gets clear and explicit packaging.

How to document the chosen package path before implementing new fe-tools features?▼

Document the chosen package path by classifying the requirement by runtime and domain first, which enforces explicit selection before coding and records the correct package directory for implementation.