First steps
After installing, you start Claude Code the usual way, with claude in your project. What is new is what Claude knows.
What changes
Section titled “What changes”- Skills load themselves. At session start, every plugin tells Claude in one sentence when its skills are needed. Write “the login is broken” and Claude reaches for
analyse-bugwithout you knowing the name. - You can also call them directly, for example
/awl-general:review. The exact spelling is on every page in the catalog. - The AWL principles are loaded: small changes, no inventing, think first.
Three prompts to try
Section titled “Three prompts to try”In a project you do not know yet:
/awl-general:explain-codebase
Before you open a merge request:
Review my changes on this branch.
When you have implemented a story:
Check the ACs of the story for this branch.
The last prompt uses ac-checker: it reads the issue number from the branch name and checks every acceptance criterion against the code.
Where to go next
Section titled “Where to go next”- How we work – the whole path from story to deploy.
- Playbooks – concrete tasks, step by step.
- Questions: #tools-claudecode on Slack.