@ryuenn3123/agentic-senior-core 4.3.6 → 4.3.8

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

@@ -7,56 +7,46 @@ Use this prompt for UI, UX, frontend layout, screen, or redesign work. Create or
 - Use current repo evidence, project docs, and `.agent-context/` as style context.
 - Do not copy layout rhythm, palette, component skin, or brand posture from external references without explicit user approval.
 - WCAG 2.2 AA is the hard compliance floor.
-- Before choosing a new UI library, research current official docs. Do not default to any component kit or styling tool by habit, and do not avoid them when they fit.
+- Before choosing a new UI library, research current official docs.
 
-## Step 1: Name Your Defaults
+## Design Direction Process
 
-Before any visual choice, name three design directions you are most tempted to use for this project. For each:
-1. Name the specific visual pattern (layout, palette, density, motion, typography).
-2. Argue against it: why would it flatten what is specific about THIS product's core purpose and data shape?
-3. Derive your search direction from the rejection argument.
+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").
+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.
 
-## Step 2: Choose an Anchor
-
-Pick one concrete, googleable real-world reference whose interaction mechanics (not surface styling) translate to this UI. The anchor must be specific enough that renaming the product to a different category breaks coherence.
-
-Hard constraints:
-- Reject generic quality words as anchors: "modern", "clean", "premium", "minimal", "bold" are not anchors.
-- Do not default to spatial place metaphors (room, studio, lab, cockpit, command center). Prefer artifacts, workflows, instruments, data behaviors, or interaction mechanisms.
-- Record what mechanic is borrowed and what is explicitly NOT borrowed (palette, component skin, layout rhythm).
-
-## Step 3: Creative Commitments
-
-Record before coding:
-1. **Typography**: Choose distinctive fonts with meaningful role contrast. Avoid Inter, Roboto, Arial, Space Grotesk, system fonts.
-2. **Color and palette**: Dominant colors with sharp accents. Name what product evidence makes the palette fit. Name one color behavior that would not transfer to another category.
-3. **Motion and interaction**: Define one signature motion behavior more specific than "smooth." One well-orchestrated page load with staggered reveals creates more delight than scattered micro-interactions.
-4. **Composition**: One composition choice that avoids interchangeable card stacks. Create atmosphere and depth rather than solid backgrounds.
-
-## Previous Directions (do not repeat)
+## Redesign Protocol
 
-If `docs/DESIGN.md` contains a list of previous directions, treat every entry as a blocklist. The chosen anchor must differ from every blocklisted entry on conceptual family, hierarchy, and motion. Restating an existing direction with new wording is not a new direction.
+When the user says "redesign from zero": treat existing UI as behavioral evidence only. Rewrite design docs. Change primary composition, hierarchy, interaction model, and responsive architecture. Do not ship a palette swap.
 
-## Named Defaults to Avoid
+## Output Format
 
-- `dev-tool default`: condensed tabular numerics, monospace on dark slate, monochrome status dots, minimal chrome
-- `AI-startup landing default`: purple-to-pink gradient hero, floating glass cards, three-up feature grid, vague hero copy
-- `SaaS admin default`: left-side icon-only nav, top utility bar, three-card KPI row above data table, neutral grey
-- `marketing site default`: hero image with headline, three feature tiles, pricing tiers, testimonial carousel
+`docs/DESIGN.md` must be a compact token file under 400 tokens. Rationale stays in working memory.
 
-Avoid: purple gradients on white, predictable centered-everything composition, solid-color backgrounds without depth, cookie-cutter component patterns. Never converge on common choices across generations.
+Required sections (in this order, no additions):
 
-## Post-Implementation Check
+### Anchor
+One sentence: the interaction anchor and what mechanic is borrowed.
 
-After generating UI code, answer:
-1. If the product name were removed, would a designer identify what specific product this was built for? If no, revise the concept.
-2. Does the primary viewport avoid the centered-everything default? If no, name the product reason or revise.
-3. Name the one default you were most tempted to use. Confirm it was rejected with a product-specific reason.
+### Tokens
+- **Typography**: font families (display, body, mono), scale base and ratio, scale method
+- **Colors**: OKLCH primitives with semantic role mapping (primary, secondary, surface, error, success)
+- **Spacing**: base unit, scale
+- **Radius**: small, medium, large values
+- **Shadow**: elevation levels
+- **Motion**: duration, easing, reduced-motion fallback
 
-## Redesign Protocol
+### Constraints
+- WCAG 2.2 AA floor
+- Up to 3 product-specific anti-patterns
 
