@ryuenn3123/agentic-senior-core 4.3.11 → 4.3.14

package/.agent-context/prompts/bootstrap-design.md

@@ -10,25 +10,10 @@ Use this prompt for UI, UX, frontend layout, screen, or redesign work. Create or
 - When generating any UI component that renders or accepts user data, explicitly state in the prompt: "ensure all user-supplied input is sanitized, all status indicators have non-color alternatives, and all interactive elements have visible focus states."
 - Before choosing a new UI library, research current official docs.
 
-## Design Reference Retrieval
-
-Before generating tokens from scratch, check if a proven brand reference matches
-the product aesthetic. Run `npx -y getdesign list` to see all available references.
-Pick by spatial mechanics and typographic character, not by color.
-
-Fetch: `npx -y getdesign add <slug> --out docs/DESIGN.md --force`
-
-Customize: replace brand colors with product OKLCH equivalents, replace brand name
-with product name, remove brand iconography, keep spatial rhythm and density logic.
-
-If no brand matches or terminal is unavailable, skip and generate from scratch below.
-
-Source: https://github.com/VoltAgent/awesome-design-md
-
 ## Design Direction Process
 
 1. **Name Your Defaults**: Name three temptations (e.g. SaaS admin default, AI-startup landing) and why they flatten this product. Derive your search direction by rejecting them.
-2. **Choose an Anchor**: Pick a specific real-world reference whose mechanics translate here. Do not use generic quality words ("clean", "modern").
+2. **Choose an Anchor**: Run `npx -y getdesign@latest list` to browse proven brand references. Pick one whose spatial rhythm fits this product. Run `npx -y getdesign@latest add <brand>` to read the full reference — use it to derive token values, then discard it. Output DESIGN.md stays under 400 tokens. Do not use generic quality words ("clean", "modern").
 3. **Creative Commitments**: Choose distinctive typography, dominant colors with sharp accents, and one signature motion behavior. Create depth rather than flat card stacks.
 4. **Previous Directions**: If `docs/DESIGN.md` contains previous directions, treat them as a blocklist. The new anchor must differ in conceptual family, hierarchy, and motion.
 
@@ -38,7 +23,7 @@ When the user says "redesign from zero": treat existing UI as behavioral evidenc
 
 ## Output Format
 
-`docs/DESIGN.md` must be a compact token file under 400 tokens (exception: if using a fetched brand reference from `getdesign`, you may preserve its rich details up to 2500 tokens). Rationale stays in working memory.
+`docs/DESIGN.md` must be a compact token file under 400 tokens. Rationale stays in working memory.
 
 Required sections (in this order, no additions):
 

package/AGENTS.md

@@ -17,18 +17,19 @@ Write instructions as imperative gates:
 - Move detailed policy into `.agent-context/`.
 - Add validation when a rule can drift.
 
-## Bootstrap Receipt
-For non-trivial work, run `agentic-senior-core context "<task_description>"` (or `npx @ryuenn3123/agentic-senior-core context "<task_description>"`) and emit a concise Bootstrap Receipt before implementation output or file edits:
+## MANDATORY FIRST STEP: Context Activation
+STOP. Before generating ANY plan, code, or design for a non-trivial task, you MUST run `agentic-senior-core context "<task_description>"` (or `npx @ryuenn3123/agentic-senior-core context "<task_description>"`) to resolve scopes. Do not guess or hallucinate context.
+
+Immediately emit a concise Bootstrap Receipt:
 - `loaded_files`: files actually read (exact paths from selectedRules/selectedPrompts only; zero hallucination)
 - `selected_rules`: files selected for this scope and why
 - `skipped_rules`: out-of-scope categories left unloaded
 - `unreachable_files`: required files that could not be read
 - `validation_plan`: expected checks before completion
 
-Keep it short. Do not load every rule just to fill it out.
+Skip this step ONLY for trivial tasks (version bumps, typo fixes).
 
-## Default Activation And Command Economy
-Before any non-trivial task, run `agentic-senior-core context "<task_description>"` and emit the Bootstrap Receipt. Skip only for trivial tasks: version bumps, typo fixes, single-line commits.
+## Command Economy
 Always prefix noisy shell commands: `ascx git status`, `ascx git diff`, `ascx npm test`, `ascx npm install`, `ascx npm run build`, `ascx tsc`, `ascx rg` searches. Use raw commands only for pipes, redirects, or commands not supported by ascx.
 Always read and apply `.agent-context/prompts/compact-natural-mode.md` for every final user-facing reply. Never repeat full command output; reference tee file paths when truncated.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ryuenn3123/agentic-senior-core",
-  "version": "4.3.11",
+  "version": "4.3.14",
   "type": "module",
   "description": "Change your AI Agent to code like a Staff Engineer, not a Junior.",
   "bin": {