Packs

1 pack

@alirezarezvani

Business Operations

Internal BizOps domain. v2.8.0 ships 7 skills: orchestrator + process-mapper (BPMN/bottleneck/cycle-time, Lean+TOC) + vendor-management (scorecard+SLA+3rd-party risk, NIST SP 800-161/ISO 27036) + capacity-planner (Erlang-C queueing math for ops teams, NOT engineering) + internal-comms (ADKAR+Kotter 8-step, NOT marketing) + knowledge-ops (SOP+runbook+KB hygiene with 5W2H, context: fork) + procureme

3 skills · pack

Results for “planner”

8 skills

frontend-data-fetching-planner

Use this when a frontend feature needs a clear plan for server data fetching, caching, invalidation, mutations, optimistic UI, or auth-aware data loading.

responsive-design-planner

Use when a web product or component needs responsive layout planning across mobile, tablet, and desktop. Trigger on requests about breakpoints, layout adaptation, content priority, or mobile-first UI behavior.

frontend-scaffold-planner

Plan the frontend application structure for a product or feature. Use when the team needs route structure, feature modules, state boundaries, design-system needs, and frontend delivery sequencing based on defined screens and flows.

More results

frontend-component-planner

Use this when the team needs a component breakdown for a screen or feature that may or may not be React-specific. Trigger on requests to plan component responsibilities, composition, states, and boundaries before implementation.

product-builder-orchestrator

Use when the request is broad and spans idea evaluation, MVP planning, UX, frontend, backend, database, auth, integrations, and launch strategy. Trigger on asks like "build this app", "turn this idea into a product", "design the whole system", or "plan everything end to end".

Plan screens, views, and page responsibilities for a product flow. Use when user journeys already exist and the team needs a screen inventory, screen purpose, key states, and component-level responsibilities without jumping into visual styling too early.

frontend-architecture-planner

Use when the team needs route structure, feature modules, design-system boundaries, and frontend responsibilities for a React, Next.js, or Tailwind application. Trigger on requests about frontend architecture, app structure, pages, modules, or client-side delivery planning.

Integrate Uniswap liquidity provisioning (LP) into applications via the LP REST API. Use when the user says "LP API", "liquidity provisioning API", "provide liquidity programmatically", "create LP position via API", "add liquidity via API", "increase liquidity", "decrease liquidity", "remove liquidity", "claim LP fees", "collect LP fees", "manage LP positions in code", or mentions building a backend, bot, or frontend that creates or manages Uniswap v2/v3/v4 liquidity positions through an API. Also use when debugging LP API calls (e.g. /lp/create, /lp/check_approval, /lp/increase, /lp/decrease, /lp/claim_fees), unexpected response fields, the approval or EIP-712 permit flow, or transaction-building errors for liquidity positions. For generating deep links to the Uniswap web app instead of calling the API, use the liquidity-planner skill; for using the Uniswap v4 SDK directly rather than the REST API, use the v4-sdk-integration skill.