Amsterdam

Maak een Jira ticket aan.

Werk een ticket-idee uit tot een compact Nederlands Jira-concept.

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in a date-prefixed folder under ./docs/plan/ (for example ./docs/plan/2026-06-02-feature-name/plan.md). Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

Create a PRD through user interview, codebase exploration, and module design, then write the PRD to a date-prefixed feature folder under ./docs/plan/ (alongside plan.md if it exists). Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

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.

Reference clean code principles for readability, maintainability, naming, function design, tests, and code smell checks. Use when reviewing code quality, planning refactors, or checking whether a change stays simple and understandable.