Web & Frontend

praxstack Bundle

Coordinate a cross-functional star-team workflow (Product Manager, Principal Engineer, Backend, Frontend, QA/Security, DevOps) with mandatory architecture and code-review checkpoints. Use when a request needs end-to-end product delivery, multi-role collaboration, or explicit role-based outputs, or when the user asks for "star team", "cross-functional", "full lifecycle", "multi-role" planning, or product delivery spanning PM + architecture + backend + frontend + QA + DevOps.

ziadnagar Bundle

Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.

ziadnagar Bundle

Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "C4 diagram", "system context", "container diagram", "component diagram", "deployment diagram", "document architecture", "visualize architecture".

ziadnagar Bundle

Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with render_game_to_text.

ziadnagar Skill

Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when: 3D website, three.js, WebGL, react three fiber, 3D experience.

ziadnagar Bundle

Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visualisation that requires fine-grained control over visual elements, transitions, or interactions. Use this for bespoke visualisations beyond standard charting libraries, whether in React, Vue, Svelte, vanilla JavaScript, or any other environment.

ziadnagar Skill

Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.

ziadnagar Skill

Create premium, Awwwards-quality website designs as React (.jsx) components that look like they were built by a top-tier agency charging $50k+ per project. Use this skill whenever the user asks for a website, landing page, portfolio, or web component that should look expensive, premium, luxury, editorial, high-end, or agency-quality. Also trigger when the user mentions Awwwards, FWA, award-winning design, or references brands like Apple, Aesop, Bottega Veneta, Stripe, or any luxury/fashion/design-forward brand. Trigger when the user says things like "make it look professional", "make it look expensive", "I want it to look really good", "high quality design", "not generic", or expresses dissatisfaction with typical AI-generated website aesthetics. Do NOT trigger for dashboards, admin panels, internal tools, or functional UI where aesthetics are secondary to utility — the standard frontend-design skill handles those.

ziadnagar Skill

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

ziadnagar Bundle

Best practices for Remotion - Video creation in React

userinner Bundle

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

userinner Bundle

Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies.

userinner Bundle

Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.

userinner Bundle

Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.

userinner Bundle

Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.

userinner Bundle

Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.

kora-projects Skill

Build and maintain Java/Kotlin services on the Kora Framework 1.x (ru.tinkoff.kora) — compile-time DI, zero reflection, annotation processors (Java) or KSP (Kotlin). Routes to 39 domain sub-skills. Use when the request mentions Kora, or uses Kora APIs: @KoraApp, @Component, @Module, @KoraSubmodule, @Root, @Tag, @HttpController, @HttpRoute, @HttpClient, @Repository, @Query, @EntityJdbc, @KafkaListener, @KafkaPublisher, gRPC, SOAP/WSDL, @S3.Client, MapStruct, @Json, @ConfigSource (HOCON/YAML), OpenAPI codegen, @KoraAppTest, Testcontainers, @Valid, @Validate, @Log, @Mdc, @Retry, @CircuitBreaker, @Timeout, @Fallback, @Schedule*, @Cacheable, @CachePut, @CacheInvalidate, Micrometer/Prometheus metrics, OpenTelemetry/OTLP tracing, Undertow, Hikari. Also use for Kora project setup, Gradle/BOM dependencies, DI graph errors, or explaining Kora concepts. Do not use for Spring Boot, Micronaut, or Quarkus work.

kora-projects Skill

Build and maintain Java/Kotlin services on the Kora Framework 2.0 (io.koraframework) — compile-time DI, zero reflection, synchronous contracts on virtual threads, annotation processors (Java) or KSP (Kotlin). Routes to 39 domain sub-skills. Use when the request mentions Kora, or uses Kora APIs: @KoraApp, @Component, @Module, @KoraSubmodule, @Root, @Tag, @Conditional, @FactoryModule, @HttpController, @HttpRoute, @HttpClient, @Repository, @Query, @EntityJdbc, @KafkaListener, @KafkaPublisher, gRPC, SOAP/WSDL, @S3.Client, @S3.Head, MapStruct, Konvert, @Json, @ConfigSource, @ConfigMapper (HOCON/YAML), OpenAPI codegen, @KoraAppTest, Testcontainers, @Valid, @Validate, @Log, @Mdc, @Retryable, @CircuitBreakable, @Timeout, @RateLimited, @Fallback, @Schedule*, @Cacheable, @CachePut, @CacheInvalidate, @CacheInvalidateAll, Micrometer/Prometheus metrics, OpenTelemetry/OTLP tracing, Undertow, Hikari. Also use for Kora project setup, Gradle/BOM dependencies, DI graph errors, or explaining Kora concepts. Do not use for Spring

kora-projects Bundle

