Chaac Skills

The unified development process for every Tawa repo. If your Claude Code session loads `tawa-docs/.claude/rules/tawa-agile-workflow.md`, it will follow this…

The platform runs a Matomo instance at `engage.insureco.io`. Declare one line in your catalog and the builder provisions a per-environment Matomo site and…

The procedure for turning a brief ("a landing page for Acme with a waitlist") into a published site. The always-on rules are in `tawa-hypesites`; this is the…

A service that calls Claude does not need an Anthropic API key. Switch **Claude access** on for its OAuth client and the builder gives that service its own…

On 2026-09-26 an audit of iec-ledger found months of work reported "done" that an accountant could not use: 48 vendor fields in the API schema and 11 in the…

A **HypeSite** publishes a project's **artifact pages** in iec-portal as a real public website, with that project's **tables** as its database. Build the…

`tawa dev` reads your `catalog-info.yaml`, generates all platform environment variables, and either connects to real databases via SSH tunnels (online mode) or…

How to scaffold a new service on Tawa with `tawa sample`.

Renders a letter template to a PDF through docman and mails it through [Lob](https://lob.com). Delivery status arrives by webhook and is tracked per mailing.

A service that serves pages declares `spec.seo` in its catalog. On a prod deploy the builder registers the service's custom domain with **iec-webmaster** (the…

`tawa skills sync` pulls Claude Code rules and slash-commands onto every dev's machine. This is where that content comes from, and how to change it.

Human explainer: https://portal.insureco.io/spaces/iec-portal/pages/walkthrough-maker Styling rules: https://brand.insureco.io/artifact-spec.md

Half of what sits on a board is one person waiting on one or two facts from one other person. The work is not hard, it is just not *here* — and the loop that…

The architecture of the Tawa platform — what services exist, how they connect, and the URLs you need.

Plan and execute work using Forgejo as the source of truth. No local markdown files to overwrite — everything lives in the repo's milestones and issues.

A walkthrough is a short flow through a UI where every step **asserts** something on the page and then screenshots it. The output is a public page with the…

Coding agents (Claude, Cursor, Copilot, etc.) share a small set of persistent failure modes. They are not random and they are not model-specific — they all…