Menu
Skills in this repository
SkillsMP has collected 180 skills from peterbamuhigire/chwezi-dev-engine. Open a skill to review its source and details.
peterbamuhigire/chwezi-dev-engineShowing 40 of 180 collected skills.
Use when producing, automating, or reviewing Blender source assets, characters, rigs, animations, props, vehicles, collisions, LODs, FBX/glTF exports, or Blender-to-engine validation; use game-3d-asset-pipeline for DCC-neutral art direction and budgets.
Use when delivering a game on iOS, iPadOS, or macOS with Apple-native services, Metal diagnostics, controllers, haptics, cloud saves, signing, notarisation, sandboxing, or Mac window and display behaviour.
Use when producing, importing, validating, or optimising 2D game concepts, sprites, atlases, tile sets, skeletal or frame animation, UI art, particles, VFX, resolution variants, or licensed source assets.
Use when directing or producing game-ready 3D environments, characters, props, materials, rigs, animations, LODs, collisions, lighting assets, or DCC-to-engine imports; mobile budgets must come from target-device measurement.
Use when creating reproducible Unity, Godot, Unreal, Android, iOS, or macOS game build pipelines, manifests, symbols, signing boundaries, artifact promotion, patching, certification, or rollback rehearsals.
Use when threat-modelling a game client/server, validating actions, protecting game economy and accounts, detecting tampering or cheats, limiting bots and abuse, investigating incidents, or designing proportionate enforcement and appeals.
Use when designing and producing game levels, worlds, encounters, missions, narrative content, procedural generation, streaming partitions, content schemas, validation, pacing, or multidisciplinary content handoffs.
Use when designing or implementing authoritative multiplayer topology, replication, RPCs, prediction, reconciliation, matchmaking, sessions, reconnect, game backend persistence, regional hosting, protocol evolution, or network tests.
Use when building or restructuring an Unreal Engine game with C++, Blueprints, Gameplay Framework classes, replication, assets, packaging, automation, or Unreal-specific profiling and release evidence.
Use when designing, recording, licensing, editing, integrating, mixing, localising, profiling, or testing game music, ambience, dialogue, UI, Foley, spatial audio, and adaptive audio systems.
Use when a game system needs explicit vector, matrix, quaternion, geometry, interpolation, collision, camera, steering, probability, or numerical-simulation rules; use gameplay-systems-architecture for ownership and the engine skill for API integration.
Use when building, migrating, profiling, testing, or exporting a Godot mobile game for Android or iOS; covers scenes, nodes, resources, signals, GDScript/C#, saves, plugins, rendering, and export pipelines.
Use when establishing or enforcing mobile-game frame-time, memory, loading, storage, network, battery, thermal, rendering, physics, AI, audio, and asset budgets through physical-device profiling; not for speculative optimisation.
Use when preparing or operating Android/iOS game signing, packaging, store submission, privacy, ratings, analytics, crash reporting, IAP, staged rollout, rollback, support, patches, downloadable content, events, or ethical live operations.
Use when designing or diagnosing a game's render pipeline, shaders, materials, lighting, shadows, visibility, post-processing, GPU resources, frame graph, graphics API, or visual-performance trade-offs; use game-3d-asset-pipeline for content and…
Use when the task matches skill: new project scaffold and this skill's local workflow.
Use when pricing, billing, refunding, recognizing revenue, or packaging commercial terms for agentic AI services and outcomes.
Use when mapping AI agent operations to SOC 2, ISO 27001, HIPAA, audit logs, control testing, attestations, and compliance evidence.
Use when defining agent budgets, step limits, reversibility, blast-radius controls, kill switches, and governance policy for agentic AI systems.
Use when measuring, evaluating, replaying, evidencing, or tracking success for AI agent tasks, steps, traces, and outcomes.
Use when defining agent SLAs, customer commitments, SLA dashboards, credits, support promises, and service evidence for agentic AI products.
Use when designing agent tool catalogs, tool schemas, action gating, human approval, and human-in-the-loop control for agentic AI systems.
Use when designing AI analytics, dashboards, SaaS AI metrics, NLP analytics, predictive analytics, or executive AI insight workflows. Orchestrates the former granular AI analytics skills as references.
Use when designing or building AI-powered application systems — choosing architecture style, selecting components, structuring the AI stack, making build-vs-buy decisions, and planning multi-tenant AI module gating
Use when modeling, metering, attributing, billing, or controlling AI usage costs across tenants, plans, features, providers, and agent workloads.
Use when preventing, detecting, triaging, communicating, recovering from, or reviewing AI incidents, AI errors, RCA, and postmortems.
Use when integrating an LLM provider into an application with streaming, structured outputs, tool calls, embeddings, multi-model routing, retries, caching, and usage metering.
Use when writing, refining, or structuring prompts for AI-powered app features — system prompts, user prompt templates, few-shot examples, chain-of-thought, prompt versioning, and defensive prompting
Use when building features that answer questions from private data, documents, policies, or time-sensitive information — RAG architecture, chunking strategies, hybrid search, re-ranking, vector databases, evaluation, agentic RAG, multimodal RAG...
Use when securing an AI/LLM-powered feature against prompt injection, cross-tenant data leakage and tenant isolation failures, jailbreaks, and adversarial inputs. Covers PII scrubbing before model calls, output validation, rate limiting, audit logging, and…
Use when designing Android local storage, Room migrations, DataStore preferences, or offline API synchronisation; use android-development for broader application structure.
Use when developing Android behaviour test-first across Kotlin, Room, repositories, ViewModels, and Compose; use android-development for architecture not centred on a test workflow.
Use when designing HTTP APIs with OpenAPI, versioning, authentication, rate limits, idempotency, error contracts, and observability requirements.
Use when scoping or specifying an e-commerce platform, payment, API, security, AI, data protection, integration, and remediation audit for SMEs or cross-border digital trade programmes.
Use when designing or operating GraphQL APIs with schemas, resolvers, authorization, pagination, federation, code generation, and hostile-input controls.
Use when designing or reviewing relational or document-backed data architecture for SaaS platforms, ERP systems, APIs, analytics stores, or mobile sync. Covers domain modeling, tenancy, indexing, migrations, integrity, retention, and performance tradeoffs.
Use when designing, implementing, or reviewing MySQL application schemas, SQL, indexes, constraints, stored routines, and production query patterns. Load absorbed MySQL best-practice, data-modeling, and advanced-SQL reference files as needed.
Use when administering, tuning, backing up, restoring, monitoring, or troubleshooting MySQL production systems. Load absorbed MySQL administration and query-performance reference files for operational runbooks, indexes, replication, and incident response.
Use when designing, implementing, or reviewing PostgreSQL application data models, SQL, indexes, constraints, extensions, server-side routines, and production query patterns. Load the absorbed PostgreSQL reference files for fundamentals, advanced SQL, schema…
Use when designing, implementing, or reviewing an embedded accounting engine with append-only ledgers, mapped postings, idempotency, reversals, period locks, audit trails, and integrity tests.