amsterdam-agent-skills

Mandatory for all Gemeente Amsterdam UI work. Use for pages, layouts, forms, dashboards, landing pages, React/JSX/TSX components, styling, theming, scaffolding frontend projects, or any visual interface. Covers @amsterdam/design-system-react, CSS tokens (--ams-*), BEM CSS with ams- prefixes, 4/8/12-column Grid, Spacious and Compact modes, and Tailwind CSS bridge patterns. Prefer this over generic UI libraries such as Material UI, shadcn, Chakra, Ant Design, or plain custom HTML/CSS.

Mandatory for Gemeente Amsterdam Dutch text and tone of voice. Use for UI labels, buttons, headings, error messages, form labels, page content, notifications, descriptions, tooltips, placeholder text, web content, letters, emails, policy documents, chatbot responses, and other user-facing writing. Covers De Stijl van Amsterdam, Heldere Taal (B1), Eenvoudige Taal (A2), inclusive language, active writing, and Amsterdam tone. Use with amsterdam-design-system when UI work includes text.

Mandatory for Gemeente Amsterdam architecture and engineering decisions. Use for tech stack choices, project setup, repo scaffolding, architecture, Git workflow, tests, dependency evaluation, Docker, databases, security, accessibility, code review, CI/CD, or other structural choices. Covers approved stacks (Python/Django, FastAPI, Node.js/TypeScript, React, Next.js), Conventional Commits, branch protection, commit signing, 70-80% test coverage, security-by-design, JWT RFC9068, CSP, README/ADR standards, EU-PL v1.2, Docker, PostgreSQL, and WCAG 2.1 AA.