Marcos Paulo
dc6cb5a0a3
Pushing main now rebuilds the site and force-pushes dist/ to pages. .agents/scripts/publish-pages.sh does the work. It never checks pages out: it writes a tree straight from dist/ with write-tree and commit-tree, so the working tree is untouched and a failure halfway through leaves nothing behind. The commit is parented on the current pages tip, so the branch keeps its history and a rollback is one force-push to an earlier commit -- which the script prints before it pushes. It refuses to publish when the working tree is dirty, when HEAD is not main, when HEAD is not the commit being pushed, or when any of the ten routes is missing or empty in dist/. A build can succeed and still emit a stub; that is exactly how this site would go down. The hook guards three ways. AF_PUBLISHING short-circuits it so the publisher's own push does not re-enter it forever. AF_NO_PUBLISH=1 lets you push main without publishing. And because git has no post-push hook, the publish necessarily runs before main lands -- so it first checks that the remote tip is an ancestor of what is being pushed, and skips publishing when the push could still be rejected as a non-fast-forward. Also rewrites the operations guide's rollback section, which still described merging main into pages with --ff-only. That has not been true since pages started carrying build output. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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 bilingualfull-guide, the chapter pages,rules,skills, andskills-reviewsrc/components/— blocks and islands; the interactive diagrams, selectors, and the language togglesrc/content/— the content collections every page renders fromsrc/styles/tokens.css— the design tokenslegacy/— 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.mdpublic/— assets copied to the site root verbatim: fonts, the hands-on labs, andsubmitted-skills/docs/references/— bundled research sources and notesdocs/operations-guide.md— canonical SilverBullet operations and skills guidepublic/hands-on/starter/— dependency-free Tiny Tasks exercisepublic/hands-on/rules/— dependency-free Guardrails lab; toggles rule sources into the promptskills/— reusable design and rules-case-study skillsGATES.md— acceptance ledger for the project
Publishing
The Gitea instance has a Pages Server configured to publish a repository’s
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 repository’s pages branch exists. Gitea itself does not provide a built-in
Pages server; this setup uses the instance’s 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.