slices AI Agent Skills
Browse 35 skills related to slices
zustand
lobehubZustand state management guide. Use when working with store code (src/store/**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.
Frontend Architecture
exceptionlessSvelte SPA architecture for Exceptionless. Route groups, lib structure, API client, feature slices, and barrel exports. Keywords: route groups, $lib, feature slices, api-client, barrel exports, index.ts, vertical slices, shared components, generated models, ClientApp structure
zustand-state-management
Build type-safe global state in React with Zustand. Supports TypeScript, persist middleware, devtools, slices pattern, and Next.js SSR with hydration handling. Prevents 6 documented errors. Use when setting up React state, migrating from Redux/Context, or troubleshooting hydration errors, TypeScript inference, infinite render loops, or persist race conditions.
zustand
a5c-aiZustand state management patterns including store creation, middleware, persistence, slices, and DevTools integration.
phasing
Group slices into risk-optimized phases with timeline generation
workflow-feature-shipper
HeyvhuangUse when you need to ship a single PR-sized feature end-to-end (plan -> implement -> verify) with artifacts. Ship core product features quickly in a Next.js codebase: turn a feature idea into an executable plan, implement in PR-sized slices, and keep artifacts under runs/ (or OpenSpec changes/ when available). Supports plan-only mode for early scoping. For prototype UI work, include a demo-ready wow moment (animation/micro-interaction) by default unless user opts out.
zustand-patterns
yonatangrossZustand 5.x state management with slices, middleware, Immer, useShallow, and persistence patterns for React applications. Use when building state management with Zustand.
State Management with Zustand
jhl-labsZustand를 사용한 전역 상태 관리 패턴. SEPilot Desktop의 chat-store, extension-slices 등 실제 구현 기반. Store 설계, Slice 패턴, Persistence, Middleware 사용법을 다룹니다.
slice
tkerseySlice a plan into a DAG in SLICES.md; validate it; and pick/mark the next ready slice to execute. Use when asked to break a plan into slices, generate or repair `SLICES.md`, or choose the next ready slice to work on.
select
tkerseySwarm-ready work selector: choose one source (invocation list, `SLICES.md`, or `plan-N.md`), refine it into dependency-aware atomic tasks, and emit an OrchPlan (waves + delegation) plus optional pipelines. Use for prompts like `$select`, `use $select`, `pick the next ready slice`, `orchestrate workers from SLICES`, or `what should run in parallel next`. Plan-only; no writeback; orchestration-agnostic.
commit
tkerseyCreate micro-commits (minimal incision) with at least one validation signal per commit. Use when requests say "split this into micro commits," "stage only the minimal change and commit," "keep commits tiny while checks pass," or when parallel workers/slices need isolated, reviewable commits.
mesh
tkerseySwarm coordinator activated only by explicit `$mesh` invocation. Trigger cues/keywords: orchestrate subagents/workers, execute ready `$st` slices/tasks, run propose/critique/synthesize/vote cycles, coordinate concurrent workers, require consensus + validation before completion, and persist learnings via `$learnings`.
user-story-mapping
melodic-softwareJeff Patton's User Story Mapping technique for Agile discovery. Visualizes user journey as a map, identifies backbone activities, walking skeleton, and release slices. Use when organizing requirements into deliverable increments or defining MVP scope.
use-case-2.0
melodic-softwareUse Case 2.0 methodology by Ivar Jacobson. Covers use case slices, lightweight documentation, user story derivation, and value-driven prioritization. Modern approach to use case modeling for agile teams.
zustand-state-management
ovachieverBuild type-safe global state in React applications with Zustand. Supports TypeScript, persist middleware, devtools, slices pattern, and Next.js SSR. Use when setting up React state, migrating from Redux/Context API, implementing localStorage persistence, or troubleshooting Next.js hydration errors, TypeScript inference issues, or infinite render loops.
dotnet-feature
jguadagnoExpert .NET 10 Full-Stack Developer skill. Use this when implementing new features, vertical slices, or modifying existing logic in the JJGNET Broadcasting application. It covers Domain, Data (EF Core), Managers, API, and Web.
zustand-state-management
jackspaceProduction-tested setup for Zustand state management in React applications with TypeScript. This skill provides comprehensive patterns for building scalable, type-safe global state. Use when: setting up global state in React, migrating from Redux or Context API, implementing state persistence with localStorage, configuring TypeScript with Zustand, using slices pattern for modular stores, adding devtools middleware for debugging, handling Next.js SSR hydration, or encountering hydration errors, TypeScript inference issues, or persist middleware problems. Prevents 5 documented issues: Next.js hydration mismatches, TypeScript double parentheses syntax errors, persist middleware export errors, infinite render loops, and slices pattern type inference failures. Keywords: zustand, state management, React state, TypeScript state, persist middleware, devtools, slices pattern, global state, React hooks, create store, useBoundStore, StateCreator, hydration error, text content mismatch, infinite render, localStorage, sessionStorage, immer middleware, shallow equality, selector pattern, zustand v5
zustand-expert
YuniorGlezSenior State Architect for React 19 and Next.js 16.1+ applications. Specialist in Zustand v5, SSR-safe stores, and slices pattern for large-scale state management.
hamburger-method
eferroApplies the Hamburger Method to slice features into vertical deliverable pieces. Use when user asks how to slice work, break down features into layers, or wants to deliver incrementally. Helps generate 4-5 options per layer and compose minimal vertical slices. Use when: - Feature feels large but not obviously splittable with story-splitting heuristics - User asks "how to slice" or "how to deliver incrementally" - Need to generate multiple implementation options - Want to compose end-to-end vertical slices Do NOT use when: - Story has obvious "and", "or", "manage" indicators (use story-splitting instead) - User is asking HOW to implement (use micro-steps-coach instead) - Feature is already small (< 1 day work)
agent-contracts-backend-runtime
yatarousan0227Build an API-oriented agent using AgentRuntime/StreamingRuntime with predictable request/response slices and session support.
agent-contracts-interactive-flow
yatarousan0227Build question/answer style agents using InteractiveNode, explicit routing, and workflow slices.
agent-contracts-app-builder
yatarousan0227Build a production-minded AI agent using agent-contracts (contracts, slices, validation, graph, runtime, CLI tooling).
mlx-dev
ettrickshepherdWrite correct, idiomatic Apple MLX code for Apple Silicon ML. Use when working with MLX arrays, neural networks, training loops, lazy evaluation, unified memory, mx.eval, mx.compile, Metal GPU, memory optimization, quantization, or Apple Silicon performance. Covers critical API differences from PyTorch/NumPy, array indexing gotchas (lists must be mx.array, slices create copies), NHWC format for Conv2d, __call__ not forward(), float64 CPU-only, mlx-lm integration, and debugging patterns.
dotnet-feature
cwoodruffExpert .NET 10 Full-Stack Developer skill. Use this when implementing new features, vertical slices, or modifying existing logic in the MoreSpeakers application. It covers Domain, Data (EF Core), Managers, and Web (Razor Pages + HTMX).
story-planner
SDiamante13Break application into thin vertical slices with clear acceptance criteria
Feature-Sliced Design
constellosThis skill should be used when the user asks to "implement FSD", "use Feature-Sliced Design", "organize architecture", "structure project folders", "set up FSD layers", "create feature slices", "refactor to FSD", "add FSD structure", or mentions "feature slices", "layered architecture", "FSD methodology", "architectural organization", "views layer", "entities layer", "shared layer", "Next.js with FSD", or "Turborepo FSD structure". Provides comprehensive guidance for implementing Feature-Sliced Design methodology in Next.js applications with custom 'views' layer naming.
tech-trpc
ravnhqtRPC router architecture, procedure design, and Vertical Slice Architecture patterns. Use when building tRPC APIs, designing procedures, or structuring backend slices.
Testing Spring Apps
gitwalterJUnit 5 patterns, Spring Boot Test slices (@WebMvcTest, @DataJpaTest), MockMvc for API testing, Testcontainers for integration tests (PostgreSQL, Redis, Kafka), Mockito patterns, Test fixtures with @TestConfiguration
Testing with JUnit & Mockito
ngxtmJUnit 5, Mockito, Spring test slices, integration testing, and test organization.
spring-testing
gitwalterJUnit 5 patterns, Spring Boot Test slices (@WebMvcTest, @DataJpaTest), MockMvc for API testing, Testcontainers for integration tests (PostgreSQL, Redis, Kafka), Mockito patterns, Test fixtures with @TestConfiguration
redux-toolkit
joabgonzalezPredictable state management with Redux Toolkit. Trigger: When implementing Redux, creating slices, or managing global state.
prd-to-issues
sadiksaifiBreaks a PRD into independently-grabbable GitHub issues using vertical slices (tracer bullets). Use when decomposing a PRD into implementation work, creating tracer-bullet issues, or when the user says "break down PRD," "create issues from PRD," or "/prd-to-issues."
dotnet-architecture-patterns
wshaddixOrganizing APIs at scale. Vertical slices, request pipelines, caching, error handling, idempotency.
zustand-5
fmurillodevZustand 5 state management patterns. Use when implementing client-side state with Zustand (stores, selectors, persist middleware, slices).
mlx-dev
luqmannurhakimbazmanWrite correct, idiomatic Apple MLX code for Apple Silicon ML. Use when working with MLX arrays, neural networks, training loops, lazy evaluation, unified memory, mx.eval, mx.compile, Metal GPU, memory optimization, quantization, or Apple Silicon performance. Covers critical API differences from PyTorch/NumPy, array indexing gotchas (lists must be mx.array, slices create copies), NHWC format for Conv2d, __call__ not forward(), float64 CPU-only, mlx-lm integration, and debugging patterns.
