Verified:GitHub

feature-workflow

Name: feature-workflow
Availability: InStock
Author: lorenamellado

Coordinate type definitions, validation schemas, API services, hooks, UI components, and tests for feature implementation.

Updated Feb 10, 2026

Search Tags:#typescript #testing #architecture #react #scaffolding #end-to-end #feature-workflow

Ready to run

npx skills add https://github.com/lorenamellado/demo-portal-agents-skills --skill feature-workflow-lorenamellado

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-workflow
Source: https://github.com/lorenamellado/demo-portal-agents-skills/tree/main/.agents/skills/feature-workflow
Command: npx skills add https://github.com/lorenamellado/demo-portal-agents-skills --skill feature-workflow-lorenamellado

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams implement a full feature end-to-end by coordinating multiple specialized sub-skills in the correct order, ensuring consistency with existing types, validations, services, hooks, components, and tests.

Core Features & Use Cases

End-to-end feature orchestration: defines and aligns steps from types to UI to ensure cohesive integration.
Layered development guidance: provides structure for types, validation, service, hook, component, tests, and routing.
Use Case: When starting a new feature, trigger this skill to generate a complete implementation plan and scaffolding across codebase.

Quick Start

Describe the feature to implement and let the skill orchestrate the end-to-end workflow across types, services, components, and tests.

Frequently Asked Questions about feature-workflow

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

FAQPage Schema

How do I orchestrate end-to-end feature implementation in a React and TypeScript codebase?▼

End-to-end feature implementation is orchestrated by coordinating cross-cutting layers like TypeScript types, validation schemas, API services, hooks, and UI components in a strict sequence. This ensures cohesive integration and consistent scaffolding across the entire codebase.

What is the best way to scaffold a new feature across types, services, hooks, and components?▼

Scaffolding a new feature across types, services, hooks, and components requires a layered development approach that enforces structure. It aligns steps from type definitions to UI creation, ensuring validators, API calls, state management, and routing integrate correctly.

Does feature-workflow require a specific folder structure for React components and tests?▼

Feature-workflow enforces a required structure for React components and tests, placing types in types/, validators in utils/validators.ts, services in services/, hooks in hooks/, and routing in pages when applicable, with tests via jest-testing.

Can I use this workflow to generate validation schemas and API services together?▼

You can generate validation schemas and API services together by triggering the workflow when starting a new feature. It automates the creation of validators in utils/validators.ts and API calls in services/, ensuring they align with existing type definitions.

Why does my end-to-end feature delivery fail to integrate state management and routing correctly?▼

End-to-end feature delivery fails to integrate state management and routing when the required layered structure is not followed. Strict coordination of hooks for state and pages for routing is necessary to ensure cross-cutting layers function cohesively within the existing codebase.

When do I need an end-to-end feature workflow for React development?▼

You need an end-to-end feature workflow for React development when a feature requires cross-cutting layers and strict integration with existing codebases. It is designed for scenarios covering TypeScript types, validation, API calls, state management, and routing.