All authors
Claude Skills by Lu1sDV
github.com/Lu1sDV86 skills4 installs149 views
- Python Api DesignUse when designing or reviewing Python public APIs and compatibility, schema evolution, static-checker coverage, generic type contracts, Protocol/ABC boundaries, TypedDict schemas, dataclass invariants, dependency injection, or SOLID and design patterns: factories, builders, adapters, decorators, state machines, shallow immutability, cooperative MRO, and descriptors.Votes: 0GitHub stars: 2
- Python ConcurrencyUse when choosing or debugging Python threads, process pools, asyncio tasks, TaskGroup cancellation or early termination, timeouts, bounded queues, worker shutdown, deadlocks, GIL assumptions, free-threaded CPython, multiple interpreters, or AnyIO/Trio cancellation differences. Targets the latest stable CPython baseline.Votes: 0GitHub stars: 2
- Python IdiomaticUse when writing or reviewing Python language semantics, fixing aliasing, mutable defaults, late-bound closures, `locals()` snapshots, exhausted generators, import cycles, swallowed exceptions, or resource leaks; choosing comprehensions, decorators, context managers, match statements, or Python environment/debugging tools.Votes: 0GitHub stars: 2
- Python PerformanceUse when profiling, benchmarking, or optimizing Python CPU, memory, I/O, database, concurrency, startup, or numerical workloads; investigating leaks and performance regressions; reviewing optimization proposals; or validating before/after performance without changing behavior.Votes: 0GitHub stars: 2
- Python StdlibUse when choosing or debugging Python standard-library APIs for iteration, caching, files, timestamps, JSON/CSV/TOML, regex, logging, dataclasses, resource cleanup, subprocesses, or AST-based source analysis, especially versioned parser, boundary and data-loss bugs.Votes: 0GitHub stars: 2
- Python System DesignUse when structuring Python packages or modular monoliths, choosing Django, Flask, FastAPI, WSGI or ASGI, or designing durable jobs, database transaction ownership, startup configuration/hooks, secrets, containers and operational boundaries.Votes: 0GitHub stars: 2
- Python TddUse when implementing Python behavior test-first, reproducing bugs, characterizing legacy code, or applying red-green-refactor with pytest/unittest, fixtures, patch lookup, deterministic I/O and clocks, or Hypothesis properties. Covers coverage/mutation limits, not system-wide strategy or benchmarking.Votes: 0GitHub stars: 2
- React Components TypescriptUse when designing or reviewing React components: composition and `children`, prop drilling, boolean-prop sprawl, discriminated props, list `key` bugs and state resets, components defined inside components, error boundaries, `{count && <X/>}` rendering "0", controlled vs uncontrolled inputs, impure render, default vs named exports, or TypeScript with React (`ReactNode`, `React.FC`, event types, typing hooks, `defaultProps`/`propTypes` removed in 19, `JSX` namespace).Votes: 0GitHub stars: 2
- React Hooks StateUse when writing or reviewing React Effects, `useEffect` dependency arrays or cleanup, "You Might Not Need an Effect" derived state, `useEffectEvent`, `useRef`, custom hooks, Rules of Hooks, `useState`/`useReducer`, Context re-renders and prop drilling, where state should live, Redux Toolkit/Zustand/Jotai selectors (`useShallow`, infinite loop), Strict Mode double effects, `window is not defined` in `useState`, or stale closures.Votes: 0GitHub stars: 2
- React PerformanceUse when a React UI is slow, janky or has poor INP; reviewing `useMemo`, `useCallback`, `memo` or React Compiler (`babel-plugin-react-compiler`, `"use no memo"`) changes; diagnosing re-renders with the Profiler; using `useTransition`, `useDeferredValue`, `<Activity>`, `React.lazy`, `next/dynamic`, `optimizePackageImports`, barrel imports, or virtualizing and `content-visibility` for long lists.Votes: 0GitHub stars: 2
- React Server DataUse when fetching data in React (Effect races and stale responses, waterfalls, TanStack Query v5 `isPending`/`gcTime`/`staleTime`/invalidation, SWR), choosing Server vs Client Components (`'use client'` boundary, async components, `use(promise)`, `React.cache`), writing Server Functions (`'use server'`, auth, validation, Data Access Layer, `server-only`), using React 19 Actions (`useActionState`, `useOptimistic`, `useFormStatus`, ref as prop), or debugging Suspense, streaming and hydration mi...Votes: 0GitHub stars: 2
- React Testing A11yUse when writing, fixing, or reviewing React tests with React Testing Library, user-event, MSW, jest-axe or Playwright: "not wrapped in act(...)" warnings, getByRole/findBy/waitFor flakiness, fireEvent vs userEvent, renderHook, snapshot or mock disputes, async Server Component testing; or accessible React UI: semantic HTML vs ARIA, labels, keyboard and focus, route-change announcements, live regions, dialogs, jsx-a11y/axe findings, WCAG 2.2, and dangerouslySetInnerHTML XSS.Votes: 0GitHub stars: 2
- Rust AlgorithmsUse when choosing Rust collections or implementing and reviewing algorithmic solutions: two pointers, sliding windows, binary search, prefix sums, monotonic stacks, hash maps, streaming medians, intervals, cyclic sort, BFS/DFS, backtracking, dynamic programming, greedy algorithms, topological sort, union-find, tries, or bit manipulation. Covers invariants, complexity, empty inputs, overflow, and UTF-8 correctness rather than general Rust syntax.Votes: 0GitHub stars: 2
- Rust Api DesignUse when designing or reviewing Rust public APIs, trait boundaries, builders, newtypes, typestate transitions, enum versus dyn dispatch, or applying SOLID and creational, structural, or behavioral design patterns without class hierarchies. Triggers include dyn compatibility, dependency injection, API evolution, adapters, decorators, factories, visitors, and ownership-aware interfaces.Votes: 0GitHub stars: 2
- Rust ConcurrencyUse when implementing or debugging Rust threads, Send/Sync bounds, Arc and synchronization, channels, Tokio async tasks, cancellation, graceful shutdown, backpressure, deadlocks, or choosing Rayon for CPU-bound parallel work.Votes: 0GitHub stars: 2
- Rust GuidelinesUse when writing, refactoring, or reviewing Rust against API and engineering guidelines, auditing crate readiness, or defining ownership, error, safety, and allocation contracts. Covers naming, public APIs, interoperability, documentation, macros, and verification. Not a Rust tutorial or profiling playbook.Votes: 0GitHub stars: 2
- Rust IdiomaticUse when writing or reviewing ordinary Rust, fixing move/borrow/lifetime errors, handling Option or Result, choosing standard-library string/iterator/I/O APIs, or configuring Cargo workspaces, rustfmt, Clippy, and rust-analyzer. Covers UTF-8, partial moves, allocation semantics, and production error propagation; use specialized skills for API architecture, concurrency, or test-driven work.Votes: 0GitHub stars: 2
- Rust MacrosUse when writing or debugging Rust macro_rules! matchers, repetitions, hygiene, $crate exports, edition-dependent fragments, or procedural derive, attribute, and function-like macros using syn and quote; includes expansion and diagnostic tests.Votes: 0GitHub stars: 2
- Rust SafetyUse when auditing Rust safety or security, writing unsafe abstractions or C FFI/C-ABI bridges to C++, or investigating panic- or recursion-driven denial of service, resource/raw-handle ownership, untrusted input, filesystem/process boundaries, or concurrency invariant failures. Covers soundness proofs, MaybeUninit, Drop, Send/Sync, ABI/layout, C strings, allocator ownership, callbacks, FFI unwinding, Rust 2024 unsafe syntax, cancellation, and Miri/sanitizer evidence. Not a general Rust tutori...Votes: 0GitHub stars: 2
- Rust TddUse when implementing Rust features test-first, reproducing Rust bugs with regression tests, characterizing legacy Rust, or applying red-green-refactor with cargo test. Covers boundary and equivalence cases, proptest shrinking, mockall expectations, rstest fixtures, async/concurrent/CLI tests, and coverage interpretation. Not a substitute for system-wide test strategy or benchmarking.Votes: 0GitHub stars: 2
- Rust Type DiagnosticsDiagnoses advanced Rust type-system failures involving coercion sites, generic coercion barriers, function-item types, reference patterns, implied lifetime bounds, variance, Any downcasts, trait upcasting, and drop checking. Applies when ordinary ownership fixes do not explain an expected/found type mismatch or lifetime constraint. Complements rather than replaces everyday Rust, API design, concurrency, performance, and unsafe/FFI skills.Votes: 0GitHub stars: 2
- Rust WasmUse when compiling Rust to WebAssembly, integrating wasm-bindgen or web-sys with browser JavaScript and the DOM, packaging with wasm-pack, choosing wasm32-unknown-unknown versus wasm32-wasip1 or wasm32-wasip2, designing WIT component interfaces, or debugging Wasm loading, capabilities, and target tests.Votes: 0GitHub stars: 2
- Scrape Code Vulnerability CorpusUse when collecting a large, deduplicated corpus of non-academic vulnerability writeups (research blogs, advisories, issue and mailing-list threads, CTF and teaching writeups), each with vulnerable source code and a technical explanation, for one named programming language, into SQLite with CWE mapping, link extraction, source recovery and per-row model provenance. Requires the user to name the target language; without one, nothing starts.Votes: 0GitHub stars: 2
- Search Driven DevelopmentUse when existing code or engineering knowledge could change what gets built: understanding, debugging, extending, or migrating an existing system; finding reusable implementations, libraries, or small mechanisms in mature OSS; comparing or evaluating repositories; or before committing to a new subsystem, dependency, rewrite, or growing workaround. Not for conceptual explanations, syntax, or generic standalone code.Votes: 0GitHub stars: 2
- Typescript Algorithm PatternsUse when solving, implementing, explaining, debugging, or optimizing TypeScript algorithm problems and coding interview solutions involving sequences, searching, trees, graphs, connectivity, dynamic programming, backtracking, greedy choices, tries, heaps, or bit manipulation. Select patterns from valid preconditions, establish invariants, and verify complexity and edge cases.Votes: 0GitHub stars: 2
- Typescript Async ConcurrencyUse when designing, implementing, debugging, or reviewing asynchronous TypeScript workflows: promises, async/await, typed HTTP boundaries, bounded concurrency, queues, retries, cancellation, timeouts, mutexes, debouncing, async iterators, or race conditions where lifecycle, result ordering, failures, and cleanup must be explicit.Votes: 0GitHub stars: 2
- Typescript CollectionsUse when choosing, implementing, or reviewing TypeScript collections and JavaScript runtime APIs: arrays, maps, sets, queues, heaps, linked structures, generators, text and binary processing, JSON, cloning, dates, or numeric data where ordering, equality, mutation, memory, or runtime compatibility matters.Votes: 0GitHub stars: 2
- Typescript Design PatternsUse when choosing, implementing, or reviewing TypeScript design patterns for creation, composition, communication, and state: factories, builders, cloning, shared-resource lifetime, adapters, facades, wrappers, composites, proxies, flyweights, strategies, state machines, observers, mediators, commands, undo/redo, middleware, iterators, template methods, or visitors. Compare candidates with plain functions, objects, modules, or discriminated unions and preserve behavior and lifecycle contracts.Votes: 0GitHub stars: 2
- Typescript Interview ReviewUse when explaining TypeScript interview traps, predicting compile-time and runtime behavior, diagnosing small language examples, or coaching technical interviews about type versus interface, any/unknown/never, narrowing, equality, nullish operators, generics, enums, this binding, satisfies, infer, readonly, augmentation, variance, or overloads. Route production implementation and algorithm solving to the relevant specialist skill.Votes: 0GitHub stars: 2
- Typescript Language RuntimeUse when implementing or debugging TypeScript language features, typed JavaScript migrations, nullish handling, functions and classes, imports and module boundaries, runtime input validation, or compatibility with Node type stripping and other execution paths. Keep static contracts and JavaScript behavior aligned; use typescript-type-modeling for advanced generic or type-level API design.Votes: 0GitHub stars: 2
- Typescript Maintainable DesignUse when reviewing or refactoring TypeScript modules and services for excessive coupling, invalid inheritance, broad interfaces, dependency injection, unsafe assertions, mutable shared state, swallowed errors, circular imports, or maintainability and anti-pattern concerns. Apply SOLID through explicit behavior contracts and focused dependencies; tie performance changes to measured workloads and route detailed algorithm, async, and type- system work to specialist skills.Votes: 0GitHub stars: 2
- Typescript Tooling TddUse when configuring, diagnosing, or validating TypeScript development workflows: tsconfig or module-resolution failures, missing or slow type checks, editor/CLI disagreement, package exports or declaration compatibility, Vitest/Jest/Node test setup, regression tests, red-green-refactor changes, flaky async tests, property-based testing, coverage, linting, debugging, CI, or testability refactors. Preserve the existing package manager and toolchain unless a migration is requested.Votes: 0GitHub stars: 2
- Typescript Type ModelingUse when designing or repairing TypeScript domain models, public API types, narrowing, generic relationships, mapped and conditional types, utility types, or inference; representing valid states, deriving types from values, fixing assignability errors, or checking positive and negative compile examples. Use typescript-language-runtime for runtime parsing and execution compatibility.Votes: 0GitHub stars: 2
- Ui TasteGive your coding agent better UI taste. Build and polish web and iOS interfaces with Uizze's anti-ui-slop playbooks and optional real-product references. Use for UI design, implementation, redesign, critique, or a final visual review in Claude Code, Codex, Cursor, or Copilot.Votes: 0GitHub stars: 2
- Improve Codebase ArchitectureEvidence-backed, recursively decomposed architecture review. Identify justified deep-module opportunities, report in the terminal, and discuss selected designs collaboratively.Votes: 0GitHub stars: 2
- Reuse First Swe ResearchResearch how to implement a new or existing software engineering project with maximum verified reuse and minimum reinvention. Classify the project's change constraints, research and audit adaptive domain-specific decompositions, discover internal and external reusable implementations, verify source code and compatibility, evaluate reuse modes, and recommend a maintainable implementation or migration blueprint. Use for repository-first solution research, platform/library selection, feature ext...Votes: 0GitHub stars: 2