v9-component Skill
Scaffold a new v9 component with all required files following Fluent UI patterns (hook, styles, render, types, tests, stories, conformance) Published by microsoft in fluentui.
Decision snapshot
Is this a fit?
Testing, Documentation, Design and media, Includes SKILL.md
Compatibility not yet detected.
Can write or update data, Write actions, Filesystem access, Shell access
Copy skill directory
2 months ago · NOASSERTION license
Confirm write permissions and scope before use. Access note: Local files. Access note: Shell access.
What is v9-component Skill?
Scaffold a new v9 component with all required files following Fluent UI patterns (hook, styles, render, types, tests, stories, conformance) Published by microsoft in fluentui. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Documentation
- Design and media
- Testing use cases
- Documentation use cases
Declared skill metadata
- Source file: .agents/skills/v9-component/SKILL.md
Allowed tools declared by source
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
- Local files
- Shell access
Requirements and access
Security and permissions
Review permissions before connecting any MCP server to an agent. Pay special attention to whether it can read local files, write data, call external services, or perform destructive actions.
When to use v9-component Skill
- Use it for testing.
- Use it for documentation.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/fluentui
- Skill file: .agents/skills/v9-component/SKILL.md
What it does
Scaffold a new v9 component with all required files following Fluent UI patterns (hook, styles, render, types, tests, stories, conformance)
Skill instructions
Scaffold a V9 Component Create a new v9 component named $ARGUMENTS using the repo's Nx generators. Steps Adding a component to an existing package Use the react-component generator: bash yarn nx g @fluentui/workspace-plugin:react-component --name $ARGUMENTS --project <project-name Where <project-name is the Nx project (e.g., react-button). This generates all required files: component, types, hook, styles, render, index barrel, and conformance test. Creating a new package + component Use the react-library generator first, then add the component: bash Create the package (will prompt for owner team) yarn create-package Or non-interactively: yarn nx g @fluentui/workspace-plugin:react-library --name <package-name --owner "<team" Then add the component inside it: yarn nx g @fluentui/workspace-plugin:react-component --name $ARGUMENTS --project <package-name After scaffolding 1. Review generated files against docs/architecture/component-patterns.md and fill in component-specific logic. 2. Add
Verified compatibility and discovery
Frequently asked questions
What is v9-component?
v9-component is a open-source AI agent skill with Copy skill directory. Scaffold a new v9 component with all required files following Fluent UI patterns (hook, styles, render, types, tests, stories, conformance)
Who is v9-component best for?
v9-component is best for reusing agent instructions, scripts, and references, testing workflows, documentation workflows, design and media workflows.
How do I install v9-component?
Install or run v9-component using Copy skill directory. Check v9-component for the latest setup command.
Is v9-component actively maintained?
v9-component may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