DTO ↔ entity mapping in Kora 2.0. Java: org.mapstruct @Mapper + the MapStruct javac processor. Kotlin: Konvert @Konverter + its KSP processor — kapt is not the 2.0 path. The matching extension ships inside annotation-processors / symbol-processors, finds the generated *Impl and binds it into the graph with no @Component. Use for @Mapper, @Konverter, @Mapping, mapstruct-processor wiring, and the removed mapstruct-extension coordinate.

kora-projects Bundle

Compile-time DI in Kora 2.0 — @KoraApp, @Component, @Module, @KoraSubmodule, @FactoryModule, @Conditional, @DefaultComponent, @Root, @Tag from io.koraframework.common.annotation. Generates <App>Graph; entry point KoraApplication.run(ApplicationGraph::graph). Use when wiring the application graph, splitting a build into Gradle submodules, or fixing "No component found for dependency" / "Multiple components match dependency" / "Circular dependency found". For graph runtime behaviour see kora-di-runtime.

kora-projects Bundle

Runtime DI behaviour of the Kora 2.0 container (io.koraframework.application.graph) — @Root pruning, the synchronous Lifecycle init()/release() contract, LifecycleWrapper/Wrapped<T>, @Tag disambiguation incl. Tag.Any and Tag.Factory, All<T> collections, ValueOf<T>/PromiseOf<T>, @Nullable optional dependencies, GraphInterceptor afterInit/beforeRelease, GraphCondition + @Conditional, RefreshableGraph.refresh and RefreshListener. Use when a component must start although nothing depends on it, when writing init/release logic, when disambiguating or collecting components, when breaking a refresh chain or a dependency cycle, or when a component must be wrapped during graph build. For compile-time @KoraApp/@Module/@Component wiring see kora-di-compile.

kora-projects Bundle

Kora 2.0 gRPC server — io.koraframework:grpc-server, GrpcServerModule, untagged @Component handlers extending the generated *Grpc.*ImplBase (io.grpc.BindableService), untagged io.grpc.ServerInterceptor components, the grpcServer config section (port, reflectionEnabled, maxMessageSize, telemetry), OkHttp transport on virtual threads, gRPC Server Reflection. Use when serving unary or streaming RPCs from a Kora service, pinning io.grpc/protobuf versions against grpc-java 1.83.1, or debugging AbstractMethodError buildClientTransportServers, an interceptor that never runs, or handlers that are not registered.

kora-projects Bundle

Declarative Kora 2.x HTTP clients — io.koraframework @HttpClient("httpClient.x") interfaces with @HttpRoute, @Path/@Query/@Header/@Cookie, @Json bodies, HttpResponseEntity, @Mapping, @ResponseCodeMapper, HttpClientInterceptor + @InterceptWith, and the OkHttp / JDK / Apache transports (http-client-ok, http-client-jdk, http-client-apache). Client contracts are synchronous on virtual threads — no CompletionStage, Mono or Kotlin suspend, and http-client-async no longer exists. Use for typed outbound calls, per-client httpClient.* config and timeouts, HttpClientResponseException handling, or "No component found for dependency: HttpClientResponseMapper<...>" graph errors. For OpenAPI-generated clients see kora-openapi-generator-client; for the inbound @HttpController server see kora-http-server.

kora-projects Bundle

Kafka consumers in Kora 2.0 — @KafkaListener (io.koraframework.kafka.common.annotation) on a @Component method, wired by KafkaModule from io.koraframework:kafka. Covers the accepted handler signatures, subscribe vs assign containers, who commits the offset, @Json / @Tag deserializers, KafkaSkipRecordException and RecordKey/ValueDeserializationException, ConsumerAwareRebalanceListener, kafka.consumer.* config, and consumer telemetry. Use when consuming Kafka messages, porting a 1.x @KafkaListener, or debugging "Kafka listener method has unsupported parameter".

kora-projects Bundle

SLF4J + Logback logging for Kora 2.0 — LogbackModule from io.koraframework:logging-logback, KoraAsyncAppender, ConsoleTextRecordEncoder, config-driven logging.levels, StructuredArgument, the ScopedValue-based Kora MDC, and @Mask masking. Use when wiring logback.xml, setting per-logger levels from application.conf/yaml, turning on per-component telemetry.logging.enabled, or porting a Kora 1.x logging setup.

kora-projects Bundle

Kora 2.0 Micrometer metrics — io.koraframework:micrometer-module, MetricsModule (io.koraframework.micrometer.module), PrometheusMeterRegistry + injectable MeterRegistry, PrometheusMeterRegistryInitializer, MetricsScraper, and the /metrics endpoint served by the SYSTEM HTTP server under httpServer.system.metricsPath. Covers the per-component telemetry.metrics { enabled, slo, tags } keys — where enabled defaults to FALSE in 2.0 — the second MeterRegistry gate, the real 2.0 metric names (http.server.request.duration, db.client.operation.duration, cache.operation.duration, messaging.process.duration…), custom Counter/Gauge/Timer/DistributionSummary, and tag cardinality. Use when adding business metrics, wiring Prometheus scraping, or debugging an empty or JVM-only /metrics response.

