Skip to content
Skills Library
Programming · Planning

chwezi-dev-engine

/chwezi-dev-engine

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, catalog maintenance, delivery evidence packs, routing fixtures, and world-class engineering quality gates.

Licence
MIT
Last repository change
24.10.2026

Assessment and security

98/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene13 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
12
Scripts
2
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: install.ps1, install.sh

What it does and when to use it

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, catalog maintenance, delivery evidence packs, routing fixtures, and world-class engineering quality gates.

Original author description

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, catalog maintenance, delivery evidence packs, routing fixtures, and world-class engineering quality gates.

How it works

  1. Non-negotiable foundation
  2. Route by intent
  3. Running example
  4. Release workflow
  5. Stop conditions
  6. See also
Original SKILL.md headings · 72 lines, 618 words
SKILL.md preview
---
name: chwezi-dev-engine
description: 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, catalog maintenance, delivery evidence packs, routing fixtures, and world-class engineering quality gates.
---

# Chwezi Dev Engine Router

This is the entrypoint for the `chwezi-dev-engine` engine. It routes engineering work to the smallest accurate active skill, applies quality gates, and records evidence so outputs can be reviewed by a team that did not write them.

Standard implemented: Chwezi Dev Engine July 2026 upgrade baseline (engine formerly named Skills Web Dev; folder renamed 2026-09-20). Last verified: 2026-09-17.

## Non-negotiable foundation

Always apply these before domain work:

1. `skills/sdlc-meta/anti-ai-slop/SKILL.md` while producing any artifact.
2. `skills/sdlc-meta/ai-slop-audit/SKILL.md` after each major iteration and at release.
3. `templates/delivery-dod/evidence-pack.md` for implementation, architecture, security, data, DevOps, AI, SaaS, mobile, or documentation deliverables.
4. `docs/source-registers/ai-platforms.md` when work depends on current AI, Apple, cloud, security, or framework facts.

5. `skills/sdlc-meta/kaizen-improvement-system/SKILL.md` for every engine audit, product audit,
   book-driven improvement, and post-iteration learning cycle. Published audits are capped at
   65/100; improvement plans target 95/100 and require evidence.

When a task requires external research, use the Digital Research Engine at `C:\wamp64\www\digital-research-engine`, beginning with its `source-evaluation` and `source-verification` skills.

## Route by intent

| Intent | Primary skill family |
|---|---|
| AI application, model gateway, RAG, evaluations, agent runtime, HITL, AI cost or security | `skills/ai/*` |
| API contract, system architecture, distributed systems, microservices, validation contracts | `skills/architecture/*` |
| Database schema, SQL, MySQL, PostgreSQL, reliability, persistence | `skills/backend-databases/*` |
| CI/CD, cloud, containers, Kubernetes, release engineering, observability, reliability | `skills/devops-cloud/*` |
| React, Next.js, Tailwind implementation, frontend performance, image compression, content UX | `skills/frontend-ux/*` |
| Android, iOS, Kotlin Multiplatform, PWA, mobile operations | `skills/android/*`, `skills/ios/*`, `skills/mobile-cross/*` |
| Desktop applications, Avalonia UI and Python executable-suite packaging | `skills/frontend-ux/avalonia-desktop-development`, `skills/languages/python-modern-standards`, `skills/languages/csharp-dotnet-development` |
| GIS maps, spatial data, PostGIS and mapping APIs | `skills/gis/gis-platform-engineering` |
| Games, gameplay, interactive narrative, game assets, builds and live operations | `skills/game-development/game-development-orchestration` then the required specialist |
| TypeScript, JavaScript, Python, PHP, C#/.NET, Java/JVM, Spring, Jakarta EE, Hibernate, Maven, Gradle, WebLogic, Quarkus, Micronaut, Helidon, GraalVM | `skills/languages/*` |
| SaaS tenancy, pricing, billing, entitlements, SSO/SCIM, portability, admin tooling | `skills/saas/*` |
| Security audit, code safety, DPIA, Linux hardening, network security | `skills/security/*` |
| Product discovery, business metrics, documents, spreadsheets, proposal readiness, delivery control | `skills/product-business/*` |
| SDLC documentation, skill writing, catalog guardrails, world-class engineering gates | `skills/sdlc-meta/*` and `00-meta-initialization/*` |
| Finance/accounting rules, statutory values, IFRS, close, audit, payroll, tax | External `chwezi-accounting-doctrine`; local finance skills only orchestrate implementation |
| Visual design, typography, UI/UX appearance, documents, slides, spreadsheets, PDF visual polish | External `chwezi-design-engine` |
| Complete website delivery, content, SEO and launch | External `website-skills`; retain technical implementation here |
| Formal SRS, lifecycle specifications and governance artefacts | External `chwezi-sdlc-documentation`; retain implementation evidence here |

## Running example

Use `docs/world-class-exemplars/running-example.md`: a Chwezi Core Systems multi-tenant field-service SaaS called **FieldOps Ledger**. The same example threads through architecture, API, database, identity, security, reliability, deployment, and evidence-pack artifacts.

## Release workflow

1. Read the selected domain `SKILL.md`.
2. Load only the domain references, templates, and examples that the skill points to.
3. If current facts are needed, check the appropriate source register and invoke Digital Research Skills Engine verification.
4. Produce the artifact and evidence pack together.
5. Run `python -X utf8 scripts\skill_catalog_guardrails.py --report-only` after routing or catalog changes.
6. Run `python -X utf8 scripts\routing_smoke_test.py --report-only` after routing fixtures or frontmatter changes.
7. Ship only when the evidence pack, anti-slop gate, and relevant domain validation pass.

## Stop conditions

Stop and ask or research further when the request lacks a decision/audience, requires current platform/legal/statutory facts that have not been verified, asks for fabricated evidence, changes active-skill count without a routing reason, or would delete/move skill directories contrary to `AGENTS.md`.

## See also

- `README.md`
- `docs/skill-routing-index.md`
- `docs/skill-aliases.yml`
- `docs/catalog-cleanup/empty-directory-disposition.md`
- `templates/delivery-dod/evidence-pack.md`
- `examples/full-stack-saas-reference/README.md`
Files in this package (12)
  • .gitignore 1 KB
  • AGENTS.md 15 KB
  • CHANGELOG.md 4 KB
  • CLAUDE.md 1 KB
  • CONTRIBUTING.md 2 KB
  • LICENSE 1 KB
  • README.md 81 KB
  • REPLICATE-ROUTING.md 1 KB
  • SKILL.md 6 KB
  • install.ps1 1 KB
  • install.sh 2 KB
  • requirements-ci.txt 1 KB

Versions

The database has no other skills named chwezi-dev-engine.

Database snapshot: 13.11.2026 · package version 2054a310aa08 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100sdlc
    Run the autonomous SDLC pipeline on a task — the single entrypoint driving spec → review → build → test → security → delivery through the profile's quality gates. Use to run the SDLC or ship a feature.
  • 100sdlc
    Run the autonomous SDLC pipeline on a task — the single entrypoint driving spec → review → build → test → security → delivery through the profile's quality gates. Use to run the SDLC or ship a feature.
  • 85engineering-principles
    Use when designing systems, structuring code, reviewing diffs, handling state, or adhering to core software engineering discipline principles.
  • 100engineering-skills
    Index of the engineering-team skills bundle for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw, and 6 more tools. Architecture, frontend, backend, QA, DevOps, security, AI/ML, data engineering, Playwright, Stripe, AWS, MS365 (stdlib-only Python tools). Use when browsing or…
  • 100agentic-skills
    Production engineering lifecycle for spec-first, test-driven implementation, review, and staged shipping; use for disciplined software delivery with explicit quality gates.
  • 98skill-writing
    Use when creating or normalising reusable proposal skills, trigger routes, contracts, references, or authoring automation under the canonical chwezi-dev-engine skill-writing standard; use skill-safety-audit instead for a read-only security review.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.