aiblueprint-cli 1.4.96 → 1.4.97

package/README.md

@@ -102,24 +102,8 @@ npx aiblueprint-cli@latest agents config unify sessions
 
 ### Workflow Skills
 
-**Development:**
-- `commit` - Fast conventional commits
-- `create-pr` - Auto-generated PRs
-- `fix-pr-comments` - Resolve PR comments
-- `merge` - Context-aware branch merging
-
-**Project setup:**
-- `nextjs-setup-project` - Scaffold the preferred Next.js stack
-- `nextjs-add-prisma-db` - Add Prisma and PostgreSQL
-- `nextjs-setup-better-auth` - Wire Better Auth with email OTP
-- `create-vitejs-app` - Create a Vite app with Tailwind and shadcn/ui
-
-**SaaS planning:**
-- `saas-create-prd` - Build a lean Product Requirements Document
-- `saas-create-architecture` - Design technical architecture
-- `saas-create-tasks` - Generate implementation tasks
-- `saas-define-pricing` - Create pricing strategy
-- `saas-find-domain-name` - Generate and validate domains
+The free configuration ships the skills listed in the catalog below. The CLI
+installs every directory under `agents-config/skills/`.
 
 ### Agents (3 Specialized)
 
@@ -154,24 +138,26 @@ npx skills add Melvynx/aiblueprint --skill skill-manager
 
 | Skill | Description |
 |-------|-------------|
+| `agents-manager` | Create and orchestrate Claude Code agents |
+| `apex` | Structured implementation workflow |
+| `app-icon` | Generate and prepare app icons |
+| `appstore-connect` | Manage App Store Connect workflows |
 | `commit` | Quick commit and push with clean messages |
 | `create-pr` | Auto-generated pull requests |
 | `fix-pr-comments` | Resolve PR review comments |
+| `grill-me` | Stress-test a plan with focused questions |
 | `merge` | Context-aware branch merging |
+| `environments-manager` | Set up per-worktree agent environments |
+| `oneshot` | Implement one focused change quickly |
+| `prompt` | Create minimalist SVG logo variations |
 | `prompt-creator` | Expert prompt engineering |
+| `rules-manager` | Create and maintain agent rule files |
 | `skill-manager` | Manage skills and rules across Claude Code, Codex, and Cursor |
-| `saas-create-prd` | Build a lean SaaS PRD |
-| `saas-create-architecture` | Design SaaS technical architecture |
-| `saas-create-tasks` | Generate implementation task files |
-| `nextjs-setup-project` | Set up a production-ready Next.js project |
-| `create-vitejs-app` | Create a Vite app with Tailwind and shadcn/ui |
+| `tools` | AIBlueprint tools and libraries reference |
 | `use-style` | Apply named UI style guides before implementation |
 | `use-artifacts` | Create polished local HTML plans, prototypes, and visualizations |
-| `rules-manager` | Create and maintain AGENTS.md and agent rule files |
-| `agents-managers` | Manage Claude Code agents and Task-tool orchestration |
-| `environments-manager` | Set up per-worktree agent environments |
-| `grill-me` | Stress-test a plan with focused design questions |
-| `oneshot` | Ultra-fast feature implementation |
+| `use-delegate` | Delegate heavy work to cheap executors |
+| `use-goal` | Create evidence-based agent goals |
 | `ultrathink` | Deep thinking mode for elegant solutions |
 
 ## 💎 Premium

package/agents-config/skills/app-icon/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: app-icon
-description: Generate a premium, vibrant, dimensional iOS + Android app icon for an Expo / React Native app with AI image generation, then post-process it to App Store / Play specs. Use for "create my app icon", "generate the iOS icon", "redo the app logo", "make the launcher icon". Works with ANY image-generation tool (Codex `image_gen`, `gemini-cli` Nano Banana, gpt-image, …).
+description: Generate a vibrant dimensional iOS and Android app icon for an Expo or React Native app with AI image generation, then post-process it for store specs. Use for creating, regenerating, or polishing an app logo or launcher icon.
 argument-hint: "[app concept or brand]"
 ---
 

package/agents-config/skills/use-artifacts/SKILL.md

@@ -9,7 +9,7 @@ description: Create Claude-style local HTML artifacts under global ~/.agents/art
 
 Use this skill to simulate Claude Artifacts in agents that do not have a native artifact panel. The artifact is a small global workspace, usually a single self-contained HTML file, created at `~/.agents/artifacts/<id>/` so the user can open, inspect, and iterate on it from any repo.
 
-Always create artifacts in the global user directory: `/Users/melvynx/.agents/artifacts/<id>/`. Never create artifacts inside a repo-local `.agents/artifacts` directory, even when the current working directory is a product repo.
+Always create artifacts in the global user directory: `~/.agents/artifacts/<id>/`. Never create artifacts inside a repo-local `.agents/artifacts` directory, even when the current working directory is a product repo.
 
 The HTML is the deliverable. It should turn the agent's public reasoning, plan, findings, examples, and tradeoffs into a polished page the user can scan, not just dump markdown into a file.
 
@@ -112,7 +112,7 @@ application style, a requested style, or the minimalist fallback.
 4. Scaffold the workspace:
 
 ```bash
-python3 /Users/melvynx/.agents/skills/use-artifacts/scripts/create_artifact.py "<short title>" --style "<requested, project:app-name, or fallback style>" --kind thinking
+python3 "$HOME/.agents/skills/use-artifacts/scripts/create_artifact.py" "<short title>" --style "<requested, project:app-name, or fallback style>" --kind thinking
 ```
 
 5. Implement the artifact in `index.html`.
@@ -132,7 +132,7 @@ Each artifact directory should contain:
 
 Target location:
 
-- Always use `/Users/melvynx/.agents/artifacts/<id>/`.
+- Always use `~/.agents/artifacts/<id>/`.
 - Do not use `<current-project>/.agents/artifacts/<id>/`.
 - Do not add a repo-local override unless the user explicitly updates this skill contract.
 

package/agents-config/skills/use-goal/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: use-goal
+description: Use when the user asks to create, draft, set, start, or refine a Codex or Claude Code /goal objective for persistent multi-turn work.
+---
+
+# Use Goal
+
+Create or draft a Codex or Claude Code Goal that follows the official `/goal` contract: one persistent objective with evidence-based completion criteria.
+
+## When To Use
+
+Use this skill when the user explicitly asks to:
+
+- create, set, start, or use a Goal
+- turn a task into a strong `/goal`
+- make Codex or Claude Code continue until an outcome is actually done
+- define success criteria for longer debugging, optimization, migration, refactor, benchmark, flaky-test, or research work
+
+Do not introduce a Goal for a one-off edit, short explanation, simple code review, or single answer unless the user explicitly asks for Goal mode.
+Do not use a Goal for a loose backlog or unrelated task list. A good Goal is bigger than one prompt but smaller than an open-ended project.
+
+## Pick The Platform
+
+Before drafting or creating a Goal, identify the active platform from the runtime and available tools:
+
+- **Codex**: use `references/codex-goal.md`.
+- **Claude Code**: use `references/claude-code-goal.md`.
+- **Unknown platform**: draft a plain `/goal ...` command and state that the user should run it in the target agent.
+
+If Goal tools are available in Codex, use them rather than only printing a slash command. If the runtime only exposes slash commands, return the exact `/goal ...` command unless the harness can dispatch it directly.
+
+## Goal Shape
+
+Before writing or creating the Goal, think through the verification strategy. Inspect repository docs, package scripts, tests, CI config, benchmark scripts, failing logs, linked issue text, plans, or referenced files when the evidence surface is not obvious.
+
+Identify which command, artifact, report, screenshot, benchmark, source document, or manual check can prove completion. Prefer existing project commands and documented workflows over invented validation. If no reliable verification surface exists, ask one concise question or make the Goal explicitly require creating one.
+
+Write one compact objective with the outcome, verification surface, constraints, boundaries, iteration policy, and blocked stop condition. For long-running implementation work, include the files to inspect first, exact proof commands, checkpoint behavior, and a short progress log requirement.
+
+Prefer this pattern:
+
+```text
+<desired end state>, verified by <specific evidence>, while preserving <constraints>. Use <allowed inputs, tools, or boundaries>. Between iterations, <how to choose and record the next best action>. If blocked or no valid paths remain, stop with <attempted paths, evidence gathered, blocker, and next input needed>.
+```
+
+## Create Or Draft
+
+When goal tools are available, check the current Goal first. Create a new one only when the user explicitly asks for it and no active Goal blocks it. Do not overwrite, clear, pause, or resume an existing Goal unless explicitly requested.
+
+If the user asks only to draft, rewrite, explain, or refine a Goal, return the final `/goal ...` text instead of activating it.
+
+## Evidence Rules
+
+Completion must be evidence-based. Do not mark a Goal complete because the work seems likely done, because a budget is exhausted, or because no more work is planned. Only mark it complete after verifying the stated stopping condition. If blocked, report the attempted paths, evidence gathered, blocker, and exact input or external change needed.
+
+## References
+
+- `references/codex-goal.md`: Codex Goal mode, tools, lifecycle, and completion rules.
+- `references/claude-code-goal.md`: Claude Code `/goal` command, evaluator, and manual activation.
+- `references/verification-harnesses.md`: measurable validation for refactors, deletions, migrations, and moves.

