developers-amsterdam

Enforce Amsterdam engineering standards and governance artifacts across projects.

24|2|Updated Mar 20, 2026

Search Tags:#architecture #adr #governance #wcag #git-workflow #engineering-standards #eu-pl-v1.2

Ready to run

npx skills add https://github.com/Amsterdam/amsterdam-agent-skills --skill developers-amsterdam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: developers-amsterdam
Source: https://github.com/Amsterdam/amsterdam-agent-skills/tree/main/skills/developers-amsterdam
Command: npx skills add https://github.com/Amsterdam/amsterdam-agent-skills --skill developers-amsterdam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

City-wide projects risk inconsistent architectures and diverging tech decisions. This skill standardizes governance by enforcing Amsterdam's engineering standards from day one.

Core Features & Use Cases

Clarify Before Building: prompts decision gates to surface essential choices (backend language, database, repo structure) before implementation.
Governance & Compliance: ensures ADRs, changelog, EU-PL v1.2 licensing, WCAG compliance, and architecture decision records are created and followed.
Template-Driven setup: provides a standard README/ADR/template scaffolding and repo setup guidance to accelerate compliant launches.
Use Case: When starting a new Amsterdam project, run the standard checks to align on tech stacks, repo layout, and governance artifacts.

Quick Start

Review the decision gates and apply the standards before coding to ensure compliant architecture, repo setup, and governance.

Frequently Asked Questions about developers-amsterdam

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce engineering standards and architecture decisions for Amsterdam projects?▼

To enforce engineering standards for Amsterdam projects, apply decision gates during project initiation and tech stack selection to ensure uniform architecture. This validates that governance artifacts like ADRs and changelogs are correctly implemented and aligned from day one.

What is included in Amsterdam project governance and compliance checks?▼

Amsterdam project governance checks include validating the creation of architecture decision records, changelogs, EU-PL v1.2 licensing, and WCAG compliance. This ensures all governance artifacts align with the official Amsterdam GitHub workflow.

How do I set up a compliant GitHub repository for Amsterdam city projects?▼

Set up a compliant Amsterdam repository using template-driven scaffolding for standard README and ADR files. This accelerates compliant launches by enforcing the correct repo layout, governance artifacts, and GitHub workflow structure before coding begins.

When do I need to create architecture decision records for Amsterdam projects?▼

You need to create architecture decision records during project initiation and tech stack selection. Prompting decision gates at these stages surfaces essential choices like backend language and database, ensuring compliant architecture before implementation starts.

Does Amsterdam project development require EU-PL v1.2 licensing and WCAG compliance?▼

Yes, Amsterdam project development requires EU-PL v1.2 licensing and WCAG compliance. Governance reviews validate that these specific licensing and accessibility standards are documented and followed alongside standard architecture decision records.

What is the best way to standardize tech stack selection across city-wide projects?▼

The best way to standardize tech stack selection across city-wide projects is to apply standardized decision gates before implementation. This prevents inconsistent architectures and diverging technical decisions by enforcing uniform engineering standards early.