-When the user says "redesign from zero" or equivalent: treat existing UI as behavioral evidence only. Rewrite design docs. Change primary composition, hierarchy, interaction model, and responsive architecture. Do not ship a palette swap or same hero with new colors.
+### Previous Directions
+Anchors used in prior iterations (blocklist for redesign). Start empty for fresh projects.
 
-## Required Docs
+## Required Validation Gates
 
-Generate or refine `docs/DESIGN.md` (human-readable design direction) and `docs/design-intent.json` (machine-readable intent with `conceptualAnchor`, creative commitments, and anti-repeat ledger) before UI implementation.
+Only three gates. Do not add more:
+1. Anchor exists and is specific.
+2. Token values are derived from the anchor.
+3. WCAG 2.2 AA compliance floor is met.

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

@@ -26,7 +26,7 @@ If the user describes a project or feature, the agent must:
 If the user asks to create, complete, fix, or review project docs, documentation, dokumen, `docs/*`, architecture docs, flow docs, API docs, or "lengkapkan docs", treat the request as documentation-first.
 
 The agent must:
-1. Materialize or refine required project docs before implementation: root `README.md` for every fresh or existing project; `docs/doc-index.md` whenever `docs/` exists; `docs/project-brief.md`; `docs/architecture-decision-record.md`; `docs/flow-overview.md`; `docs/api-contract.md` when APIs, firmware endpoints, CLI commands, or web application flows exist; `docs/database-schema.md` when persistent data exists; and `docs/DESIGN.md` plus `docs/design-intent.json` for UI scope.
+1. Materialize or refine required project docs before implementation: root `README.md` for every fresh or existing project; `docs/doc-index.md` whenever `docs/` exists; `docs/project-brief.md`; `docs/architecture-decision-record.md`; `docs/flow-overview.md`; `docs/api-contract.md` when APIs, firmware endpoints, CLI commands, or web application flows exist; `docs/database-schema.md` when persistent data exists; and `docs/DESIGN.md` for UI scope.
 2. Write formal project docs in English by default unless the user explicitly asks for another documentation language.
 3. Keep `docs/doc-index.md` short. Use it as the read-routing map with document path, purpose, reads-when triggers, status, and last-updated date. Do not duplicate the docs it points to.
 4. Keep `README.md` public and developer friendly even for private projects: explain what the project is, who it is for, how to set it up, how to run the core workflow, how to configure it, and where deeper docs live. Do not put internal agent notes, private reasoning, secrets, or governance policy in the README.
@@ -44,10 +44,8 @@ If the user specifies a framework, runtime, or architecture constraint, the agen
 4. Scaffold the initial project structure only after runtime and architecture decisions are explicit:
    - Create only the directories and files justified by the approved structure.
    - Set up configuration, validation, error handling, observability, health checks, and persistence only when they fit the approved runtime and project scope.
-   - Every file must follow [naming conventions](../rules/naming-conv.md).
    - Every module must follow [architecture.md](../rules/architecture.md).
    - New code must pass the natural implementation pass in [architecture.md](../rules/architecture.md): start with the simplest correct flow, add complexity only when the requirement or repo evidence needs it, and do not add files or layers for small tasks.
-   - Every dependency must be justified per [efficiency-vs-hype.md](../rules/efficiency-vs-hype.md).
    - Use official framework setup commands or canonical starter flows when they produce newer, better-supported dependency defaults than manual package assembly.
    - Do not assemble a framework project from scratch by habit when official setup commands create the supported structure. Manual assembly is allowed only for tiny prototypes, educational demos, unusual repo constraints, or a documented architecture reason.
    - If containerization is selected, Docker assets must follow [docker-runtime.md](../rules/docker-runtime.md) and the latest official Docker docs instead of stale blog-era patterns. Selected Docker lanes require files and runbooks, not docs-only acknowledgment.
