wire-feature

Scaffold full-stack features across server, shared types, and client layers.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/twlines/maslow --skill wire-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wire-feature
Source: https://github.com/twlines/maslow/tree/main/.claude/skills/wire-feature
Command: npx skills add https://github.com/twlines/maslow --skill wire-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation and integration of new features across the entire application stack (server, shared types, client), ensuring consistency and preventing missed touchpoints.

Core Features & Use Cases

  • Full-Stack Scaffolding: Generates necessary code for new REST endpoints or WebSocket messages across server, shared types, and client layers.
  • Touch Point Identification: Automatically identifies all files and code sections requiring modification for a new feature.
  • Use Case: When adding a new API endpoint for user profiles, this skill will scaffold the server route, the shared type definitions, the API client method, and the UI integration points.

Quick Start

Use the wire-feature skill to scaffold a new REST endpoint for the 'user-profile' feature.

Frequently Asked Questions about wire-feature

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

FAQPage Schema
How do I scaffold full-stack features across server and client layers?

Scaffolding full-stack features involves generating code for server route handlers, shared type definitions, API client methods, and UI integration points. This process ensures consistency and prevents missed touchpoints across server, shared types, and client layers.

What's the best way to add a new API endpoint and wire it to the client?

The best way to wire a new API endpoint is to identify all touch points and generate the server route handler, service methods, persistence queries, shared types, and API client methods. This guarantees completeness across the server, shared types, and client layers.

Can I scaffold WebSocket message types across my application stack?

Yes, you can scaffold WebSocket message types across your application stack. The process identifies all required touch points and generates the necessary server handlers, shared type definitions, and client UI integration code for the new WebSocket messages.

How do I identify all touch points when adding new full-stack features?

To identify all touch points for new full-stack features, you map out the required server routes, service methods, persistence queries, shared types, API client methods, and UI sections. This ensures every file and code section needing modification is covered.

Does full-stack scaffolding work for both REST endpoints and WebSocket messages?

Yes, full-stack scaffolding works for both new REST endpoints and WebSocket messages. It generates the required server route handlers, shared type definitions, API client methods, and UI integration points to maintain consistency across the application architecture.

Why do I need to generate shared type definitions when adding server route handlers?

Generating shared type definitions when adding server route handlers ensures type consistency across the server, shared types, and client layers. It acts as the contract for API client methods and UI integration, preventing missed touchpoints in multi-layered applications.