@aurodesignsystem-dev/auro-cli 0.0.0-pr302.0 → 0.0.0-pr310.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -159,75 +159,3 @@ Reads the repo's commits, classifies each by conventional-commit type, and repor
159
159
  - `-l, --set-label`: label the PR by the highest-priority commit type.
160
160
  - `-d, --debug`: print detailed commit info.
161
161
  - `-r, --release-notes`: generate release notes from the commits.
162
-
163
- ### AI assistant context
164
-
165
- #### `auro context`
166
-
167
- Prints an AI-ready context document describing the Auro Design System, its components, and usage patterns. Designed to be piped into or pasted into AI coding assistants (Claude, Cursor, Copilot, etc.) to prime them on Auro.
168
-
169
- - `-o, --output <file>`: write the context document to a file instead of stdout (e.g. `AURO_CONTEXT.md`).
170
-
171
- Print the context to the terminal:
172
-
173
- ```bash
174
- auro context
175
- ```
176
-
177
- Write the context to a file for your AI tool:
178
-
179
- ```bash
180
- auro context --output AURO_CONTEXT.md
181
- ```
182
-
183
- `auro cem`
184
- Aggregates the Custom Elements Manifests (`custom-elements.json`) of every published Auro component into a single file. Each component's manifest is fetched from the latest published version on unpkg; components that do not publish a manifest yet are skipped. Useful for feeding a complete, machine-readable component API index to IDEs, docs tooling, and AI assistants.
185
-
186
- #### Options
187
-
188
- - `-o, --output <file>` Path to write the aggregated manifest (default: `custom-elements.aggregate.json`).
189
-
190
- #### Examples
191
-
192
- Generate the aggregated manifest:
193
-
194
- ```
195
- auro cem
196
- ```
197
-
198
- Write it to a specific path:
199
-
200
- ```
201
- auro cem --output dist/custom-elements.aggregate.json
202
- ```
203
-
204
- `auro component <name>`
205
- Looks up a single Auro component's API — attributes, properties/methods, slots, events, and CSS parts — from its published Custom Elements Manifest. Useful for humans and for AI coding assistants that call the CLI in a tool-use loop to avoid guessing an API.
206
-
207
- #### Options
208
-
209
- - `-t, --tag <version>` npm dist-tag or version to look up (default: `latest`).
210
- - `--json` Output the raw manifest declaration(s) as JSON instead of formatted text.
211
-
212
- #### Examples
213
-
214
- Look up a component (name is normalized, so all of these work):
215
-
216
- ```
217
- auro component button
218
- auro component auro-button
219
- auro component @aurodesignsystem/auro-button
220
- ```
221
-
222
- Look up a specific version or dist-tag:
223
-
224
- ```
225
- auro component auro-button --tag beta
226
- auro component auro-button --tag 11.0.0
227
- ```
228
-
229
- Get machine-readable output:
230
-
231
- ```
232
- auro component auro-button --json
233
- ```