peterbamuhigire/chwezi-dev-engine - Page 3

doc-architect

Use when generating or repairing layered AGENTS.md project guidance from verified repository structure, technology, data, and planning conventions.

git-collaboration-workflow

Use when planning branch strategy, making commits, reviewing diffs, resolving conflicts, preparing pull requests, or shipping releases. Covers trunk-friendly collaboration, commit hygiene, conflict recovery, and CI-linked release discipline.

markdown-lint-cleanup

Use when fixing Markdown lint failures, heading structure, list spacing, code-fence languages, or local formatting consistency without changing document meaning.

sdlc-documentation

Use when producing, reviewing, or consolidating SDLC documentation across planning, requirements, design, testing, deployment, user rollout, post-deployment, and maintenance phases. Load absorbed SDLC phase references as needed.

skill-composition-standards

Use when authoring, normalising, or reviewing skills that must follow the repository house style, capability boundaries, input/output contracts, decision rules, references, and composition gates.

skill-engine-audit

Use when auditing, grading, benchmarking, or conforming an entire skills engine. Measures taxonomy, doctrine, contracts, depth, routing, safety, references, output readiness, and normalisation priorities.

skill-writing

Use when creating or upgrading reusable skills, specialist-role instructions, or vendor adapters. Covers agent-versus-skill boundaries, model-neutral canonical sources, triggers, capability and output contracts, progressive disclosure, validation, and…

world-class-engineering

Use when designing, building, reviewing, or upgrading production software systems that must be secure, performant, maintainable, scalable, and user-centered. Apply before writing specs, code, architecture, APIs, databases, mobile apps, SaaS platforms, or ERP…

code-safety-scanner

Use when scanning a codebase before deployment for critical vulnerabilities, server-error risks, unsafe AI-generated code, dependency problems, or payment misconfiguration.

linux-security-hardening

Use when hardening or auditing Debian and Ubuntu hosts for identity, sudo, PAM, MFA, permissions, AppArmor, auditd, kernel, patching, integrity, boot, encryption, and CIS controls.

network-security

Use when designing, hardening, or auditing network security for self-managed SaaS infrastructure, including firewalls, WAF, VPN, TLS/PKI, IDS/IPS, SSH, segmentation, DDoS, and DNS controls.

vibe-security-skill

Use when designing or reviewing application, API, or multi-tenant SaaS security. Produces threat models, abuse cases, authorisation matrices, secret plans, and OWASP-aligned evidence.

web-app-security-audit

Use when auditing a PHP/JavaScript/HTML web application for security vulnerabilities. Covers configuration, authentication, authorization, input validation, XSS, API security, HTTP headers, and dependency scanning. Produces a severity-rated audit...

ai-slop-audit

Use when auditing or scoring an artefact for AI slop after a major iteration or before release. Produces evidence-backed findings, severity, fixes, genericness score, and an A/B/C/F verdict.

anti-ai-slop

Use when producing any human-facing artefact. Applies real-time anti-slop controls for specificity, verification, authored intent, hard cases, language, code, UI, and release quality.

00-meta-initialization

Use when starting project documentation to detect project type, select Waterfall, Agile, or Hybrid delivery, and generate the documentation roadmap.

engine-control-plane

Use when coordinating or auditing multi-engine workflows, agent roles, command surfaces, hooks, evidence contracts, handoffs, or bounded recovery. Keeps domain doctrine in the owning engines.

advanced-testing-strategy

Use when designing or reviewing test strategy for production systems, APIs, mobile apps, SaaS platforms, ERP workflows, and AI-enabled systems. Covers unit, integration, contract, end-to-end, regression, release-gate, and risk-based testing decisions.

electronic-fiscal-taxing

Use when implementing or reviewing electronic fiscal taxation integrations in web, ERP, POS, or mobile-backed systems; covers jurisdiction adapters, tenant-scoped tax identities, API security, queues, offline operation, fiscal evidence, and Uganda EFRIS as…

full-coverage-saas-seeding

Use when designing, implementing, executing, replaying, or verifying a realistic synthetic SaaS tenant through the product's supported UI, APIs, application services, commands, and workflow boundaries for both prospect demonstration and full system testing.

pos-sales-operations-engineering

Use when implementing or reviewing a tenant-aware ERP POS, agent POS, or manual sales-entry workflow where customer defaults, product-to-stock identity, inventory timing, payments, permissions, and audit-safe posting must remain consistent. Use the design…

game-development-orchestration

Use when initiating, replanning, or governing a complete game project from concept through vertical slice, production, certification, and post-launch; routes specialist game skills and prevents premature full-production commitment.

ai-evaluation

Use when setting up quality assurance for AI features — defining evaluation criteria, measuring output quality, using AI-as-judge, monitoring production AI, detecting drift, and building user feedback loops

image-compression

Use when implementing or reviewing client image optimisation plus authoritative server decode, validation, resize, metadata stripping, and canonical re-encoding. Use saas-managed-visual-assets for administrative asset lifecycle and frontend-performance for…

gameplay-systems-architecture

Use when specifying or implementing engine-neutral gameplay systems such as movement, combat, AI, quests, dialogue, inventory, progression, save/load, world state, spawning, cameras, or narrative state; engine skills own framework integration.

unity-mobile-game-development

Use when building, restructuring, profiling, testing, or packaging a Unity mobile game in C# for Android or iOS; covers project architecture, scenes, prefabs, data, input, assets, saves, builds, and Unity-specific release evidence.

distributed-systems-patterns

Use when designing or reviewing multi-service, message-driven, or eventually consistent systems. Covers service boundaries, consistency tradeoffs, event workflows, outbox and inbox patterns, sagas, ordering, and idempotency.

microservices-architecture

Use when designing, reviewing, or refactoring microservice boundaries, communication, service ownership, deployment independence, resilience, and distributed data flows. Load absorbed microservices fundamentals, models, communication, and resilience…

postgresql-operations

Use when administering, tuning, backing up, restoring, monitoring, or troubleshooting PostgreSQL production systems. Load the absorbed PostgreSQL administration and performance reference files for operational runbooks, query tuning, vacuum, replication, and…

javascript-modern

Use when writing or reviewing modern JavaScript for browser or PHP-backed SaaS applications, including modules, asynchronous flows, error handling, language features, and performance.

php-modern-standards

Use when writing or reviewing PHP 8+ applications, object-oriented domain code, Laravel services, PSR-compliant packages, secure request handling, tests, or performance-sensitive PHP.

implementation-status-auditor

Use when auditing actual software implementation status against requirements, plans, schemas, integrations, tests, and release evidence, with a prioritised completion blueprint.

document-spreadsheet-tooling-readiness

Use when checking whether this machine can generate and validate requested DOCX, PDF, XLSX, workbook, register, budget, or dashboard outputs.

game-accessibility-localisation-and-player-safety

Use when designing or testing accessible gameplay, remapping, visual/audio alternatives, difficulty assists, localisation/internationalisation, cultural review, chat/community safety, reporting, moderation, parental controls, or player-support escalation.

game-data-analytics-and-live-economy

Use when defining game telemetry, player funnels, retention or progression metrics, experiments, remote configuration, virtual economy sources and sinks, live events, anomaly controls, or ethical data-driven decisions.

game-studio-delivery-and-commercial-operations

Use when running game discovery, estimation, staffing, RACI, greenlight, statements of work, milestone governance, outsourcing, client demos, change control, launch command, postmortems, or evidence-based case studies.

game-testing-polish

Use when planning or executing game QA, playtesting, balance, usability, compatibility, accessibility, localisation, save migration, regression, bug triage, polish prioritisation, alpha, beta, or release-candidate gates.

lean-game-product-development

Use when converting a game idea, mechanic, feature, vertical slice, production milestone, or live change into falsifiable hypotheses, prototypes, measurements, learning and go/narrow/pivot/stop decisions; use game-development-orchestration for the full…

mobile-game-design

Use when designing or validating a mobile game's player fantasy, core loop, touch controls, sessions, onboarding, accessibility, progression, economy, retention, and ethical monetisation; use engine skills for implementation.

skill-safety-audit

Use when reviewing new, imported, or changed skills for unsafe tools, installers, credential harvesting, hidden execution, prompt injection, excessive permissions, data exfiltration, or improperly retained third-party source content.