All Skills

Redux-Saga (generator-based) middleware for async side effects — yields declarative effects (call/put/select/takeLatest/delay) instead of imperative async code, watcher-per-slice composition, optimistic updates with rollback. Use when authoring per-slice operations.js, the rootSagas composer, or reviewing saga workers.

Atomic-design guidance for Molecules — functional groups of atoms (SearchBar = input + button + icon; FormField = label + input + error) with a single cohesive purpose. Use when authoring or reviewing components under ui/molecules, composing atoms, or deciding atom vs molecule vs organism.

Atomic-design guidance for Organisms — complex feature-level sections (Header, ProductGrid, CommentSection) that compose molecules, connect to state, handle loading/error/empty states, and own responsive layout decisions. Use when authoring components under ui/organisms or deciding molecule vs organism boundaries.

Skeleton loading placeholders — gray-shape stand-ins that mirror final content dimensions, use subtle shimmer/pulse animation, and prevent layout shift. Use when replacing generic spinners with content-shaped placeholders, reducing perceived latency on slow routes, or preventing CLS on image-heavy cards.

Pure switch/case reducers for the chota-react-saga template — initial-state file, three-phase async cases per CRUD verb, optimistic mutations with `previousState<Items>` rollback, fall-through SUCCESS/ERROR for toggle and delete.

Selector functions for the chota-react-saga template — colocated with each slice, return derived view-data from the saga state shape (isLoading/isContentLoading/isActionLoading/error/<items>/<current>), filter/sort projections that combine slices (e.g. visibleTodos × selectedFilter).

App Shell architecture — the cached HTML/CSS/JS skeleton (header, nav, footer) served instantly via Service Worker while dynamic content streams in. Use when building PWAs, wiring service-worker caches, inlining critical CSS, or adding offline fallbacks and skeleton loading states.

Create product objectives, key results, initiatives, guardrails, and review cadence.

Plan structured workshops with goals, agenda, activities, prompts, decision rules, and follow-ups.

Frame jobs, triggers, desired outcomes, anxieties, and product opportunities.

Write a roadmap narrative that connects customer problems, company goals, bets, and sequencing.

Design team offsites with objectives, agenda flow, exercises, logistics, and post-offsite actions.

Prepare PRINCE2 Closing a Project material: product acceptance, end project report, lessons report, benefits review plan, handover, follow-on actions, and closure recommendation.

Create a practical onboarding plan for a new team member with outcomes, first-week structure, stakeholder introductions, learning path, and manager check-ins.

Create a clear project status brief with progress, risks, blockers, decisions, and next actions.

Compare a product against alternatives by positioning, capabilities, gaps, and strategic moves.

Turn meetings into decisions, owners, open questions, and follow-ups.

Write executive-ready product updates with signal, tradeoffs, risks, and recommendations.

Create a market activation plan with audience, positioning, channels, enablement, and metrics.

Create a delivery plan with goals, capacity, scope, risks, and commitments.

Prepare implementation handoffs with states, flows, assets, edge cases, and acceptance criteria.

Assess launch readiness across product, engineering, support, sales, marketing, risk, and measurement.

Turn research inputs into concise evidence, patterns, confidence levels, and product decisions.

Turn strategy inputs into a clear narrative with stakes, choices, tradeoffs, and next moves.

Specify dashboards around decisions, audiences, questions, metrics, cuts, and refresh rhythm.

Prioritize product work with explicit criteria, scoring, tradeoffs, and decision rationale.

Map the PRINCE2 management products and project documentation needed by process, including startup, initiation, stage control, product delivery, stage boundary, direction gates, and closure.

Analyze product health across acquisition, activation, engagement, retention, quality, and monetization.

Synthesize interviews into themes, contradictions, opportunities, and product implications.

Run PRINCE2 Controlling a Stage: work package tracking, highlight reports, risk and issue control, tolerance checks, change handling, and corrective action planning.

Prepare PRINCE2 Managing a Stage Boundary material: end stage report, next stage plan, updated business case, updated project plan, lessons, risks, issues, and exception plan if needed.

Prepare PRINCE2 Directing a Project gate briefs for project board decisions, including initiation authorization, stage authorization, exception decisions, and closure authorization.

Prepare PRINCE2 Managing Product Delivery material: work package acceptance, team plans, checkpoint reports, quality evidence, delivery confirmation, and handback notes.

Draft product requirements with the problem, users, scope, requirements, metrics, and open decisions.

After cloning a repository, scan for skill definitions and load them on demand. Always use this after cloning any repo.

Use this skill to write and run SQL queries, pull data, build metrics, or answer analytical questions. Always use this skill when you need to query data.