kora-projects Bundle

In-process scheduled jobs in Kora 2.x — @ScheduleAtFixedRate, @ScheduleWithFixedDelay, @ScheduleOnce and the new @ScheduleWithCron from io.koraframework.scheduling.jdk.annotation, contributed by SchedulingJdkModule (artifact io.koraframework:scheduling-jdk) on top of a ScheduledThreadPoolExecutor of platform threads. Covers the config attribute for externalising timings, the scheduling.jdk.shutdownWait and scheduling.telemetry keys, per-job telemetry overrides, and why a scheduled method must be a no-argument, non-suspend member of a @Component. Use for heartbeat, cleanup, cache-warm and in-process cron jobs. For persistent, clustered or Quartz-flavoured cron jobs use kora-aop-scheduling-quartz.

kora-projects Bundle

In-process JUnit 5 tests for Java Kora 2.0 services — io.koraframework:test-junit5 with @KoraAppTest, @TestComponent, KoraAppTestConfigModifier/KoraConfigModification, KoraAppTestGraphModifier/KoraGraphModification, KoraAppGraph, Mockito @Mock/@Spy plus @MockitoStrictness, the @KoraApp TestApplication submodule pattern behind -Akora.app.submodule.enabled=true, and Testcontainers for PostgreSQL/Kafka. Needs testAnnotationProcessor "io.koraframework:annotation-processors". Contracts are synchronous, so reactive/CompletionStage test shapes are gone, and HOCON embedded in KoraConfigModification.ofString must use 2.0 keys (jdbc, httpServer.port). Use when writing a Kora 2.0 Java test, mocking a component inside the graph, overriding test config, or starting a real database/broker. For Kotlin see kora-testing-junit-kotlin; for the packaged image see kora-testing-blackbox.

kora-projects Bundle

In-process JUnit 5 tests for Kotlin Kora 2.x services — io.koraframework:test-junit5, @KoraAppTest/@TestComponent from io.koraframework.test.extension.junit5, MockK @field:MockK/@SpyK, Mockito-Kotlin, KoraAppTestConfigModifier/KoraConfigModification.ofString, KoraAppTestGraphModifier/KoraGraphModification, the TestApplication submodule pattern with kspTest + kora.app.submodule.enabled, and Testcontainers. Use when writing or migrating a Kotlin @KoraAppTest, mocking a graph component, overriding test config, or wiring PostgreSQL/Kafka containers. Kora 2.0 contracts are synchronous — no runTest/coEvery around Kora calls. For Java see kora-testing-junit-java; for E2E over the packaged artifact see kora-testing-blackbox.

kora-projects Bundle

Generate a Kora 2.x HTTP server from an OpenAPI 3.x contract with the `kora` generator (io.koraframework:openapi-generator, modes java-server / kotlin-server). Emits *ApiController (@Component + @HttpController), a *ApiDelegate interface you implement, sealed *ApiResponses with one record per status code, *ApiServerResponseMappers, model records/data classes and an ApiSecurity @Module for securitySchemes. Use for contract-first servers, enableServerValidation, HttpServerPrincipalExtractor wiring, enum fromValue parsing, or "delegate not found" / phantom-package build errors.

blockmatic Bundle

Framework (OSS). Set up Tailwind CSS v4 in Expo SDK 57 with react-native-css and NativeWind v5 for universal styling (upstream v55 naming)

me2resh Skill

WCAG 2.1 AA audit — perceivable, operable, understandable, robust criteria. Deep-dive for /launch-check accessibility.

synkraai Skill

Activate Aria (architect) for Architect. Use for system architecture (fullstack, backend, frontend, infrastructure), technology stack selection (technical evaluation), API design (REST/GraphQL/tRPC/WebSocket), security architecture, perf...

synkraai Skill

Activate Orion (aiox-master) for AIOX Master Orchestrator & Framework Developer. Use when you need comprehensive expertise across all domains, framework component creation/modification, workflow orchestration, or running tasks that don't...

promovaweb Bundle

Preparar, monitorar ou reconciliar o contexto persistente de um projeto Specsfy. Use ao iniciar o framework, antes e depois de mudanças na aplicação, ao verificar consistência documental, quando PROJECT.md ou os arquivos .specsfy/STACK.md, .specsfy/RULES.md e .specsfy/DATABASE.md estiverem ausentes, ou quando for necessário sugerir modelos coerentes com Laravel, Next.js, Astro ou um stack genérico. Pode ser executada repetidamente e deve preservar todo conteúdo já existente.

promovaweb Bundle

Projetar, implementar e revisar interfaces React com composição, estado, efeitos, concorrência, acessibilidade, performance e testes. Use quando a tarefa envolve componentes React, hooks, context, forms ou renderização cliente; use a skill Next.js quando o framework definir fronteiras server/client.