@@ -58,5 +56,5 @@ See [.agent-context/state/onboarding-report.json](../state/onboarding-report.jso
 
 ## UI/UX Bootstrap
 
-When a user requests frontend or UI/UX design, the agent must automatically execute the [bootstrap-design.md](./bootstrap-design.md) prompt to synthesize a dynamic design contract (`docs/DESIGN.md` + `docs/design-intent.json`).
+When a user requests frontend or UI/UX design, the agent must automatically execute the [bootstrap-design.md](./bootstrap-design.md) prompt to synthesize a dynamic markdown design contract (`docs/DESIGN.md`).
 Keep UI-only requests context-isolated: load [bootstrap-design.md](./bootstrap-design.md) and [frontend-architecture.md](../rules/frontend-architecture.md) first, and do not eagerly load backend-only rules unless the task explicitly crosses backend boundaries.

package/.agent-context/prompts/refactor.md

@@ -11,7 +11,7 @@ Before editing:
 3. If required project docs are missing, stop and bootstrap or update docs first.
 4. If the change touches UI, load .agent-context/prompts/bootstrap-design.md and .agent-context/rules/frontend-architecture.md before editing.
 5. If the change touches a dependency, framework, Docker, runtime, or ecosystem claim, verify current official docs before choosing.
-6. Enforce Universal SOP hard gate: stop implementation if root `README.md` is missing, if `docs/doc-index.md` is missing while `docs/` exists, if `docs/project-brief.md` is missing, if `docs/architecture-decision-record.md` is missing, if `docs/flow-overview.md` is missing, if `docs/database-schema.md` is missing while the project uses persistent data, if `docs/api-contract.md` is missing while the project exposes API or web application flows, or for UI scope if `docs/DESIGN.md` or `docs/design-intent.json` is missing.
+6. Enforce Universal SOP hard gate: stop implementation if root `README.md` is missing, if `docs/doc-index.md` is missing while `docs/` exists, if `docs/project-brief.md` is missing, if `docs/architecture-decision-record.md` is missing, if `docs/flow-overview.md` is missing, if `docs/database-schema.md` is missing while the project uses persistent data, if `docs/api-contract.md` is missing while the project exposes API or web application flows, or for UI scope if `docs/DESIGN.md` is missing.
 7. Enforce backend universal principles: no clever hacks, no premature abstraction, readability over brevity.
 8. For backend/API scope, enforce layered boundaries, zero-trust input validation, safe centralized error responses, bounded list reads, transaction safety for multi-write mutations, idempotency for sensitive mutations, and behavior-focused API tests.
 9. Backend/API governance is global and stack-agnostic. Do not create stack-specific adapters or framework-specific rule branches; apply the global rules through the framework already present in the target project.

package/.agent-context/prompts/review-code.md

@@ -10,8 +10,8 @@ Before reviewing:
 2. Read .agent-context/review-checklists/pr-checklist.md.
 3. Read .agent-context/review-checklists/architecture-review.md only when architecture or boundaries changed.
 4. Load only the rules relevant to the changed scope.
-5. For UI changes, load .agent-context/prompts/bootstrap-design.md, .agent-context/rules/frontend-architecture.md, docs/DESIGN.md, and docs/design-intent.json when present.
-6. Enforce Universal SOP hard gate: block coding flow when required project docs are missing (root `README.md`; `docs/doc-index.md` when `docs/` exists; `docs/project-brief.md`; `docs/architecture-decision-record.md`; `docs/flow-overview.md`; `docs/database-schema.md` when persistent data exists; `docs/api-contract.md` when API or web application flows exist; and for UI scope `docs/DESIGN.md` plus `docs/design-intent.json`).
+5. For UI changes, load .agent-context/prompts/bootstrap-design.md, .agent-context/rules/frontend-architecture.md, and docs/DESIGN.md when present.
+6. Enforce Universal SOP hard gate: block coding flow when required project docs are missing (root `README.md`; `docs/doc-index.md` when `docs/` exists; `docs/project-brief.md`; `docs/architecture-decision-record.md`; `docs/flow-overview.md`; `docs/database-schema.md` when persistent data exists; `docs/api-contract.md` when API or web application flows exist; and for UI scope `docs/DESIGN.md`).
 7. Enforce single-source and lazy-loading policy: canonical rule source must be explicitly enforced, global domain governance must load lazily based on touched scope, and conflicting duplicate rule instructions must not appear during normal flow.
 
 Prioritize findings in this order:

package/.agent-context/review-checklists/pr-checklist.md

@@ -80,7 +80,7 @@ Run this before declaring a task done. Apply only the sections relevant to the c
 
 ## 7. UI And Accessibility
 
-- [ ] UI work follows `docs/DESIGN.md` and `docs/design-intent.json`.
+- [ ] UI work follows `docs/DESIGN.md`.
 - [ ] Visual direction is project-specific and not a template/default component-kit habit.
 - [ ] UI work includes a Motion/Palette Decision, and product categories were treated as heuristics rather than style presets.
 - [ ] Responsive behavior recomposes content and priority, not only shrinking desktop layout.
@@ -129,7 +129,7 @@ Run this before declaring a task done. Apply only the sections relevant to the c
 - [ ] Coding flow is blocked if `docs/flow-overview.md` is missing
 - [ ] Coding flow is blocked if `docs/database-schema.md` is missing while the project uses persistent data
 - [ ] Coding flow is blocked if `docs/api-contract.md` is missing while the project exposes API or web application flows
-- [ ] UI implementation flow is blocked if `docs/DESIGN.md` or `docs/design-intent.json` is missing
+- [ ] UI implementation flow is blocked if `docs/DESIGN.md` is missing
 
 ## Verdict
 

package/.agent-context/rules/architecture.md

@@ -30,8 +30,4 @@ keywords: [architecture, arch, boundary, system]
 2. Load global domain rules lazily based on touched scope.
 3. Do not create or load stack-specific governance adapters as the baseline.
 
-## ARCH-008: Backend Universal Principles
-1. No clever hacks.
-2. No premature abstraction.
-3. Readability over brevity.
-4. Keep backend and shared core modules clean.
+

package/.agent-context/rules/frontend-architecture.md

@@ -22,7 +22,7 @@ Load this rule for UI-facing engineering work. This file contains strict enginee
 
 ## FE-011: Implementation Boundaries
 1. Follow the shipped project stack and current repo patterns.
-2. Do not hardcode Zustand, React Query, smart/dumb component doctrine.
+2. Do not hardcode framework-specific state management or data fetching libraries, or rigid component doctrines.
 
 ## FE-012: Data State Surface
 1. Explicitly handle empty, loading, error, and offline states.

package/AGENTS.md

@@ -33,12 +33,13 @@ Always prefix noisy shell commands: `ascx git status`, `ascx git diff`, `ascx np
 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.
 
 ## Layer Index
-### Layer 1: Rules (21 Files) [SCOPE-RESOLVED]
+### Layer 1: Rules (18 Files) [SCOPE-RESOLVED]
 Location: `.agent-context/rules/`.
 
 Load only relevant rule files. Do not read the entire rule directory by default.
 
-Available rules: `naming-conv.md` (`NAME-*`, v4), `architecture.md` (`ARCH-*`, v4), `security.md` (`SEC-*`, v4), `performance.md` (`PERF-*`, v4), `error-handling.md` (`ERR-*`, v4), `testing.md` (`TEST-*`, v4), `git-workflow.md` (`GIT-*`, v4), `efficiency-vs-hype.md` (`DEP-*`, v4), `api-docs.md` (`API-*`, v4), `microservices.md` (`SVC-*`, v4), `event-driven.md` (`EVT-*`, v4), `database-design.md` (`DATA-*`, v4), `realtime.md` (`RT-*`, v4), `frontend-architecture.md` (`FE-*`, v4), `docker-runtime.md` (`DOCK-*`, v4), `observability.md` (`OBS-*`, v4), `resilience.md` (`RES-*`, v4), `migrations.md` (`MIG-*`, v4), `background-jobs.md` (`JOB-*`, v4), `config-and-flags.md` (`CFG-*`, v4), `api-versioning.md` (`VER-*`, v4).
+Available rules: `architecture.md` (`ARCH-*`, v4), `security.md` (`SEC-*`, v4), `performance.md` (`PERF-*`, v4), `error-handling.md` (`ERR-*`, v4), `testing.md` (`TEST-*`, v4), `api-docs.md` (`API-*`, v4), `microservices.md` (`SVC-*`, v4), `event-driven.md` (`EVT-*`, v4), `database-design.md` (`DATA-*`, v4), `realtime.md` (`RT-*`, v4), `frontend-architecture.md` (`FE-*`, v4), `docker-runtime.md` (`DOCK-*`, v4), `observability.md` (`OBS-*`, v4), `resilience.md` (`RES-*`, v4), `migrations.md` (`MIG-*`, v4), `background-jobs.md` (`JOB-*`, v4), `config-and-flags.md` (`CFG-*`, v4), `api-versioning.md` (`VER-*`, v4).
+
 
 For Docker or Compose work, load `docker-runtime.md` and verify the latest official Docker docs before authoring container assets. Also perform live web research for Docker and framework/package setup claims. For framework or package setup work, use the latest stable compatible dependency set and official setup flow unless a documented compatibility constraint blocks it; prefer official framework scaffolders when they create the supported project shape. New dependencies are allowed when they improve efficiency, delivery time, correctness, accessibility, UX, or maintainability. Do not treat dependency avoidance or vague performance fear as a default reason to skip a modern maintained library.
 

package/README.md

@@ -115,7 +115,7 @@ If you see `Property $schema is not allowed`, keep `.vscode/mcp.json` without `$
 
 ## Design Direction
 
-For UI, UX, layout, screen, Tailwind, frontend, or redesign work, the pack routes agents through a research dossier prompt and design bootstrap before code changes. The flow synthesizes a conceptual anchor, derives typography, spacing, morphology, motion, and responsive behavior, and carries a 90-day freshness gate with an anti-repeat ledger to avoid recycling the same visual direction. Existing projects read the real repository and docs first; fresh projects ask the agent to recommend the stack from current evidence instead of hardcoding a framework.
+For UI, UX, layout, screen, Tailwind, frontend, or redesign work, the pack routes agents through a compact design bootstrap before code changes. The flow asks the agent to reject generic defaults, choose a concrete interaction anchor, record creative commitments, and write the result into `docs/DESIGN.md`. Existing projects read the real repository and docs first; fresh projects ask the agent to recommend the stack from current evidence instead of hardcoding a framework.
 
 See [docs/doc-index.md](docs/doc-index.md) for the full doc routing map.
 

package/lib/cli/adaptive-context/catalog.mjs

@@ -143,26 +143,6 @@ export const RULE_FAMILY_CATALOG = [
       'rapikan',
     ],
   },
