Marcos Paulo 3daad86db8 feat(i18n): wire audit-translations into pnpm run verify
Wires the .agents/scripts/audit-translations.mjs script into the
existing pnpm run verify chain as the first gate. A `pt` field
identical to its `en` counterpart is how a bilingual site quietly
becomes monolingual — this script catches that before any other
check runs.

Added an allowlist mechanism: the script now reads a sibling
`.agents/scripts/audit-translations.allowlist.json` file. Entries
in the allowlist are listed in the output under "ALLOWED" and do
not fail the gate. Currently 18 entries: numeric card labels
("01"–"06") in chapters/landing.json and chapters/summary.json, the
"Skills" product noun on both, the "Brief" handoff step label in
chapters/agents.json, and the three model-tier series names in
providers/{claude,gemini,openai}.json.

Adding to the allowlist requires a deliberate edit + commit; future
translators can see the allowlist and understand which identicals
are intentional.

The verify chain order is now:

  1. audit-translations.mjs  — fail-fast on translation regressions
  2. verify.mjs              — content + interaction contracts
  3. audit-ui.mjs            — responsive / no-external-dep audit
  4. check-tokens.mjs        — design-token enforcement

Ownership notes:

  - package.json is owned by the astro-architect agent per
    .agents/rules/git-worktrees.md. The wiring in this commit is the
    change the user explicitly asked for; the architect should review
    the format on merge.

  - scripts/verify.mjs is owned by the verification-engineer agent
    per the same table. The pre-existing assertion that `package.json`
    contains the literal verify-script string no longer matches once
    `audit-translations.mjs &&` is prepended. This commit updates the
    assertion from a strict `.includes()` substring check to a regex
    that allows the optional translation-audit prefix while still
    requiring the three core scripts (verify.mjs, audit-ui.mjs,
    check-tokens.mjs) to run in order. The regex still rejects any
    chain that drops one of them.

Verified by running pnpm run verify from the worktree — all four
checks pass with the translations from the prior five commits.
2026-09-06 21:18:48 -03:00
2026-09-05 04:29:42 +00:00

AI For Dummies

A lightweight, presentation-style field guide to AI-assisted engineering.

It explains how to combine a strong planning/review model with faster workers, reusable skills, subagent handoffs, Git worktrees, and explicit verification. An interactive field kit compares common behavior skills such as ponytail-lite, caveman, unlazy, research, debugging, and review. The skill-forge workflow covers discovery, triggers, package anatomy, progressive instructions, structural validation, and behavioral iteration. The hands-on lab provides a tiny starter project and copy-ready baseline and skill-enabled prompts for a short side-by-side exercise. An interactive model gearbox separates capability tier from reasoning effort across OpenAI, Claude, and Gemini, and every featured skill links to a pinned source with an approval-first installation prompt.

Run locally

This is an Astro static site. It builds to dist/ and ships no runtime dependencies.

pnpm install
pnpm run dev        # http://localhost:4321/ai-for-dummies/
pnpm run build      # writes dist/
pnpm run preview    # serves the built output

Verify the content and interaction contracts with:

pnpm run verify     # reads dist/, so build first

The full gate — astro check, astro build, verify.mjs, audit-ui.mjs, check-tokens.mjs, and the assertion-count floor — runs as:

bash .agents/scripts/gate.sh

Project structure

  • src/pages/ — one file per route: the landing route map, the complete bilingual full-guide, the chapter pages, rules, skills, and skills-review
  • src/components/ — blocks and islands; the interactive diagrams, selectors, and the language toggle
  • src/content/ — the content collections every page renders from
  • src/styles/tokens.css — the design tokens
  • legacy/ — the editorial visual system and the review-desk modules, not yet migrated into components. Still imported by the pages that need them; see .agents/context/architecture.md
  • public/ — assets copied to the site root verbatim: fonts, the hands-on labs, and submitted-skills/
  • docs/references/ — bundled research sources and notes
  • docs/operations-guide.md — canonical SilverBullet operations and skills guide
  • public/hands-on/starter/ — dependency-free Tiny Tasks exercise
  • public/hands-on/rules/ — dependency-free Guardrails lab; toggles rule sources into the prompt
  • skills/ — reusable design and rules-case-study skills
  • GATES.md — acceptance ledger for the project

Publishing

The Gitea instance has a Pages Server configured to publish a repositorys pages branch under pages.marcospaulo.dev.br. pages now carries the built site — the contents of dist/ — not a copy of main. The intended site address is:

https://netcracker.pages.marcospaulo.dev.br/ai-for-dummies/

If the URL is not available yet, verify that the pages branch exists and that the repositorys pages branch exists. Gitea itself does not provide a built-in Pages server; this setup uses the instances separate Pages Server and Actions deployment path.

For the complete authoring, verification, publication, rollback, worktree, and skill workflow, see docs/operations-guide.md.

Reader voting on the skills-review desk

skills-review/ is static, so its "which draft would you ship?" vote widget calls a separate stateful service — a small Go API on its own pod, one vote per visitor enforced server-side by IP (a MAC address is never visible to a server across the internet, so it cannot be used). Its source no longer lives in this repository; the deployed service is unchanged. src/pages/skills-review.astro sets window.SKILLS_REVIEW_VOTE_API to point at it.

Research

See docs/references/README.md for official Claude, Codex, and Git documentation. The additional reading path bundles 12 verified articles and guides, including Medium and practitioner sources. See model routing for current provider controls and verified skill sources for commit-pinned provenance.

Rules and enforcement case study

Open /rules/ for a concise walkthrough grounded in the netcracker/interview repository. It shows how AGENTS.md, project-local skills, machine-readable repo ledgers, a UI contract ratchet, lint-staged, Husky, commitlint, specialist verifier agents, and PR review reinforce one another. Every example links to its source file in Gitea, and the page includes a copy-ready prompt for mapping the same layers in another repository.

The implementation patterns are also packaged as project-local skills in skills/. Use editorial-playbook when adding chapters or sections, and rules-case-study when turning repository controls into a source-linked teaching page.

S
Description
A lightweight field guide to AI-assisted engineering workflows
Readme 14 MiB
Languages
Astro 51.3%
Python 16.3%
JavaScript 14.6%
Shell 12.9%
CSS 2.8%
Other 2.1%