AD

add-skyux-component

End-to-end framework for creating and integrating SKY UX library components.

Install

mkdir -p .claude/skills/add-skyux-component && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10428" && unzip -o skill.zip -d .claude/skills/add-skyux-component && rm skill.zip

Installs to .claude/skills/add-skyux-component

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

End-to-end workflow for adding a new component (or directive/service) to an existing @skyux/* library in this Nx monorepo. Use when asked to "add a component", "create a new SKY UX component", scaffold a component with its module, harness, code example, tests, and docs, or wire a new component into a library''s public API. Covers file layout, the src/index.ts barrel and sky/Sky prefix rules, SCSS compat overrides, test harness, code-example unit tests, documentation.json, and the test/lint/format/commit gate.
514 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • →Scaffold component structure
  • →Wire components to library APIs
  • →Create test harnesses
  • →Add visual tests
  • →Update documentation

How it works

It scaffolds the component, module, spec, harness, and documentation, then wires it into the library's public API.

Inputs & outputs

You give it
Library name and component name
You get back
Scaffolded and wired component

When to use add-skyux-component

  • →Adding new SKY UX components
  • →Scaffolding component structure
  • →Wiring components to library APIs

About this skill

Add a SKY UX Component (end-to-end)

Use this skill to take a new component from scaffold to a fully wired, tested, and documented addition to a published @skyux/* library. It ties together the repo's scoped instruction files; read each referenced instruction file when you reach that step rather than guessing.

Read AGENTS.md first if you are not already familiar with the monorepo's conventions (Nx tasks, public API discipline, the sky/Sky export prefix, Karma vs. Jest split, and Conventional Commits).

When to Use

  • Adding a new component to an existing library under libs/components/<library>/.
  • Wiring a new public type/component into a library's src/index.ts barrel.

Do NOT use this skill to create a brand-new library/package — use the add-skyux-library skill first, then return here to add the suite's first component. Do not use this skill to modify build tooling.

Conventions at a Glance

  • Library source lives at libs/components/<library>/src/lib/modules/<module>/.
  • Component files follow the Angular style guide naming rule in AGENTS.md: <name>.ts, <name>.html, <name>.scss, and <name>.spec.ts, with a Sky<Name> class (e.g. SkyCode in libs/components/code/src/lib/modules/code/code.ts).
  • Do NOT create an NgModule for a new component. Consumers import the standalone component directly.
  • Components are standalone; do NOT set standalone: true explicitly in the decorator. OnPush is Angular's default change detection, so do NOT set changeDetection in the decorator either. Use input()/output() and signals. Follow angular.instructions.md.
  • Many existing components still use *.component.* file names, a Component class suffix, and an NgModule wrapper. That is a legacy pattern — do NOT copy it into new components.
  • The public API is the src/index.ts barrel. Public exports MUST be prefixed with sky/Sky (e.g. SkyThing, SkyThingHarness). Export the component by its own name (e.g. export { SkyThing } from './lib/modules/thing/thing';). Some existing libraries export older components under obscured aliases (e.g. as λ1); that is a legacy pattern — do NOT use it for new exports.

Procedure

Work top to bottom. Look up conventions in the most recently added equivalent component (e.g. SkyCode, SkyInputBoxButton) rather than an older sibling, which likely uses the legacy pattern described above.

  1. Confirm placement. Identify the target <library> (directory name, not package name) and the <module> folder. Inspect a sibling component in that library and copy its folder structure (not its legacy file naming or NgModule; see Conventions above). If the library does not exist yet, create it first with the add-skyux-library skill.
  2. Scaffold the component. Create <name>.ts, <name>.html, and <name>.scss following Angular best practices in angular.instructions.md.
  3. Export from the barrel. Add the component and any public types to libs/components/<library>/src/index.ts, using the sky/Sky prefix. Export a new component by its own name (not an obscured as λN alias).
  4. Write the component spec. Add <name>.spec.ts. Most libs/components/* projects enforce 100% coverage and run on Karma + Jasmine (SKY UX styles are loaded, so computed styles are assertable).
  5. Add a test harness. Create the harness, filters, and harness spec under libs/components/<library>/testing/src/modules/<module>/ per component-harnesses.instructions.md. Export the harness and filters from testing/src/public-api.ts.
  6. Add visual tests. Create a Storybook story for the component in the library's e2e app per the add-component-visual-tests skill.
  7. Add a code example + tests. Create an example under libs/components/code-examples/src/lib/modules/<library>/<component>/<example-name>/ and its example.spec.ts per the add-skyux-code-example skill.
  8. Update documentation. Add the new doc IDs to the library's documentation.json (development, testing, and codeExamples sections) so the manifest picks them up.
  9. Verify. Run the affected tests, lint, and format before committing:
    npx nx test <library> --configuration=ci
    npx nx test <library>-testing --configuration=ci
    npx nx test code-examples --configuration=ci
    npx nx build <library>-storybook
    npm run lint:affected
    nx format --files=<changed-file-paths>
    
  10. Commit. Use a Conventional Commit with the matching components/<library> scope per commit-message.instructions.md.

Definition of Done

  • Component, spec, harness (+ spec), visual-test story, and code example (+ spec) exist, with no NgModule, no type-suffixed file or class names, and no changeDetection in the decorator.
  • Public types are exported with the sky/Sky prefix from src/index.ts and testing/src/public-api.ts.
  • documentation.json lists the new development, testing, and code-example doc IDs.
  • Affected tests pass at the project's coverage threshold, lint is clean, and files are formatted.

When not to use it

  • →Creating new libraries

Limitations

  • →Requires existing library
  • →Requires manual verification of tests

How it compares

This enforces monorepo compliance and standardizes the component creation process compared to manual scaffolding.

Compared to similar skills

add-skyux-component side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
add-skyux-component (this skill)05moReviewIntermediate
svelte-expert111yNo flagsIntermediate
writing-registry-meta510moNo flagsBeginner
docs-demo35moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

svelte-expert

Raudbjorn

Expert Svelte/SvelteKit development assistant for building components, utilities, and applications. Use when creating Svelte components, SvelteKit applications, implementing reactive patterns, handling state management, working with stores, transitions, animations, or any Svelte/SvelteKit development task. Includes comprehensive documentation access, code validation with svelte-autofixer, and playground link generation.

11107

writing-registry-meta

siriwatknp

Use this skill when writing meta file for MUI Treasury registry.

587

docs-demo

remotion-dev

Add an interactive demo to the Remotion documentation. Use when creating a new <Demo> component for docs pages.

344

wot-ui

wot-ui

wot-ui uni-app 组件库开发指南。当用户询问 wot-ui 组件使用、配置、示例或 API 时使用此技能。

211

vitepress

antfu

VitePress static site generator powered by Vite and Vue. Use when building documentation sites, configuring themes, or writing Markdown with Vue components.

56

port-from-bslib

posit-dev

Comprehensive guide for porting UI components from R's bslib package to py-shiny. Use this skill when: (1) User asks to "port this feature" or "port a component" and mentions bslib or links to a bslib PR (e.g., github.com/rstudio/bslib/pull/...), (2) Porting a new component from bslib to py-shiny, (3) Adding a new input, output, or UI component that exists in bslib, (4) Implementing feature parity with bslib, (5) Working on bslib-related features or components. Covers the complete workflow including understanding source implementation, creating Python equivalents, vendoring assets (SCSS, CSS, JavaScript), creating tests, documentation, and all necessary project files.

17

Search skills

Search the agent skills registry