From diataxis
Use when the user asks for a tutorial, beginner walkthrough, getting-started lesson, first-project guide, or onboarding material for new users. Creates learning-oriented step-by-step lessons where readers learn by doing something meaningful. The goal is skill and confidence, not task completion. Do not use for advanced tasks, troubleshooting, or exhaustive product coverage — those are how-to guides.
npx claudepluginhub jayteealao/agent-skills --plugin diataxisThis skill uses the workspace's default tool permissions.
Create a true tutorial: a learning-oriented lesson in which the reader learns by doing something meaningful.
Creates new Angular apps using Angular CLI with flags for routing, SSR, SCSS, prefixes, and AI config. Follows best practices for modern TypeScript/Angular development. Use when starting Angular projects.
Generates Angular code and provides architectural guidance for projects, components, services, reactivity with signals, forms, dependency injection, routing, SSR, ARIA accessibility, animations, Tailwind styling, testing, and CLI tooling.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Create a true tutorial: a learning-oriented lesson in which the reader learns by doing something meaningful.
This is not a how-to guide. The aim is not to help an already-competent user complete a task, but to help a learner build skill and confidence.
Use this skill when the user asks for:
Do not use this skill for troubleshooting, advanced tasks, operational runbooks, or exhaustive product coverage.
A tutorial should say, in effect:
"Stay with me, follow these steps, and you will successfully build or do something concrete."
The author is responsible for the learner's path and success.
Use this shape:
State what the learner will accomplish, not what they will "learn".
Good:
Bad:
Get to a meaningful output quickly.
Every step should create an observable result:
Tell the learner what should happen next.
Use language like:
Only explain just enough for the step to make sense. Move conceptual depth into explanation pages.
Choose defaults for the learner. Do not branch unless absolutely necessary.
A shorter tutorial that works is better than a broad tutorial that overwhelms.
Produce a tutorial that:
Before returning, verify: