
Claude Skills by Intense-Visions
github.com/Intense-Visions> Seed databases idempotently with prisma/seed.ts, --seed flag, and environment branching
> Implement soft deletes in Prisma with middleware or $extends query extensions and deletedAt pattern
> Execute atomic operations with Prisma $transaction, interactive transactions, and nested writes
> Use generated Prisma types like XxxCreateInput, XxxWhereInput, $Enums, and validator utilities
> Turn a client diagram + conversation into a Business Requirements Document and a resolved gap-list, then seed the harness pipeline. The pre-inception front door: gather requirements with AI, feed them in, and let the existing flow continue as it does today.
> Turn one picked work item into a durable PRD — user stories, testable acceptance criteria, and prioritization — through a guided interview. The product-management middle between `product-advisor` (BRD) and `harness-brainstorming` (spec). Authors requirements; never authors the spec.
> Modern React patterns for 2025-2026 including React 19, Compiler, and AI-integrated UI
> Render React entirely in the browser for highly interactive single-page applications
> Build multi-part components that share state implicitly via context
> Build responsive UIs using React 18 concurrent features and transitions
> Separate data-fetching containers from stateless presentational components
> Share state across the component tree without prop drilling using React Context
> Load modules on demand to reduce initial bundle size and improve startup performance
> Extend component behavior by wrapping in a higher-order component
> Reuse stateful logic across components via custom hooks
> Hydrate only interactive UI islands, leaving static content as HTML
> Prevent expensive re-renders and recomputations with React memoization APIs
> Delay hydration of below-fold or non-critical components to improve TTI
> Make data available to any component in the tree without prop drilling
> Share stateful logic by passing a render function as a prop
> Run components on the server to eliminate client JavaScript and enable direct data access
> Pre-render React components on the server for improved SEO and initial load performance
> Choose the right state management approach for your React application scale
> Bundle all dependencies at build time for predictable loading performance
> Declaratively handle async loading states with React Suspense boundaries
> Normalize entity collections with createEntityAdapter for O(1) lookups and pre-built CRUD reducers
> React to dispatched actions and state changes with createListenerMiddleware for structured side effects
> Persist and rehydrate Redux state across browser sessions with redux-persist or manual localStorage strategies
> Apply optimistic and pessimistic cache updates with onQueryStarted for instant UI feedback with automatic rollback
> Define query and mutation endpoints with cache tag invalidation, response transformation, and auto-generated hooks
> Configure RTK Query with createApi and fetchBaseQuery for automatic caching, deduplication, and loading state management
> Derive and memoize computed state with createSelector to avoid redundant calculations and unnecessary re-renders
> Organize Redux state into self-contained slices using createSlice for co-located reducers, actions, and selectors
> Configure the Redux store with configureStore, typed hooks, middleware, and Provider wiring
> Test Redux slices, thunks, selectors, and connected components with focused, maintainable test strategies
> Handle async operations with createAsyncThunk for structured pending/fulfilled/rejected lifecycle management
> Type Redux state, actions, thunks, and hooks with full inference and minimal manual annotation
> Isolate failures by partitioning resources so one failing component cannot exhaust capacity for others
> Validate resilience by injecting controlled failures to verify that fallbacks, retries, and circuit breakers work under real conditions
> Protect services from cascading failures by stopping requests to unhealthy dependencies until they recover
> Handle permanently failing messages with dead letter queues for safe inspection, alerting, and reprocessing
> Provide degraded but functional responses when primary operations fail, ensuring users always get a result
> Implement health check endpoints for service readiness, liveness, and dependency monitoring
> Ensure safe retries by making operations produce the same result regardless of how many times they execute
> Control request throughput with token bucket, sliding window, and fixed window algorithms to protect services from overload
> Handle transient failures with configurable retry strategies, exponential backoff, and jitter
> Prevent resource exhaustion and hung requests with timeouts, AbortController, and deadline propagation
> Evaluate access decisions using attributes of the subject, resource, action, and environment -- eliminating role explosion by expressing authorization as policy rules over contextual data
> Public-key cryptography for key exchange, digital signatures, and identity verification > -- Ed25519 for signatures, X25519 for key exchange, RSA-2048+ only for legacy > compatibility
> Model multi-step adversary strategies as goal-oriented tree decompositions -- revealing which attack paths are cheapest and which defenses yield the highest leverage