peterbamuhigire

Top-level router for the Chwezi Core Systems web-development and software-engineering skills engine. Use for AI systems, SaaS, architecture, APIs, databases, security, frontend engineering, mobile, DevOps, reliability, product engineering, SDLC documentation,…

Use when turning a design system, product requirement, or frontend codebase into a maintainable component, content, state, and delivery architecture with measurable quality gates.

Use when auditing or improving this engineering engine or a product it produces. Coordinates evidence-backed baselines, small experiments, standardisation, and re-audits without replacing domain skills.

Use when auditing or tuning a development machine's Claude Code or Codex setup for context, model, subagent, permission, or token efficiency. Analyse local capabilities first and apply only supported reversible changes; route runner-specific details to the…

Use when defining database SLOs, error budgets, backup verification, capacity policy, incident response, game days, or MySQL and PostgreSQL on-call practice.

Use when designing tenant isolation, panel boundaries, zero-trust authorization, audit trails, or tenant permission overrides.

Use when checking that every irreversible agent action has signed approval evidence linked to the action audit log, and producing an approval-gap register or audit evidence pack.

Use when capturing kill-switch, red-team, and eval-drift drills as audit-ready compliance evidence — minimum-cadence enforcement, pass/fail recording, and cross-link to the incident drill skill. Turns drills from operational exercises into SOC 2 / ISO 27001 /…

Use when auditing or improving the social-media engine or any campaign, content system, strategy, report, training asset, or marketing product it produces.

Use when the main deliverable concerns full-funnel content across awareness, engagement, subscription, conversion, retention, and advocacy; use 10-content-pillars when that neighbouring workflow owns the primary decision.

Use when AI Data Foundation Plan is needed to produce an implementation plan for social-media or digital-marketing work; use `ai-readiness-diagnostic` when its narrower outcome is requested.

Use when designing or improving a Crisis Communications operating playbook with roles, ordered actions, controls and measures. Use platform skills for channel plans and strategy skills for upstream direction.

Use when the main deliverable concerns healthcare trust, patient-safe content, misinformation response, and East African health-sector communication; use policy-ai-content-ethics when that neighbouring workflow owns the primary decision.

Use when AI Content Humaniser is needed to produce a AI content humaniser deliverable for social-media or digital-marketing work; use `ai-readiness-diagnostic` when its narrower outcome is requested.

Use when Content Writing Skill is needed to produce a content writing deliverable for social-media or digital-marketing work; use `caption-writer` when its narrower outcome is requested.

Use when Language Standards — Multi-Language Tone & Grammar is needed to produce a language quality specification for social-media or digital-marketing work; use `east-african-english` when its narrower outcome is requested.

Use when independently reviewing drafted requirements for correctness, completeness, consistency, feasibility, traceability, and testability before baselining; use requirements-analysis to resolve raw elicitation conflicts.

Use when comparing solution candidates or prototypes to reduce uncertainty before locking requirements or design; use UX-specification after the chosen interaction direction is approved.

Use when specifying a SaaS aha event, activation milestones, segmented paths, nudges, measurement sources, and drop-off interventions. Use customer-success-playbook for ongoing intervention and user-manual for product procedures.

Use when specifying, planning, tracing, or reviewing realistic synthetic SaaS demo data and application-workflow test coverage for an SRS, PRD, test plan, release gate, or go-live evidence pack.

Use when auditing or improving the SDLC documentation engine or any PRD, SRS, architecture, test, deployment, governance, or game documentation product it produces.

Use when converting approved discovery evidence into a traceable PRD with objectives, prioritised features, success measures, constraints, and release scope; use vision-statement for the strategic north star and lean-canvas while assumptions still need…

Use when a SaaS or digital product needs to choose, tier and sequence AI features, separate table stakes from differentiation, decide build versus buy, and define an AI moat; use AI economic value brief for a single initiative's value proof and AI…

Use when defining a game's player promise, product hypotheses, platform options, production model, vertical-slice evidence, commercial boundaries, or greenlight decision before detailed requirements.

Top-level router for the Chwezi Core Systems web-development and software-engineering skills engine. Use for AI systems, SaaS, architecture, APIs, databases, security, frontend engineering, mobile, DevOps, reliability, product engineering, SDLC documentation,…

iOS AI/ML standards for WWDC26 Apple intelligence work, including Foundation Models, Language Model providers, Dynamic Profiles, Core AI, Evaluations, Core ML, Vision, NaturalLanguage, Speech, SoundAnalysis, and privacy-first on-device inference.