-  {
-    label: 'NAME',
-    rulePath: '.agent-context/rules/naming-conv.md',
-    priority: 60,
-    triggers: [
-      'naming',
-      'name',
-      'variable',
-      'function name',
-      'comment',
-      'comments',
-      'readable',
-      'humanizer',
-      'natural code',
-      'generic name',
-      'namingnya',
-      'dibaca',
-      'variabel',
-    ],
-  },
   {
     label: 'FE',
     rulePath: '.agent-context/rules/frontend-architecture.md',
@@ -375,20 +355,6 @@ export const RULE_FAMILY_CATALOG = [
       'breaking change',
     ],
   },
-  {
-    label: 'DEP',
-    rulePath: '.agent-context/rules/efficiency-vs-hype.md',
-    priority: 200,
-    triggers: [
-      'dependency',
-      'dependencies',
-      'package',
-      'library',
-      'install',
-      'npm',
-      'framework',
-    ],
-  },
 ];
 
 export const PROMPT_CATALOG = [
@@ -415,11 +381,10 @@ export const DOCS_BY_LABEL = {
   ARCH: ['docs/architecture-decision-record.md', 'docs/flow-overview.md'],
   API: ['docs/api-contract.md'],
   DATA: ['docs/database-schema.md'],
-  FE: ['docs/DESIGN.md', 'docs/design-intent.json'],
+  FE: ['docs/DESIGN.md'],
   TEST: ['docs/flow-overview.md'],
 };
 
 export const STATE_BY_LABEL = {
   ARCH: ['.agent-context/state/architecture-map.md'],
-  DEP: ['.agent-context/state/dependency-map.md'],
 };

package/lib/cli/audits/typography-palette-anti-repeat-audit.mjs

@@ -4,14 +4,11 @@
  * Typography and palette anti-repeat audit.
  *
  * Scans CSS-like files for font-family declarations and color values, then
- * cross-checks them against
- * `docs/design-intent.json`'s
- * `researchDossier.metadata.antiRepeatLedger.previousTypographyChoices` and
- * `previousPalettes` so a redesign cannot leak the previous direction's
- * exact font trio or perceptually-identical palette colors through CSS
- * implementation files alone.
  *
- * Severity model:
+ * DEPRECATED: This audit was built for the legacy design-intent.json system
+ * and its machine-readable antiRepeatLedger. In the 2026 Context Ops Paradigm,
+ * anti-repeat checks are handled by the LLM reading docs/DESIGN.md's 
+ * "Previous Directions" blocklist. This audit now unconditionally skips.
  *   - Typography matches are EXACT family-name matches and are always
  *     blocking (kind: typography.previously-shipped-family,
  *     diagnosticCode: BOUNDARY_TYPOGRAPHY_LEDGER_VIOLATION).
@@ -129,19 +126,8 @@ function findPaletteFindingsForFile({ relativeFilePath, sourceText, ledgerColors
   return findings;
 }
 
-function loadDesignIntentContract(repositoryRootPath, designIntentRelativePath) {
-  const designIntentAbsolutePath = join(repositoryRootPath, designIntentRelativePath);
-  if (!existsSync(designIntentAbsolutePath)) {
-    return { contract: null, reason: 'design-intent-file-absent' };
-  }
-  let contract;
-  try {
-    contract = JSON.parse(readFileSync(designIntentAbsolutePath, 'utf8'));
-  } catch (parseError) {
-    const errorMessage = parseError instanceof Error ? parseError.message : String(parseError);
-    return { contract: null, reason: `design-intent-file-not-valid-json: ${errorMessage}` };
-  }
-  return { contract, reason: 'ok' };
+function loadDesignIntentContract() {
+  return { contract: null, reason: 'design-intent-deprecated-use-design-md-blocklist' };
 }
 
 function buildSkippedReport(reportShell, reason) {
@@ -200,12 +186,10 @@ export function runTypographyPaletteAntiRepeatAudit(auditOptions = {}) {
     },
   };
 
-  const designIntentLoad = loadDesignIntentContract(repositoryRootPath, designIntentRelativePath);
+  const designIntentLoad = loadDesignIntentContract();
   if (!designIntentLoad.contract) {
     return buildSkippedReport(reportShell, designIntentLoad.reason);
   }
-
-  const antiRepeatLedger = designIntentLoad.contract?.researchDossier?.metadata?.antiRepeatLedger;
   if (!antiRepeatLedger || typeof antiRepeatLedger !== 'object') {
     return buildSkippedReport(reportShell, 'anti-repeat-ledger-absent');
   }

package/lib/cli/compiler.mjs

@@ -468,7 +468,6 @@ export async function buildCompiledRulesContent({
       'api-contract.md',
       'flow-overview.md',
       'DESIGN.md',
-      'design-intent.json',
       'runbook.md',
       'troubleshooting.md',
     ];

package/lib/cli/project-scaffolder/prompt-builders.mjs

@@ -130,13 +130,13 @@ export function buildDesignBootstrapPrompt({
     `Protocol version: ${PROJECT_DOC_SYNTHESIS_PROMPT_VERSION}`,
     '',
     'You are the Lead UI/UX Art Director for this project.',
-    'Create a dynamic design contract, not a fixed stylistic template.',
+    'Create a compact design token file, not a fixed stylistic template or prose document.',
     '',
     '## Mission',
-    `Author docs/DESIGN.md in ${docsLanguage.toUpperCase()} language with strong art direction and engineering-ready guidance.`,
+    `Author docs/DESIGN.md in ${docsLanguage.toUpperCase()} language as a compact token file under 400 tokens.`,
     '',
     '## Deliverables',
-    '1. docs/DESIGN.md',
+    '1. docs/DESIGN.md (compact token file)',
     '',
     '## Design Direction Process',
     'Follow `.agent-context/prompts/bootstrap-design.md` for the three-step design direction:',
@@ -146,13 +146,12 @@ export function buildDesignBootstrapPrompt({
     '',
     '## Hard Rules',
     '1. Do not copy external style guides or anchor to famous product surfaces.',
-    '2. Do not choose final style, library, palette, typography, or motion from this offline scaffold.',
-    '3. Use repo evidence, active brief, current docs, and current official docs for technology choices.',
-    '4. WCAG 2.2 AA is the hard floor. APCA is advisory perceptual tuning only.',
-    '5. Research current official docs before importing any new UI-related library.',
-    '6. Do not default to any component kit by habit, and do not avoid them when they fit.',
-    '7. Keep research vocabulary internal; evidence, anchor, and category-code labels must not appear in public-facing docs.',
-    '8. Treat production content as blocking: remove demo, placeholder, lorem, TODO, and scaffold copy.',
+    '2. Use repo evidence, active brief, current docs, and current official docs for technology choices.',
+    '3. WCAG 2.2 AA is the hard floor. APCA is advisory perceptual tuning only.',
+    '4. Research current official docs before importing any new UI-related library.',
+    '5. Do not default to any component kit by habit, and do not avoid them when they fit.',
+    '6. Keep research vocabulary internal; evidence, anchor, and category-code labels must not appear in public-facing docs.',
+    '7. Treat production content as blocking: remove demo, placeholder, lorem, TODO, and scaffold copy.',
     '',
     '## Project Inputs',
     `- Project name: ${discoveryAnswers.projectName}`,
@@ -163,10 +162,10 @@ export function buildDesignBootstrapPrompt({
     `- Architecture constraint: ${initContext.blueprintFileName === 'agent-decision-architecture.md' ? 'agent recommendation required before coding' : toTitleCase(initContext.blueprintFileName)}`,
     '',
     '## Required Execution',
-    '1. Create or update docs/DESIGN.md with complete content covering: design intent, audience signals, visual direction, color/typography/spacing decisions, responsive strategy, motion rules, component language, accessibility non-negotiables, and anti-patterns.',
-    '2. Make the contract executable without screenshot dependency.',
-    '3. Preserve repoEvidence.designEvidenceSummary when onboarding or detector evidence exists.',
-    '4. After the contract exists, use it as a first-class source for future UI tasks.',
+    '1. Follow the output format defined in `.agent-context/prompts/bootstrap-design.md`: Anchor, Tokens, Constraints, Previous Directions.',
+    '2. Keep docs/DESIGN.md under 400 tokens. Rationale and derivation stay in working memory.',
+    '3. Make the token file executable without screenshot dependency.',
+    '4. After the token file exists, use it as a first-class source for future UI tasks.',
     '',
   ].join('\n');
 }

package/lib/cli/project-scaffolder/storage.mjs

@@ -15,7 +15,7 @@ import {
 } from './discovery.mjs';
 import {
   shouldBootstrapDesignDocument,
-} from './design-contract.mjs';
+} from './ui-scope-detection.mjs';
 import {
   buildDesignBootstrapPrompt,
   buildProjectContextBootstrapPrompt,

package/lib/cli/project-scaffolder/ui-scope-detection.mjs

@@ -0,0 +1,36 @@
+/**
+ * UI scope detection utility. Determines whether a project needs
+ * design bootstrap based on domain and blueprint signals.
+ *
+ * Extracted from design-contract/seed-signals.mjs so the design
+ * contract module can be removed without breaking this dependency.
+ */
+
+export function shouldBootstrapDesignDocument(discoveryAnswers, initContext) {
+  const normalizedDomain = String(discoveryAnswers.primaryDomain || '').trim().toLowerCase();
+  const normalizedBlueprint = String(initContext.blueprintFileName || '').trim().toLowerCase();
+
+  const isUiDomain = normalizedDomain.includes('web')
+    || normalizedDomain.includes('mobile')
+    || normalizedDomain.includes('frontend')
+    || normalizedDomain.includes('fullstack')
+    || normalizedDomain.includes('ui');
+
+  const isBackendOnlyDomain = normalizedDomain.includes('api service')
+    || normalizedDomain.includes('cli tool')
+    || normalizedDomain.includes('library');
+
+  const blueprintLooksUi = normalizedBlueprint.includes('frontend')
+    || normalizedBlueprint.includes('landing')
+    || normalizedBlueprint.includes('ui');
+
+  if (isUiDomain) {
+    return true;
+  }
+
+  if (!isBackendOnlyDomain && blueprintLooksUi) {
+    return true;
+  }
+
+  return false;
+}

package/lib/cli/project-scaffolder.mjs

@@ -19,9 +19,7 @@ export {
 
 export {
   shouldBootstrapDesignDocument,
-  validateDesignIntentContract,
-  validateDesignContractCompleteness,
-} from './project-scaffolder/design-contract.mjs';
+} from './project-scaffolder/ui-scope-detection.mjs';
 
 export {
   generateProjectDocumentation,

package/package.json

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

package/scripts/adaptive-context/fixtures.mjs

@@ -38,8 +38,8 @@ export const ADAPTIVE_CONTEXT_FIXTURES = [
   {
     id: 'indonesian-readable-service',
     requestText: 'Rapihin service ini biar namingnya enak dibaca.',
-    requiredLabels: ['ARCH', 'NAME'],
-    allowedLabels: ['ARCH', 'NAME'],
+    requiredLabels: ['ARCH'],
+    allowedLabels: ['ARCH'],
   },
   {
     id: 'natural-cron-silent',
@@ -86,8 +86,8 @@ export const ADAPTIVE_CONTEXT_FIXTURES = [
   {
     id: 'checkout-helper-naming',
     requestText: 'Rapihin nama variabel di checkout helper, jangan bikin abstraction baru.',
-    requiredLabels: ['ARCH', 'NAME'],
-    allowedLabels: ['ARCH', 'NAME'],
+    requiredLabels: ['ARCH'],
+    allowedLabels: ['ARCH'],
   },
   {
     id: 'mobile-button-cut-off',
@@ -125,12 +125,7 @@ export const ADAPTIVE_CONTEXT_FIXTURES = [
     requiredLabels: ['DATA', 'PERF', 'RES'],
     allowedLabels: ['DATA', 'PERF', 'RES'],
   },
-  {
-    id: 'dependency-update-check',
-    requestText: 'Cek dependency package ini outdated atau perlu update.',
-    requiredLabels: ['DEP'],
-    allowedLabels: ['DEP'],
-  },
+
   {
     id: 'frontend-redesign',
     requestText: 'Redesign this frontend screen from zero with responsive layout, motion, and UI design docs.',
@@ -158,8 +153,8 @@ export const ADAPTIVE_CONTEXT_FIXTURES = [
   {
     id: 'service-refactor-clean-code',
     requestText: 'Refactor this service module. Clean up helper names, avoid over-engineering, and keep tests readable.',
-    requiredLabels: ['ARCH', 'NAME', 'TEST'],
-    allowedLabels: ['ARCH', 'NAME', 'TEST'],
+    requiredLabels: ['ARCH', 'TEST'],
+    allowedLabels: ['ARCH', 'TEST'],
   },
   {
     id: 'versioned-api-endpoint',

package/scripts/context-triggered-audit.mjs

@@ -43,12 +43,7 @@ const REQUIRED_PR_CHECKLIST_SNIPPETS = [
   'User can always force strict audit mode manually',
 ];
 
-const REQUIRED_ARCHITECTURE_CHECKLIST_SNIPPETS = [
-  '## Backend Universal Principles',
-  'No clever hacks in backend and shared core modules',
-  'No premature abstraction',
-  'Readability over brevity',
-];
+const REQUIRED_ARCHITECTURE_CHECKLIST_SNIPPETS = [];
 
 function pushResult(results, isPassed, checkName, details) {
   results.push({

package/scripts/frontend-usability-audit.mjs

@@ -42,12 +42,7 @@ const REQUIRED_PR_CHECKLIST_SNIPPETS = [
   '### 15. Universal SOP Consolidation',
 ];
 
-const REQUIRED_ARCHITECTURE_CHECKLIST_SNIPPETS = [
-  '## Backend Universal Principles',
-  'No clever hacks in backend and shared core modules',
-  'No premature abstraction',
-  'Readability over brevity',
-];
+const REQUIRED_ARCHITECTURE_CHECKLIST_SNIPPETS = [];
 
 const REQUIRED_FRONTEND_RULE_SNIPPETS = [
   '## FE-009: Accessibility',
@@ -56,7 +51,7 @@ const REQUIRED_FRONTEND_RULE_SNIPPETS = [
   '## FE-010: CSS Production Hardening',
   'overflow, wrapping, truncation',
   '## FE-011: Implementation Boundaries',
-  'Do not hardcode Zustand, React Query, smart/dumb component doctrine',
+  'Do not hardcode framework-specific state management or data fetching libraries, or rigid component doctrines',
 ];
 
 const REQUIRED_BOOTSTRAP_DESIGN_SNIPPETS = [

package/scripts/release-gate/constants.mjs

@@ -28,17 +28,10 @@ export const AUTO_DOCS_SYNC_SCOPE_BOUNDARIES = [
 ];
 
 export const REQUIRED_BACKEND_ARCHITECTURE_RULE_SNIPPETS = [
-  'No clever hacks.',
-  'No premature abstraction.',
-  'Readability over brevity.',
-  'backend and shared core modules',
   'Do not create or load stack-specific governance adapters as the baseline.',
 ];
 
 export const REQUIRED_BACKEND_REVIEW_CHECKLIST_SNIPPETS = [
-  'No clever hacks in backend and shared core modules',
-  'No premature abstraction (base classes/util layers created only after repeated stable patterns)',
-  'Readability over brevity for maintainability',
   'Controllers, route handlers, and transport adapters do not contain business policy',
   'Sensitive mutations include idempotency or duplicate-submit coverage',
   'Backend/API governance was applied through global domain rules',
@@ -46,7 +39,6 @@ export const REQUIRED_BACKEND_REVIEW_CHECKLIST_SNIPPETS = [
 
 export const REQUIRED_RELEASE_VERSION = '4.3.4';
 export const REQUIRED_REFACTOR_PROMPT_SNIPPETS = [
-  'Enforce backend universal principles: no clever hacks, no premature abstraction, readability over brevity.',
   'Prioritize maintainability over compressed one-liners.',
   'zero-trust input validation',
   'idempotency for sensitive mutations',
@@ -54,10 +46,6 @@ export const REQUIRED_REFACTOR_PROMPT_SNIPPETS = [
 ];
 
 export const REQUIRED_ARCHITECTURE_REVIEW_CHECKLIST_SNIPPETS = [
-  '## Backend Universal Principles',
-  'No clever hacks in backend and shared core modules',
-  'No premature abstraction',
-  'Readability over brevity',
   'Service or use-case code owns orchestration',
   'Relational reads avoid N+1 patterns',
   'Global backend/API governance is used directly',

package/scripts/ui-design-judge/constants.mjs

@@ -7,18 +7,7 @@ const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
 
 export const REPOSITORY_ROOT = resolve(__dirname, '..', '..');
-export const DESIGN_INTENT_PATH = resolve(REPOSITORY_ROOT, 'docs', 'design-intent.json');
 export const DESIGN_GUIDE_PATH = resolve(REPOSITORY_ROOT, 'docs', 'DESIGN.md');
 export const MAX_DIFF_CHARS = 12000;
 export const UI_FILE_EXTENSIONS = new Set(['.js', '.jsx', '.ts', '.tsx', '.vue', '.css', '.scss', '.sass']);
-export const DESIGN_EXECUTION_REQUIRED_CAPABILITIES = [
-  'requireSurfacePlan',
-  'requireComponentGraph',
-  'requireViewportMutationPlan',
-  'requireInteractionStateMatrix',
-  'requireContentPriorityMap',
-  'requireTaskFlowNarrative',
-  'requireSignatureMoveRationale',
-  'requireStructuredHandoff',
-  'requireRepoEvidenceAlignment',
-];
+