How do I install the Flutter Shadcn CLI skill?

Run npx skillmds@latest add tomevault-io/flutter-shadcn-cli in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Flutter Shadcn CLI safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Flutter Shadcn CLI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Flutter Shadcn CLI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Flutter Shadcn CLI?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Flutter Shadcn CLI by tomevault-io — Agent Skill

Name: Flutter Shadcn CLI
Author: tomevault-io

Flutter Shadcn CLI

Use when maintaining, testing, documenting, or automating the flutter_shadcn CLI, multi-registry resolution, inline init actions, diagnostics, skill installation, or pub.dev packaging behavior.

tomevault-io 1cfd2f8 2 files · 4.0 KB Updated Sep 17, 2026

File contents

Flutter shadcn CLI

flutter_shadcn is the installer and maintenance CLI for Flutter shadcn registries. Treat CLI commands, tests, docs, and registry schemas as one product surface.

Start Here

Run from the CLI repo root before changing behavior:

dart pub get
dart run bin/flutter_shadcn.dart --help
dart test

For architecture questions, read graphify-out/GRAPH_REPORT.md first. Use graphify query, graphify path, or graphify explain for cross-module relationships. After modifying code, run graphify update ..

Non-Negotiables

Do not guess flags. Check dart run bin/flutter_shadcn.dart --help and command help.
Preserve single-registry compatibility while changing multi-registry behavior.
Keep namespace behavior deterministic: prefer @namespace/component in scripts, docs, tests, and AI output.
Preview installs with dry-run --json before non-trivial add operations.
Never bypass path safety in init actions. Reject traversal and writes outside the project.
Keep docs, generated command metadata, tests, and behavior in sync.
Ship AI skills with the packaged CLI under registry/skills so pub.dev users can install them.

Core Workflows

Maintain CLI Behavior

Read the existing command implementation in lib/src/presentation/cli/commands/.
Read lower-level services in lib/src/application, lib/src/infrastructure, and compatibility exports in lib/src/*.dart.
Write or update a focused test in test/ before implementation.
Run the specific test, then the relevant command manually with dart run bin/flutter_shadcn.dart.
Update docs/user/, docs/developer/, and lib/src/presentation/cli/command_metadata.dart when public behavior changes.

Validate A Registry-Aware Change

dart test test/resolver_v1_test.dart
dart test test/multi_registry_manager_test.dart
dart test test/e2e_multi_registry_fixture_test.dart
dart run bin/flutter_shadcn.dart registries --json
dart run bin/flutter_shadcn.dart doctor --json

Validate Skill Installer Changes

dart test test/skill_manager_test.dart
dart run bin/flutter_shadcn.dart --advanced install-skill --available
dart run bin/flutter_shadcn.dart --advanced install-skill --skill flutter-shadcn-cli --model .codex
dart run bin/flutter_shadcn.dart --advanced install-skill --skill flutter-shadcn-ui --model .codex

Command Map

Use references/commands.md for public commands, advanced flags, and machine-readable outputs.

Architecture Map

Use references/architecture.md for resolver, config/state, init actions, installer, diagnostics, docs, and skill packaging responsibilities.

Test Discipline

Use references/testing.md for targeted tests and expected coverage by change type.

Skill Packaging

Use references/skills-packaging.md before editing registry/skills, install-skill, SkillsLoader, or SkillManager.

Source: mibrar-dev/flutter_shadcn_cli — distributed by TomeVault.

---name: flutter-shadcn-clidescription: Use when maintaining, testing, documenting, or automating the flutter_shadcn CLI, multi-registry resolution, inline init actions, diagnostics, skill installation, or pub.dev packaging behavior.---# Flutter shadcn CLI`flutter_shadcn` is the installer and maintenance CLI for Flutter shadcn registries. Treat CLI commands, tests, docs, and registry schemas as one product surface.## Start HereRun from the CLI repo root before changing behavior:```bashdart pub getdart run bin/flutter_shadcn.dart --helpdart test```For architecture questions, read `graphify-out/GRAPH_REPORT.md` first. Use `graphify query`, `graphify path`, or `graphify explain` for cross-module relationships. After modifying code, run `graphify update .`.## Non-Negotiables- Do not guess flags. Check `dart run bin/flutter_shadcn.dart --help` and command help.- Preserve single-registry compatibility while changing multi-registry behavior.- Keep namespace behavior deterministic: prefer `@namespace/component` in scripts, docs, tests, and AI output.- Preview installs with `dry-run --json` before non-trivial `add` operations.- Never bypass path safety in init actions. Reject traversal and writes outside the project.- Keep docs, generated command metadata, tests, and behavior in sync.- Ship AI skills with the packaged CLI under `registry/skills` so pub.dev users can install them.## Core Workflows### Maintain CLI Behavior1. Read the existing command implementation in `lib/src/presentation/cli/commands/`.2. Read lower-level services in `lib/src/application`, `lib/src/infrastructure`, and compatibility exports in `lib/src/*.dart`.3. Write or update a focused test in `test/` before implementation.4. Run the specific test, then the relevant command manually with `dart run bin/flutter_shadcn.dart`.5. Update `docs/user/`, `docs/developer/`, and `lib/src/presentation/cli/command_metadata.dart` when public behavior changes.### Validate A Registry-Aware Change```bashdart test test/resolver_v1_test.dartdart test test/multi_registry_manager_test.dartdart test test/e2e_multi_registry_fixture_test.dartdart run bin/flutter_shadcn.dart registries --jsondart run bin/flutter_shadcn.dart doctor --json```### Validate Skill Installer Changes```bashdart test test/skill_manager_test.dartdart run bin/flutter_shadcn.dart --advanced install-skill --availabledart run bin/flutter_shadcn.dart --advanced install-skill --skill flutter-shadcn-cli --model .codexdart run bin/flutter_shadcn.dart --advanced install-skill --skill flutter-shadcn-ui --model .codex```## Command MapUse [references/commands.md](references/commands.md) for public commands, advanced flags, and machine-readable outputs.## Architecture MapUse [references/architecture.md](references/architecture.md) for resolver, config/state, init actions, installer, diagnostics, docs, and skill packaging responsibilities.## Test DisciplineUse [references/testing.md](references/testing.md) for targeted tests and expected coverage by change type.## Skill PackagingUse [references/skills-packaging.md](references/skills-packaging.md) before editing `registry/skills`, `install-skill`, `SkillsLoader`, or `SkillManager`.---> Source: [mibrar-dev/flutter_shadcn_cli](https://github.com/mibrar-dev/flutter_shadcn_cli) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions