@ryuenn3123/agentic-senior-core 3.0.8 → 3.0.9

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

@@ -10,10 +10,12 @@ This contract is a structure and reasoning system, not a fixed visual template.
 The agent must:
 1. Read [AGENTS.md](../../AGENTS.md) for project context and team roles.
 2. Scan all files in [.agent-context/rules/](../rules/) for UI/UX and accessibility standards.
-3. Reference [docs/deep-dive.md](../../docs/deep-dive.md) and [docs/faq.md](../../docs/faq.md) for architecture and product background.
+3. Use repository evidence from [.agent-context/state/onboarding-report.json](../state/onboarding-report.json), existing UI code, product copy, route names, component names, and any existing `docs/*` project docs to infer architecture and product background.
 4. If [docs/DESIGN.md](../../docs/DESIGN.md) or `docs/design-intent.json` already exists, check for drift and improve them instead of rewriting blindly.
-5. Treat any example structure or stylistic inspiration as non-normative. Use it only to judge depth and clarity, never to copy a visual language directly.
-6. All references to docs or rules must be clickable markdown links.
+5. If context is incomplete, write explicit assumptions and reversible design bets instead of defaulting to generic SaaS output.
+6. Explore multiple plausible design directions internally, then commit to one cohesive direction with clear rationale tied to the product context.
+7. Treat any example structure or stylistic inspiration as non-normative. Use it only to judge depth and clarity, never to copy a visual language directly.
+8. All references to docs or rules must be clickable markdown links.
 
 Required `docs/DESIGN.md` sections:
 1. Design Intent and Product Personality
@@ -44,5 +46,5 @@ Required `docs/design-intent.json` fields:
 Output:
 - Create or update both `docs/DESIGN.md` and `docs/design-intent.json`.
 - Keep both files synchronized: the markdown explains the why, the JSON captures the contract in machine-readable form.
-- Use practical, modern, accessible language grounded in the project, not generic SaaS defaults.
+- Use practical, modern, accessible language grounded in the project, not generic SaaS defaults or copycat brand systems.
 - Wait for user approval before generating Figma or code assets.

package/.agent-context/prompts/init-project.md

@@ -6,7 +6,7 @@ This prompt boots a repository with strict rules operations context (Federated G
 When a new project is created or initialized, the agent should automatically:
 1. Read [AGENTS.md](../../AGENTS.md) to understand available roles and knowledge base.
 2. Scan all files in [.agent-context/rules/](../rules/) for mandatory engineering standards.
-3. Review dynamic stack and architecture signals from [docs/deep-dive.md](../../docs/deep-dive.md), [docs/faq.md](../../docs/faq.md), and task constraints.
+3. Review dynamic stack and architecture signals from [.agent-context/state/onboarding-report.json](../state/onboarding-report.json), [.agent-context/state/stack-research-snapshot.json](../state/stack-research-snapshot.json), available stack and blueprint sources, and task constraints.
 
 ## Architect Mode (Recommended)
 If the user describes a project or feature, the agent should:
@@ -19,7 +19,7 @@ If the user describes a project or feature, the agent should:
 If the user specifies a framework/blueprint, the agent should:
 1. Read [AGENTS.md](../../AGENTS.md) for role context.
 2. Scan all files in [.agent-context/rules/](../rules/) for engineering standards.
-3. Reference [docs/deep-dive.md](../../docs/deep-dive.md) and [docs/faq.md](../../docs/faq.md) for stack/blueprint guidance.
+3. Reference [.agent-context/state/onboarding-report.json](../state/onboarding-report.json), [.cursorrules](../../.cursorrules), and [.windsurfrules](../../.windsurfrules) for the active stack and blueprint guidance already applied to this project.
 4. Scaffold the initial project structure following the blueprint exactly:
 	- Create all directories and files from the blueprint
 	- Set up environment config and validation (e.g., Zod, Pydantic, FluentValidation)
@@ -32,7 +32,7 @@ If the user specifies a framework/blueprint, the agent should:
 	- Every dependency must be justified per [efficiency-vs-hype.md](../rules/efficiency-vs-hype.md)
 
 ## Stacks & Blueprints Reference
-See [docs/roadmap.md](../../docs/roadmap.md) and [docs/deep-dive.md](../../docs/deep-dive.md) for the latest stack and blueprint list.
+See [.agent-context/state/onboarding-report.json](../state/onboarding-report.json), [.cursorrules](../../.cursorrules), and [.windsurfrules](../../.windsurfrules) for the latest shipped stack and blueprint context.
 
 ## UI/UX Bootstrap
 When a user requests frontend or UI/UX design, the agent should automatically execute the [bootstrap-design.md](./bootstrap-design.md) prompt to synthesize a dynamic design contract (`docs/DESIGN.md` + `docs/design-intent.json`).
@@ -93,7 +93,7 @@ Every dependency must be justified per [efficiency-vs-hype.md](../rules/efficien
 
 ## Stacks & Blueprints Reference
 
-See [docs/roadmap.md](../../docs/roadmap.md) and [docs/deep-dive.md](../../docs/deep-dive.md) for the latest stack and blueprint list.
+See [.agent-context/state/onboarding-report.json](../state/onboarding-report.json), [.cursorrules](../../.cursorrules), and [.windsurfrules](../../.windsurfrules) for the latest shipped stack and blueprint context.
 
 ---
 

package/.agent-context/state/memory-continuity-benchmark.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-04-20T01:05:14.547Z",
+  "generatedAt": "2026-04-20T02:01:47.871Z",
   "reportName": "memory-continuity-benchmark",
   "schemaVersion": "1.0.0",
   "passed": true,

package/.cursorrules

@@ -1,6 +1,6 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v3.0.8
+Generated by Agentic-Senior-Core CLI v3.0.9
 Timestamp: 2026-04-18T00:00:00.000Z
 Selected profile: beginner
 Selected policy file: .agent-context/policies/llm-judge-threshold.json

package/.windsurfrules

@@ -1,6 +1,6 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v3.0.8
+Generated by Agentic-Senior-Core CLI v3.0.9
 Timestamp: 2026-04-18T00:00:00.000Z
 Selected profile: beginner
 Selected policy file: .agent-context/policies/llm-judge-threshold.json

package/README.md

@@ -10,12 +10,12 @@
 **Production-grade Rules Engine (Governance Engine) for AI coding agents.**
 Works with Cursor, Windsurf, GitHub Copilot, Claude Code, Gemini, and other LLM-powered IDE workflows.
 
-Latest release: 3.0.8 (2026-04-20).
+Latest release: 3.0.9 (2026-04-20).
 
-Highlights in 3.0.8:
-- Existing UI repositories now get `docs/design-intent.json` seeded during both `init` and `upgrade`.
-- Upgrade preview explicitly shows when a machine-readable design seed will be created on apply.
-- UI scope detection is now shared between `init` and `upgrade` so design-contract enforcement stays consistent.
+Highlights in 3.0.9:
+- Design bootstrap prompts now rely on shipped project evidence instead of assuming extra docs exist in every initialized repository.
+- Dynamic UI design guidance now emphasizes structure, rationale, and anti-generic constraints without anchoring to example brand systems.
+- Init prompts now point agents at the active onboarding and compiled-rule context that actually exists in target projects.
 
 </div>
 

package/package.json

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