@maccesar/aiskills 1.17.0 → 1.17.1

package/README.md

@@ -2,9 +2,7 @@
 
 <div align="center">
 
-![npm](https://img.shields.io/npm/dm/aiskills)
-![npm](https://img.shields.io/npm/v/aiskills)
-![NPM](https://img.shields.io/npm/l/aiskills)
+![npm](https://img.shields.io/npm/dm/aiskills) ![npm](https://img.shields.io/npm/v/aiskills) ![NPM](https://img.shields.io/npm/l/aiskills)
 
 </div>
 

package/commands/release.md

@@ -102,8 +102,7 @@ Do all of this **internally**. Do not print a status summary or any "Step 1" hea
    - Screenshots in repo root (`*.png`, `*.jpg`, `*.jpeg`, `Screenshot*.png`, `Captura*.png`) unless they live inside an `assets/`, `docs/`, or similarly-blessed directory.
    - Editor scratch files: `*.swp`, `*.tmp`, `.DS_Store`, `Thumbs.db`.
    - Local-only env files: `.env`, `.env.local`, `*.local.json` if the project's `.gitignore` already excludes them but they appear because of `git add -A`.
-   - Credentials, secret keys, large binaries that look unrelated to the project.
-   When in doubt, **list the file in the Step 4 plan as "excluded — confirm?"** instead of silently dropping or silently including it.
+   - Credentials, secret keys, large binaries that look unrelated to the project. When in doubt, **list the file in the Step 4 plan as "excluded — confirm?"** instead of silently dropping or silently including it.
 
    **Output of this step (held internally for Step 4):** an ordered list `[ {type, scope, subject, files[], body?}, ... ]` representing the N semantic commits, plus an "excluded" list.
 
@@ -344,8 +343,7 @@ After Phase 1, the working tree should be clean except for files explicitly list
 
 3. **Update `README.md`** with everything identified in Step 1.6:
    - The documentation gap patches (new command rows, new sections, updated tables) so the README reflects the user-visible surface being shipped in this release.
-   - Plus any version badge / install snippet that referenced the old version.
-   Apply with `Edit` per location. Skip only if Step 1.6 found nothing.
+   - Plus any version badge / install snippet that referenced the old version. Apply with `Edit` per location. Skip only if Step 1.6 found nothing.
 
 4. **Stage exactly the release-commit files** (the bumped version file + lockfile if `npm version` updated it + `CHANGELOG.md` + `README.md` if changed). Use explicit `git add <paths>`, not `git add -A`.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maccesar/aiskills",
-  "version": "1.17.0",
+  "version": "1.17.1",
   "description": "AI coding assistant skills for Claude Code, Gemini CLI, and Codex CLI",
   "type": "module",
   "bin": {

package/skills/refactoring-ui/SKILL.md

@@ -9,9 +9,7 @@ Design advice grounded in the principles taught by Adam Wathan & Steve Schoger i
 
 ## Required workflow (read before responding)
 
-The SKILL.md alone is an **index** of references. The detail you need
-to give accurate answers lives in the reference files. **Reading this
-SKILL.md is not enough.**
+The SKILL.md alone is an **index** of references. The detail you need to give accurate answers lives in the reference files. **Reading this SKILL.md is not enough.**
 
 ### Step 1 — Open the relevant reference files
 
@@ -27,8 +25,7 @@ SKILL.md is not enough.**
 
 ### Step 2 — Output contract
 
-Every design recommendation, ratio, value, or rule you cite MUST be
-backed by a citation in the form:
+Every design recommendation, ratio, value, or rule you cite MUST be backed by a citation in the form:
 
 `[source: references/<file>.md]`
 
@@ -36,8 +33,7 @@ Example: *"Use weight and color, not just font size, to establish hierarchy [sou
 
 ### Step 3 — If you must answer from memory
 
-If you write a claim without having read the reference that backs it,
-prepend `FROM_MEMORY (unverified):` to that claim. Do not hide it.
+If you write a claim without having read the reference that backs it, prepend `FROM_MEMORY (unverified):` to that claim. Do not hide it.
 
 ### Banned behaviors