iOS architecture orchestration for production apps, modular codebases, Swift patterns, App Intents, Foundation Models/Core AI provider boundaries, scale practices, and release-ready implementation boundaries.

iOS data persistence standards with SwiftData, Keychain, files, offline sync, Core Spotlight semantic indexing, App Entity data exposure, and AI cache/privacy boundaries.

iOS development standards for AI agent implementation. Swift-first, SwiftUI, MVVM + Clean Architecture, async/await, comprehensive security, testing, and performance patterns. Use when building or reviewing iOS applications, generating Swift...

StoreKit 2 in-app purchases, subscriptions, App Store Server API, group and organization subscription watch items, Unity StoreKit plugin routing, paywall UI, transaction verification, and App Store Connect configuration.

iOS platform capability orchestration for App Intents, Siri, Spotlight semantic indexing, widgets, biometrics, Bluetooth printing, push notifications, native PDF export, networking, media, and Apple framework entitlements.

iOS quality and release orchestration for Swift Testing 6.4, Device Hub, Xcode 27 agents, Xcode Cloud, AI Evaluations, Instruments, TestFlight, App Store review, stability, and release evidence.

Use when auditing or improving the business-plan engine or any business plan, strategy, model, pitch, nonprofit plan, or execution framework it produces.

Use when use before writing when market assumptions still need field validation. Use the relevant plan-section skill for section drafting.

Use when producing or reviewing the 08 operations plan component of a business plan; applies its specialist evidence, decisions, and acceptance tests instead of neighbouring pipeline skills.

Use when authoring an internal-control policy, risk-management framework, control matrix, or risk register for an East African organisation; use `finance-policy-and-manual` for finance procedures and defer accounting controls, audit evidence, and close…

Use when producing or reviewing the 07 marketing sales strategy component of a business plan; applies its specialist evidence, decisions, and acceptance tests instead of neighbouring pipeline skills.

Use when producing or reviewing the 14 ai integration component of a business plan; applies its specialist evidence, decisions, and acceptance tests instead of neighbouring pipeline skills.

Use when drafting or editing plans, proposals, pitches, reports, summaries, or founder narratives for clarity, argument, persuasion, originality, and human voice; use `language-standards` for multilingual correctness and `anti-ai-slop` for the mandatory…

Use when producing any human-facing business-plan artefact; applies live specificity, verification, authored-intent, hard-case, and language controls, while `ai-slop-audit` independently grades completed work.

Use when a SaaS bid needs buyer qualification through ICP fit, critical event, pain chain, role-level impact, decision process, and no-bid signals; use AI-on-SaaS discovery when AI data, model, or hallucination questions apply.

Use when a SaaS proposal needs a time-boxed POC or pilot with explicit scope, success measures, exit criteria, and a decision gate to implementation; use the AI-on-SaaS pilot skill when evaluation datasets or hallucination controls apply.

Use when routing, drafting, reviewing, or assembling a complete consulting proposal, EoI, bid, or tender response; use a numbered pipeline skill when only one known section is required.

Use when a proposal concerns banking, insurance, payments, mobile money, microfinance, digital finance, or financial inclusion; also apply the finance doctrine whenever money, ledger, tax, or accounting claims are in scope.

Use when routing a proposal to the correct procurement-framework and industry-sector skills before drafting; use profiles separately to determine proposer identity and voice.

Use when auditing or improving the proposal engine or any bid, tender, EOI, methodology, technical/financial proposal, or consulting product it produces.

Use when a proposal must address adoption, resistance, readiness, communications, transition, or organisational reform. Unlike capacity-building, this skill governs behaviour and operating-model change rather than teaching competencies alone.

Use when a proposal requires a theory of change, logframe, results framework, indicators, baselines, targets, learning, or evaluation. Unlike data-management, this skill defines performance questions and evidence use rather than the full data lifecycle.

Use when auditing this design engine or any rendered product for continuous improvement, evidence quality, visual readability, accessibility, AI trust, or repeatable remediation. Use design-audit for a single diagnostic without the Kaizen portfolio loop.

Use when packaging an approved identity into a client-facing guide with logo, colour, typography, spacing, imagery, voice, and application rules. Unlike brand-visual-identity, this documents settled decisions rather than creating the identity.

Use when an AI agent or copilot interface needs status, plans, approvals, uncertainty, interruption, or trust controls across web or mobile. Do not use for formatting a single AI answer; route output structure and citations to ai-output-design.

Use when an AI answer surface needs structure, citations, grounding, editable refinement, or a chat-versus-canvas decision. Do not use for agent autonomy, approvals, or execution status; route those interaction controls to ai-agent-ux.

Use when crafting or reviewing an individual chart, analytical exhibit, or data story for perceptual accuracy, decluttering, annotation, accessibility, and narrative focus. Use chart-selection-and-encoding to choose the chart type and…

Use when a banking, wallet, remittance, mobile-money, lending, transfer, balance, transaction, statement, fee, or payment-confirmation interface must prevent costly mistakes and build trust. Do not use for accounting rules or backend payment architecture;…

Use when defining reusable component anatomy, variants, states, slots, composition, APIs, or component documentation. Use design-tokens-and-naming for shared values and figma-and-tooling-workflow for tool-specific library operations.

Use when designing or reviewing a dashboard, analytics console, monitoring view, KPI scorecard, or data product with multiple metrics, charts, filters, drill-downs, and freshness states. Use chart-selection-and-encoding for chart choice and data-visualization…

Use when routing evidence-disciplined research across intake, source evaluation, web search, OSINT, due diligence, academic review, policy research, synthesis, verification, and final deliverables.

Use when research requires quantitative modelling: market sizing, triangulation, sensitivity analysis, scenario models, assumption registers, forecast models, data-quality caveats, and model audit checks.

Use when admitting any source into research and assessing its provenance, authority, independence, timeliness, bias, media integrity, and fit for a claim; use source-verification afterward to test URLs, quotes, statistics, claim links, and release readiness.

Use when drafting or revising an academic paper, essay, thesis, or dissertation with source-away composition, originality, citation, synthesis, voice, and register controls; use academic-reporting-standards for selecting formal study-reporting rules.

Use when planning, drafting, reviewing, or formatting a dissertation from research question through defence-ready manuscript; use academic-writing for prose originality and research-design for method selection.

Use when the engine must turn research into reusable knowledge assets, audience-specific variants, and monetizable offerings rather than a one-off document only. Encodes knowledge audit, asset design, reuse discipline, and commercialization framing.

Use when a research project needs formal questions, method selection, case logic, historical or trend design, MROC design, knowledge-lifecycle modelling, or a research-design document; use research-orchestration for wave planning and research-techniques for a…

Use when producing or revising any research artefact to prevent generic, unsupported, repetitive, or mechanically styled output in real time; use ai-slop-audit to grade a concrete completed iteration independently.

Use when an approved brand strategy must become an evidence-based narrative for About pages, case studies, heroes, or campaigns. Use `brand-strategy` to decide positioning and `premium-commercial-writing` when persuasion, SEO, and offer conversion dominate.

Use when discovery must establish audience, positioning, differentiation, architecture, and a decision-ready brand brief before design or copy. Use `brand-storytelling` after the strategy exists and `agency-positioning` for the agency's own commercial offer.

Use when auditing or improving the website engine or any website, landing page, ecommerce experience, dashboard, portal, or visual web product it produces.

Use when website pages or interface copy need clear message hierarchy, genuine voice, scannable structure, and evidence-aware editing; use `blog-writer` for articles and `sales-copywriting` for persuasion frameworks.

Use when a measured website question needs a pre-registered controlled test, power check, guardrails, analysis, and decision; use `cro-audit` to diagnose opportunities and `marketing-measurement-system` to define KPIs.

Use when a multilingual website needs cross-language tone, terminology, locale ownership, and consistency rules; use `french-native-copy`, `swahili-native-copy`, or `east-african-english` for language-specific execution.

Use when website, authority, offer, SEO, or sales-enablement writing must justify premium fees through buyer insight, proof, clear claims, and editorial restraint; use the owning execution skill for publishing or page implementation.

Use when sequencing an established offer through prelaunch, launch, close, and follow-up across a website, email, WhatsApp, or blog. Use `authority-offers` when the offer itself is undefined and `sales-copywriting` for deep page persuasion.

Legal sector website design for law firms. Use instead of generic sector-strategies when building websites for lawyers, law firms, solicitors, barristers, or legal consultants. Covers practice-area-specific design direction, client psychology for legal…

Canonical accessibility enforcement layer. Owns the WCAG 2.2 AA baseline, the automated axe-core gate, manual QA checklists, and the screen-reader smoke tests that every primary template must survive before deploy. Runs in the canonical CI pipeline as a hard…

Canonical Africa-realistic excellence layer. Owns the low-bandwidth, mobile-money, USSD-aware, multilingual, country-trust, and cultural-pattern standards that every African-market site is built and reviewed against. Global defaults are the floor; this skill…

Client retention, retainer architecture, recurring-revenue operations, post-launch reviews, expansion offers, and the agency's internal operating model. Use when productising retainers, planning post-launch review cadence, designing expansion offers, building…

Premium positioning, offer architecture, pricing logic, qualification, scope control, and proposal structure for a website agency selling $12,000+ engagements. Use when defining the agency category, building or pricing the offer, qualifying a prospect,…

Authority-product and lead-capture offer design for agencies and expert-led businesses. Use when packaging expertise into lead magnets, paid audits, email courses, webinars, workshops, diagnostic offers, playbooks, mini-products, or ascension paths that must…

Generate 15-25 targeted blog post ideas with 200-word summaries for any client website. Reads website content, assesses available information, adaptively selects from 20 ideation methods, and conducts a guided interview. Each idea includes a narrative brief +…

Generate SEO-optimised, bilingual blog articles with featured images, in-article photography, and distinctive per-article design. Articles are drafted and edited as markdown in docs/{lang}/blog/{slug}.md. On instruction, builds Astro blog pages from those…

Use when auditing or improving the Linux operations engine, linux-sysadmin skills, or any server, network, security, observability, automation, backup, database, or recovery product it produces.

Use when operating BIND or Unbound as an authoritative or recursive DNS server, including zone authoring, validation, reloads, reverse zones, transfers, and SELinux contexts. Use linux-network-admin for client-side resolution or interface configuration.

Use when designing or reviewing practical Linux security and incident resilience for NGOs, civil-society organisations, or small mission-led teams; use linux-server-hardening for host controls and linux-disaster-recovery for backup restoration.

Use when an authorised operator wants to remediate verified Linux security findings interactively across SSH, firewall, MAC, services, permissions, and updates; use linux-security-analysis first.

Use when recovering MySQL data, application files, configuration, boot state, or filesystems from a verified backup after loss or corruption; use linux-troubleshooting first when the fault may be recoverable without restore.

Use when a Debian/Ubuntu or RHEL-family server request needs routing across provisioning, security, services, networking, recovery, databases, containers, storage, performance, or compliance; use linux-troubleshooting when an unexplained symptom spans…

Use when operating or diagnosing systemd units, timers, targets, journal logs, restart policy, dependencies, or cgroup limits. Use a service-specific skill for application configuration and linux-virtualization for VM or system-container lifecycle.

Use when inspecting time-bounded journald or service logs, correlating web/database/security events, or managing logrotate retention; use linux-observability for forwarding and linux-troubleshooting for multi-subsystem incidents.

Use for legacy e-invoicing and fiscal-device requests that need compatibility routing; the canonical electronic fiscal taxing doctrine now owns jurisdiction-neutral controls and Uganda EFRIS references.

Use when designing, reviewing, or operating electronic fiscal taxation, e-invoicing, e-receipting, fiscal-device, or authority-reporting controls; load a jurisdiction reference such as Uganda EFRIS for verified local mechanics and keep tax administration…

Use when applying the IFRS Conceptual Framework to accounting policy development, recognition, measurement, materiality, presentation, disclosure, and judgement documentation when no Standard directly resolves the transaction or a Standard permits a policy…

Advanced financial-instrument classification, measurement, impairment, derecognition, modification, hedge-accounting and risk-disclosure review under IFRS 9 and IFRS 7, with Sections 11 and 12 routing for IFRS for SMEs.

Advanced lease identification, measurement, reassessment, modification, sale-and-leaseback, lessor and disclosure review under IFRS 16, with Section 20 routing for IFRS for SMEs.

IFRS 15 (full IFRS) and Section 23 (IFRS for SMEs) revenue recognition for Chwezi systems. Covers contract identification, performance obligations, transaction price, allocation, timing of recognition, contract assets and liabilities, refunds, warranties,…

Use when identifying, measuring, reviewing, or disclosing impairment under IAS 36 and Section 27, including CGU allocation, goodwill, value in use, fair value less costs of disposal, sensitivities, reversals, and disclosures.

Provisions, contingent liabilities and contingent assets under IAS 37 (full IFRS) and Section 21 (IFRS for SMEs). Recognition criteria (present obligation, probable outflow, reliable estimate), measurement, onerous contracts, restructuring, warranties,…