From diataxis
Use when the user asks for conceptual guides, architecture overviews, design rationale, trade-off discussions, background on how a subsystem works, historical context, or "why is it built this way?" documentation. Creates understanding-oriented content that builds mental models — the why, not the how. Do not use for direct task execution (use how-to) or factual lookup (use reference).
npx claudepluginhub jayteealao/agent-skills --plugin diataxisThis skill uses the workspace's default tool permissions.
Write understanding-oriented documentation that helps readers see the why, context, trade-offs, and larger picture.
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.
Write understanding-oriented documentation that helps readers see the why, context, trade-offs, and larger picture.
Explanation is not procedure and not reference. It is where reasoning belongs.
Use this skill when the user asks for:
Do not use this skill for direct task execution or factual lookup.
Explanation can include:
Explanation must not drift into:
Use a structure like:
Produce explanation that:
Before returning, verify: