Results for “layers”

Expert patterns for adding multiplayer to single-player games including client-server architecture, authoritative server design, MultiplayerSynchronizer, lag compensation (client prediction, server reconciliation), input buffering, and anti-cheat measures. Use when retrofitting multiplayer, porting to online play, or designing networked gameplay. Trigger keywords: MultiplayerPeer, ENetMultiplayerPeer, SceneMultiplayer, MultiplayerSynchronizer, rpc, rpc_id, multiplayer_authority, client_prediction, server_reconciliation, lag_compensation, rollback.

The English summary is being prepared. Showing the original description.

Expert patterns for adding multiplayer to single-player games including client-server architecture, authoritative server design, MultiplayerSynchronizer, lag compensation (client prediction, server reconciliation), input buffering, and anti-cheat measures. Use when retrofitting multiplayer, porting to online play, or designing networked gameplay. Trigger keywords: MultiplayerPeer, ENetMultiplayerPeer, SceneMultiplayer, MultiplayerSynchronizer, rpc, rpc_id, multiplayer_authority, client_prediction, server_reconciliation, lag_compensation, rollback.

The English summary is being prepared. Showing the original description.

Structure Next.js projects with Feature-Sliced Design layers, domain-grouped slices, and strict import hierarchy. Use when organizing features into FSD layers, enforcing slice boundaries, or keeping page.tsx thin.

The English summary is being prepared. Showing the original description.

Enforce inward dependency flow, pure domain layers, and DTO-to-entity mapping in Flutter DDD architecture. Use when structuring layers or boundaries; defer navigation-only routing and feature implementation such as notifications.

The English summary is being prepared. Showing the original description.

Progressive memory recall with 4 scope layers AND 3 depth layers. Scope: identity > project > room > deep. Depth: IDs only > summary > full. 10-50x token savings through fetch-on-confirmation pattern.

The English summary is being prepared. Showing the original description.

Implements media and file management components including file upload (drag-drop, multi-file, resumable), image galleries (lightbox, carousel, masonry), video players (custom controls, captions, adaptive streaming), audio players (waveform, playlists), document viewers (PDF, Office), and optimization strategies (compression, responsive images, lazy loading, CDN). Use when handling files, displaying media, or building rich content experiences.

The English summary is being prepared. Showing the original description.

Provides AWS CloudFormation patterns for Lambda functions, layers, API Gateway integration, event sources, cold start optimization, monitoring, logging, template validation, and deployment workflows. Use when creating Lambda functions with CloudFormation, configuring event sources, implementing cold start optimization, managing layers, integrating with API Gateway, and deploying Lambda infrastructure.

The English summary is being prepared. Showing the original description.

Help fantasy players make start/sit, waiver, streaming, trade, draft and keeper decisions using current player news, usage, matchups and their league's scoring. Use for choosing between players, finding pickups, evaluating a deal or filling a roster need, even without an explicit research request. Excludes generic sports scores, betting and changing league rosters.

The English summary is being prepared. Showing the original description.

CesiumJS imagery layers - ImageryProvider, ImageryLayer, ImageryLayerCollection, WMS, WMTS, Bing, OpenStreetMap, ArcGIS, Mapbox, tile discard policies. Use when adding or swapping base map layers, configuring imagery providers, layering multiple map sources, or creating split-screen imagery comparisons.

The English summary is being prepared. Showing the original description.

The craft of weaving story into interactive systems where the player is both audience and author. This skill covers the unique challenges of game narrative: branching structures that respect player agency, environmental storytelling that rewards exploration, dialogue systems that feel alive, and the delicate balance between authored experience and emergent narrative. Unlike linear media, games don't tell stories TO players - they create the conditions for stories to emerge WITH players. The narrative designer's job is to build the scaffolding that supports infinite player-authored moments while maintaining coherent themes and emotional arcs. This skill synthesizes lessons from Disco Elysium's internal monologue as gameplay, Hades' death-as-narrative-engine, interactive fiction's branching mastery (Inkle, Twine), and procedural narrative pioneers like Dwarf Fortress. It addresses ludonarrative harmony, bark systems, cinematics that respect agency, and the "and therefore" test that separates plot from story. Use when "narrative design, game story, game writing, dialogue system, branching narrative, player choice, environmental storytelling, bark system, quest design, lore delivery, ludonarrative, interactive fiction, inkle, twine, dialogue tree, player agency, cinematic design, voice direction, localization, procedural narrative, narrative, game-writing, dialogue, branching, player-agency, environmental-storytelling, quest-design, voice-acting, localization, interactive-fiction, procedural-narrative, ludonarrative" mentioned.

The English summary is being prepared. Showing the original description.

Authors and caches a personalized container environment from a Dockerfile- like spec, as a single layer or as a composition of independently cached layers. Use when the user mentions "container layer", "Containerfile", "custom container", "cache my installs", "composable layers", "uv shim", or wants package installations, skills and environment config to survive an ephemeral session. Also for snapshotting, restoring or rebuilding that environment, and for capturing ad-hoc installs into a reproducible spec.

The English summary is being prepared. Showing the original description.

Help fantasy players make start/sit, waiver, streaming, trade, draft and keeper decisions using current player news, usage, matchups and their league's scoring. Use for choosing between players, finding pickups, evaluating a deal or filling a roster need, even without an explicit research request. Excludes generic sports scores, betting and changing league rosters.

The English summary is being prepared. Showing the original description.

Use when writing, moving or auditing any .md in imp - deciding which file a paragraph belongs in, adding a doc, fixing a stale claim, or when docs_lint.py fails in CI. Covers the four reader layers (L0 README / L1 operators / L2 kernel devs / L3 agents), the HTML-comment metadata header, [PROV:] provenance, the single-source-of-truth map, generated perf blocks, which numbers may appear in prose, plan-doc closure. Triggers on "which doc does this go in", "docs lint failed", "add a doc", "this claim is stale", "update the README", "PROV block", "layer", "STALE.md". Do NOT use for the CHANGELOG or a release body (shipping-prs), or for code-comment accuracy (codebase-audit).

The English summary is being prepared. Showing the original description.

Comprehensive audit of a user's entire Claude environment — combines Project audit (six-dimension Project Scorecard, seven anti-patterns) with Global audit (six-dimension Global Layer Scorecard) plus Cross-Layer Alignment Check across all nine layers and Evolutionary Recommendations across four pathways. Produces a unified action plan. Use when user says "full audit of everything," "audit my entire Claude setup," "full stack audit," "comprehensive review of my project and preferences," "check everything," or wants the complete health check of both a specific Project AND their global configuration. Also use when a project audit reveals cross-layer issues that require full-stack visibility. Do NOT use for auditing only a Project (use rootnode-project-audit if available) or only global layers (use rootnode-global-audit if available). Do NOT use for single prompt evaluation (use rootnode-prompt-validation if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.

The English summary is being prepared. Showing the original description.

Audit over-engineered codebases by factoring layers into live obligations, quotienting redundant distinctions, ablating unearned surface, and normalizing survivors while preserving required behavior. Use when change latency or agent difficulty comes from frameworks, plugins, DI, codegen, task runners, config indirection, ORMs, GraphQL, monorepo/infra tooling, or web stacks, or when asked to remove layers. Produces an evidence-backed Reduction Certificate, cuts, migration phases, proof signals, and rollback. Not for one local readability cleanup (use tw-complexity-mitigator).

The English summary is being prepared. Showing the original description.

Signpost (not a knowledge pack) for maritime safety and class rules: SOLAS Consolidated Edition 2024 (IH110E) as the paywalled statutory core, ISM Code & Guidelines 2018 (ID117E), ISPS Code 2003 (K116E) and the 2021 guide (IB116E), and COLREGS 2026 (IC904E), with designation, edition, owner, status, and official URL only. Contains no source content. Free-path layers are US flag implementation (eCFR Title 46 and USCG circulars), the USCG Navigation Rules PDF, UK MCA notices under Open Government Licence v3.0, and class portals (DNV, ABS, Bureau Veritas). None of those layers is the IMO consolidated text. No in-repo pack covers these instruments.

The English summary is being prepared. Showing the original description.

Loads, reloads, and reshapes the map on a running CARLA server via the Python API — get_available_maps, load_world and reload_world (with or without resetting world settings), generate a world from an OpenDRIVE .xodr, and load/unload map layers. Use when the user asks to "load a map", "change the town", "reload the world", "list available maps", "load an xodr/opendrive map", or "load/unload map layers", and when settings (sync mode, fixed delta) must survive the switch.

The English summary is being prepared. Showing the original description.

Feature-Sliced Design (FSD、フロントエンドアーキテクチャ手法) リファレンスとルール。 別名 fsd / feature-sliced。layers (app / pages / widgets / features / entities / shared)、 依存方向、Public API、@x 記法 (cross-import)、slice groups (スライスグループ)、 segments (ui / model / api / lib / config)、steiger、Next.js、TanStack Query 連携。 コードレビュー・リファクタリング時に自動参照。

The English summary is being prepared. Showing the original description.

Build or review Java services with Quarkus 3.x using patterns for REST APIs, database access with Panache, and messaging with Apache Camel. Examples cover layered code structure, validation, transactions, and asynchronous processing, where work completes separately from the main flow.

• Designing a REST API with separate service and repository layers
• Connecting services through Camel and RabbitMQ
• Reviewing Panache database access and transactions

Build React Native and Expo screens with guidance on navigation, state management, and data fetching. Apply patterns for long lists, validated forms, device features, and secure token storage when developing or reviewing mobile apps.

• Building screens and navigation in Expo
• Separating remote data from interface state
• Improving long-list rendering

Save, organize, synchronize, and retrieve documents, conversations, and project information across local files, memory tools, knowledge repositories, and databases. Check for duplicates before storing information and choose a suitable home for each type of knowledge.

• Saving documents and conversations to a knowledge base
• Consolidating duplicate notes
• Synchronizing knowledge across storage systems

Build or review FastAPI applications using examples for project structure, input validation, authentication, permission checks, and asynchronous processing. Organize database updates in a separate business logic layer and test API behavior with httpx and pytest.

• Structuring a new FastAPI application
• Defining and validating request and response data
• Reviewing authentication and permission checks

Investigate unreliable AI agents across 12 layers, including instructions, memory, tool execution, and display. Use code and logs to trace failures, rank findings by severity, and produce an ordered repair plan that prioritizes code changes.

• Investigating failures that appear only inside an agent application
• Tracing old conversation content leaking into new sessions
• Checking skipped or falsely claimed tool execution

Set up a modded Minecraft server from a server pack, including Java and Forge or NeoForge configuration. Adjust memory and viewing distances for the expected players, schedule world backups, and verify startup and connectivity.

• Set up a server from a modpack server ZIP
• Configure difficulty, PvP, and player access
• Tune memory and viewing distances