package/agents-config/skills/use-goal/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "Use Goal"
+  short_description: "Create evidence-based Codex or Claude Code goals"
+  icon_small: "./assets/codex-icon.svg"
+  icon_large: "./assets/codex-icon.svg"
+  brand_color: "#C70A64"
+  default_prompt: "Use $use-goal to help with this task."

package/agents-config/skills/use-goal/assets/codex-icon.svg

@@ -0,0 +1,4 @@
+<svg role="img" aria-label="use-goal skill icon" width="64" height="64" viewBox="0 0 64 64" xmlns="http://www.w3.org/2000/svg">
+  <rect width="64" height="64" rx="16" fill="#C70A64"/>
+  <path d="M20 20h24v6H26v8h14v6H26v4h18v6H20V20Z" fill="#fff"/>
+</svg>

package/agents-config/skills/use-goal/references/claude-code-goal.md

@@ -0,0 +1,17 @@
+# Claude Code Goal Reference
+
+Use this reference when the active agent is Claude Code.
+
+Official reference: https://code.claude.com/docs/en/goal
+
+Claude Code uses `/goal` to set a completion condition for the current session. `/goal <condition>` starts Goal mode, `/goal` shows its state, and `/goal clear` removes it. Only one Goal can be active per session.
+
+The condition must describe one measurable end state and the proof Claude must surface in the transcript. Include constraints, the files or logs to inspect first, checkpoint reporting, and a bounded blocked stop clause when useful. Goal conditions can be up to 4,000 characters.
+
+If the harness cannot dispatch slash commands, output the exact `/goal ...` command and ask the user to paste it manually. Do not replace it with a task list or call `/goal` Claude-only.
+
+Prefer:
+
+```text
+/goal <desired end state>, verified by <proof surfaced in the transcript>, while preserving <constraints>. First inspect <files/docs/logs>. After each turn, report the checkpoint, command result, remaining gap, and next smallest step. Stop when the proof is present, or after <bound> with attempted paths, evidence, blocker, and needed input.
+```

package/agents-config/skills/use-goal/references/codex-goal.md

@@ -0,0 +1,15 @@
+# Codex Goal Reference
+
+Use this reference when the active agent is OpenAI Codex.
+
+Official references:
+
+- https://developers.openai.com/codex/use-cases/follow-goals
+- https://developers.openai.com/codex/app/commands
+- https://developers.openai.com/codex/cli/slash-commands
+
+`/goal <objective>` starts Goal mode. `/goal` views the current Goal. `/goal pause`, `/goal resume`, and `/goal clear` manage lifecycle. Objectives must be non-empty and at most 4,000 characters.
+
+When Goal tools are available, call `get_goal` before lifecycle actions and create a new Goal only when the user explicitly asks and no active Goal exists. Do not overwrite an existing Goal without explicit permission. If Goals are unavailable, tell the user to enable `[features] goals = true` or run `codex features enable goals`.
+
+A strong Goal defines one objective and stopping condition, initial files/docs, exact proof commands or artifacts, non-regression constraints, checkpoint behavior, and the evidence to report if blocked.

package/agents-config/skills/use-goal/references/verification-harnesses.md

@@ -0,0 +1,7 @@
+# Verification Harnesses For Refactors
+
+Use this reference when a Goal involves refactoring, deletion, migration, moving files, eliminating a pattern, or reducing a code smell.
+
+Convert the desired end state into a deterministic count, list, or command result. First establish the baseline before editing. Prefer existing repository tooling; otherwise create a narrow, deterministic checker that prints grouped findings and exits non-zero while work remains. Exclude generated, vendored, build, lockfile, snapshot, and binary content unless the task includes it.
+
+For deletion or migration Goals, verify both the old surface is gone and the new surface works: no imports, string references, routes, config entries, or tests should point at removed paths, and typecheck/build/test should pass. Rerun the harness after each change and report the delta.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aiblueprint-cli",
-  "version": "1.4.96",
+  "version": "1.4.97",
   "description": "AIBlueprint CLI for setting up AI coding configurations",
   "author": "AIBlueprint",
   "license": "MIT",