pattern-selector

Guide architectural pattern selection for data, UI, and testing decisions.

2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/yutna/vibe-next-template --skill pattern-selector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pattern-selector
Source: https://github.com/yutna/vibe-next-template/tree/main/.claude/skills/pattern-selector
Command: npx skills add https://github.com/yutna/vibe-next-template --skill pattern-selector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pattern Selector Skill helps engineering teams decide the most appropriate architectural patterns during planning, guiding decisions between data-flow patterns, UI composition approaches, and form-handling strategies.

Core Features & Use Cases

  • Decision Flowcharts covering Data Layer Decisions, Entity Hooks vs Inline Logic, Business Logic Layer, Presenter vs Inline Transform, Form Object vs Zod Schema, State Management, and Communication Patterns.
  • Comprehensive guidance for selecting between Screen/Container/Component architecture, Server Actions vs API Routes, and testing patterns (factories vs inline data).
  • Real-world planning scenarios showing how to apply pattern choices in architecture planning sessions and to align with project constraints.

Quick Start

Provide a planning brief for a feature by selecting the appropriate architectural patterns using the decision flows.

Frequently Asked Questions about pattern-selector

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

FAQPage Schema
How do I choose the right architectural pattern for a new feature?▼

Choosing the right architectural pattern requires evaluating decision flows against project constraints. This skill provides structured criteria covering data-layer choices, UI composition, and form-handling strategies to guide consistent architecture decisions during planning sessions.

When should I use a presenter pattern versus inline transforms?▼

Use a presenter pattern versus inline transforms based on structured decision criteria evaluating your UI architecture. The skill provides explicit scenario-based guidance to determine when presenters offer advantages over inline data transformation approaches.

What is the best way to decide between a form object and a Zod schema?▼

Deciding between a form object and a Zod schema depends on specific decision flowchart criteria. The skill offers comprehensive guidance to evaluate form-handling strategies against your implementation requirements and project constraints.

How do I select between server actions and API routes for my architecture?▼

Selecting between server actions and API routes involves evaluating communication patterns and business logic layer requirements. The skill provides decision flowcharts with explicit criteria to compare these approaches against your data-flow and architectural needs.

Can I use this for planning screen, container, and component architecture?▼

Yes, you can use this for planning screen, container, and component architecture. The skill provides comprehensive guidance for selecting UI composition approaches and aligning pattern choices with real-world planning scenarios and project constraints.