adelabdelgawad
- 33 skills
- 0 followers
- 15 hours ago last updated
- ▌
- ▌
- ▌
- ▌
- ▌ Nextjs Data Table Page · adelabdelgawad bundleCreate Next.js data table pages with SSR initial load, SWR caching, and server-response-based UI updates. Use when asked to create a new data table page, entity management page, CRUD table, or admin list view. Generates page.tsx (SSR), table components, columns, context, actions, and API routes following a proven architecture with centralized reusable data-table component.
- ▌ Debug · adelabdelgawadUse when encountering any bug, error, or unexpected behavior in a fullstack project — enforces root-cause-first debugging discipline before any fix attempts
- ▌ Celery · adelabdelgawad bundleProduction-ready Celery worker configuration for distributed background task processing — task queues, routing, retry strategies, and worker performance tuning. Use when configuring Celery workers, creating background or async tasks, or debugging Celery issues. Do not use for cron-style scheduled jobs (use tasks-management for APScheduler scheduling).
- ▌ Docker · adelabdelgawad bundleProduction-ready Docker infrastructure for fullstack apps — multi-service Docker Compose, nginx reverse proxy, SSL termination, and service wiring for FastAPI + Next.js stacks. Use when setting up Docker infrastructure, adding containers or services, or configuring nginx, monitoring, or SSL. Do not use for application code changes inside the containers.
- ▌ Nextjs · adelabdelgawad bundleGenerate production-ready Next.js pages with SSR initial load, client-side data management, and server-response-based updates. Use when creating Next.js pages, admin or settings pages, or adding CRUD functionality to the frontend. Do not use for backend FastAPI code (use fastapi); for full entity data-table pages prefer data-table.
- ▌ Fastapi · adelabdelgawad bundleGenerate production-ready FastAPI CRUD modules — SQLAlchemy model, Pydantic schemas, CRUD helpers, and routers following the simplified architecture. Use when creating or extending backend entities, models, or REST endpoints with SQLAlchemy and Pydantic. Do not use for Next.js frontend code (use nextjs or data-table).
- ▌ Rust Sqlx · adelabdelgawadSQLx + PostgreSQL patterns for Rust services — compile-time-verified query macros, Executor-generic repository functions, FromRow type mapping, pool configuration, migration discipline, offline cache for CI, and SQLSTATE error mapping. Use when writing Rust database code, repositories, migrations, or queries. Do not use for SQLAlchemy/Python data access (use fastapi or python-clean-architecture).
- ▌ Data Table · adelabdelgawad bundleCreate Next.js data table pages with SSR initial load, simplified state management, and server-response-based UI updates. Use when asked to create a new data table page, entity management page, CRUD table, or admin list view. Generates page.tsx (SSR), table components, columns, context, actions, and API routes following a proven architecture with centralized reusable data-table component. Do not use for non-table pages (use nextjs) or backend code (use fastapi).
- ▌ Fetch Plan · adelabdelgawadPlan fetch layers for a new entity — determines which server actions, API routes, and client calls to create before implementation.
- ▌ Constitution · adelabdelgawadCreate and maintain a per-project constitution — the versioned, normative principles file that codebase-scanning loads and all gates check against (layer rules, language lanes, wire contract, quality limits). Use when asked to create, update, or check a project constitution, bootstrap project principles, or when a governed project has no constitution yet. Do not use for the plugin's own global rules (those live in the skills).
- ▌ Fusion Panel · adelabdelgawadPanel reasoning for high-stakes decisions — take several INDEPENDENT passes at the same question (blind to each other), then synthesize consensus, contradictions, unique insights, and blind spots into one grounded answer. Inspired by fusion-fable's "independence, then synthesis". Zero setup — uses parallel Claude subagents, no external CLIs and no slash command. Use for architecture choices, risky migrations, security-sensitive changes, stubborn bugs, and ambiguous trade-offs where being wrong is costly.
- ▌ Rust Testing · adelabdelgawadTesting strategy for Rust clean-architecture services — domain unit tests, use-case tests with hand-rolled fakes, repository integration tests with
- ▌ Prompt Polish · adelabdelgawadRefine a raw user instruction into a precise, well-structured prompt before acting on it or delegating it to worker subagents. Applies Claude prompt-engineering best practices (clear intent, explicit scope, success criteria, format, context). Runs on every request via the prompt-polish UserPromptSubmit hook; this skill carries the method. Use whenever a request is about to drive code generation, review, debugging, or multi-agent work.
- ▌ Rust Axum API · adelabdelgawadAxum 0.8 API patterns — curly-brace path syntax, extractor ordering, State via FromRef, IntoResponse error mapping, Tower middleware ordering, JWT auth middleware, WebSocket, and graceful shutdown. Use when writing or reviewing Axum handlers, routers, middleware, or HTTP-layer code in a Rust service. Do not use for FastAPI/Python endpoints (use fastapi or python-clean-architecture) or for business logic (handlers delegate to use cases — see rust-clean-architecture).
- ▌ Fetch Validate · adelabdelgawadAudit fetch pattern compliance — checks server actions use /backend/ URLs, API routes use backendFetch with (token, headers), client uses api not fetchClient, and CSRF flows correctly.
- ▌ Fetch Implement · adelabdelgawadScaffold fetch boilerplate for a new entity — generates server actions, API routes, and client call patterns following the correct architecture.
- ▌ Senior Engineer · adelabdelgawadSenior-engineer discipline for architecture, modularity, and duplication prevention — search-before-implement, composition over monoliths, SOLID boundaries, aggressive complexity reduction, and leave-it-cleaner refactoring. Use before writing, modifying, or refactoring ANY application code, and when asked to refactor, clean up, reduce duplication, or extract shared logic. Do not use for docs-only, config-only, or dependency-bump changes.
- ▌ Rust Correctness · adelabdelgawadRust language correctness reference — ownership and borrowing, lifetimes, async concurrency hazards, smart pointer selection, panic-vs-Result philosophy, and exhaustive pattern matching, with detectors for the forbidden patterns behind common compiler errors (E0382, E0499, E0502, E0597) and async bugs. Use when writing any non-trivial Rust, fixing borrow-checker or Send/Sync errors, or reviewing Rust for correctness. Do not use for Python.
- ▌ Tasks Management · adelabdelgawad bundleBackground task management combining APScheduler scheduling with Celery execution — scheduled jobs, cron-style periodic tasks, job management endpoints, execution tracking, and distributed locking. Use when creating scheduled or periodic jobs. Do not use for plain fire-and-forget background tasks (use celery).
- ▌ Codebase Scanning · adelabdelgawadDynamically detect project patterns and coding style before code generation. MANDATORY before first generation in any session.
- ▌ Fetch Architecture · adelabdelgawad bundleClient and server-side fetch utilities for Next.js — direct backend calls from server code and API route proxying with auth refresh for client code. Use when setting up fetch utilities, configuring client-side API calls, or implementing server-side data fetching. Do not use to scaffold per-entity fetch code (use fetch-plan then fetch-implement).
- ▌ Rust Quality Gates · adelabdelgawadNon-skippable verification chain for Rust services — fmt, clippy with deny-warnings, cargo check, sqlx offline-cache drift, audit, migration safety, and the no-allow policy. Use after generating or modifying Rust code, before declaring any Rust work done, or when asked to gate or validate a Rust project. Do not use for Python validation (ruff/mypy are wired separately).
- ▌ Rust Nextjs Contract · adelabdelgawadWire-contract parity for Rust APIs serving the shared Next.js frontend — camelCase JSON matching CamelModel output, limit/skip pagination, search and is_active filters, list envelopes with total, Bearer auth, and route prefixes, so Rust and FastAPI services are interchangeable behind the same frontend. Use when exposing ANY Rust endpoint that Next.js (or the existing fetch-architecture) will consume. Do not use for service-to-service-only APIs with their own contract.
- ▌ Batch Error Resolution · adelabdelgawadResolve multiple build, compile, test, lint, or type-check errors as one batch operation — fix all errors first, then verify once. Use when a build, test suite, linter, or type checker reports several failures at the same time. Do not use for a single isolated error that can be fixed and verified immediately.
- ▌ Using Fullstack Agents · adelabdelgawadAuto-triggering guide for fullstack-agents — ensures Claude automatically invokes the right code generation, review, and debugging skills before writing any FastAPI or Next.js code.
- ▌ Frontend Transformation · adelabdelgawadMigrate an existing React (or other framework) frontend to a target framework (e.g. Next.js App Router) at 1:1 fidelity — same pages, routes, layouts, components, styling, state, and interactions, with nothing redesigned or reimplemented. Use when asked to port, migrate, convert, or transform a frontend to another framework while preserving it exactly. Do not use for greenfield pages (use nextjs / data-table) or backend migrations (use backend-migration-from-frontend).
- ▌ Rust Clean Architecture · adelabdelgawadClean Architecture + DDD for Rust API microservices — Cargo workspace with domain/application/infrastructure/shared crates, ports and adapters, use-case-owned transactions, parse-don't-validate value objects, four-stage error model, and composition root. Use when creating or structuring a Rust service, deciding where Rust code belongs, or generating Rust entities end-to-end. Do not use for Python services (use python-clean-architecture) or frontend code. No Leptos — Rust serves JSON APIs only.
- ▌ Python Clean Architecture · adelabdelgawadClean Architecture + DDD for Python (FastAPI) microservices — pure domain layer with value objects and entities, application use cases owning transactions, repository ports as Protocols, SQLAlchemy adapters in infrastructure, and a four-stage error model. Use when creating or structuring a NEW Python microservice or applying DDD to Python. Do not use for the existing simplified FastAPI pattern (use fastapi — codebase-scanning decides which applies) and never for Rust services (use rust-clean-architecture).
- ▌ Backend Migration From Frontend · adelabdelgawadMigrate a backend to a new framework by reverse-engineering behavior from the frontend — trace every UI request down through router, controller, middleware, service, repository, DB, jobs, events, and side effects, then reproduce equivalent behavior (validation, permissions, transactions, responses, status codes, logging, caching, events) in the target. Use when porting/rewriting a backend and behavioral equivalence with the existing app matters. Do not use for greenfield backends (use fastapi / python-clean-architecture / rust-clean-architecture) or pure frontend migrations (use frontend-transformation).