@ryuenn3123/agentic-senior-core 4.3.15 → 5.1.0

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@ryuenn3123/agentic-senior-core",
-  "version": "4.3.15",
+  "version": "5.1.0",
   "type": "module",
-  "description": "Change your AI Agent to code like a Staff Engineer, not a Junior.",
+  "description": "Universal AI coding rules. Write code like a staff engineer, not a junior.",
   "bin": {
     "asc": "bin/agentic-senior-core.js",
     "agentic-senior-core": "bin/agentic-senior-core.js",
@@ -10,27 +10,34 @@
   },
   "files": [
     "bin/",
-    "benchmarks/compact-natural-mode/",
-    "benchmarks/runtime-token-saver/",
-    "lib/",
-    "scripts/",
-    ".agent-context/policies/",
-    ".agent-context/prompts/",
-    ".agent-context/review-checklists/",
-    ".agent-context/rules/",
-    ".agent-context/state/README.md",
-    ".agent-context/state/architecture-map.md",
-    ".agent-context/state/dependency-map.md",
-    ".agent-context/state/benchmark-comparison-schema.json",
-    ".agent-context/state/benchmark-reproducibility.json",
-    ".agent-context/state/benchmark-thresholds.json",
-    ".agent-context/state/benchmark-writer-judge-config.json",
-    ".agent-context/state/memory-adapter-contract.json",
-    ".agent-context/state/memory-schema-v1.json",
+    "lib/cli/commands/adapter.mjs",
+    "lib/cli/commands/clean.mjs",
+    "lib/cli/commands/status.mjs",
+    "lib/cli/commands/mcp.mjs",
+    "lib/cli/ascx/",
+    ".claude-plugin/",
+    ".codex-plugin/",
+    ".devin-plugin/",
+    ".github/plugin/",
+    ".github/copilot-instructions.md",
+    ".agents/",
+    ".openclaw/",
+    ".opencode/",
+    ".cursor/rules/",
+    ".windsurf/rules/",
+    ".clinerules/",
+    ".kiro/steering/",
+    "gemini-extension.json",
+    "plugin.yaml",
+    "__init__.py",
+    "commands/",
+    "hooks/",
+    "skills/",
+    "scripts/mcp-server.mjs",
+    "scripts/mcp-server/",
+    "scripts/uninstall.js",
     "AGENTS.md",
     "CLAUDE.md",
-    "GEMINI.md",
-    "mcp.json",
     "README.md",
     "LICENSE",
     "CONTRIBUTING.md"
@@ -44,58 +51,27 @@
   "keywords": [
     "ai",
     "coding-standards",
-    "cursorrules",
+    "claude-code",
+    "codex",
+    "cursor",
     "windsurf",
     "copilot",
-    "antigravity",
+    "cline",
+    "kiro",
+    "gemini",
+    "devin",
+    "hermes",
+    "opencode",
+    "openclaw",
+    "plugin",
+    "universal",
     "clean-code",
     "engineering-standards",
+    "security",
+    "architecture",
     "agentic"
   ],
   "scripts": {
-    "init": "node ./bin/agentic-senior-core.js init",
-    "audit:frontend-usability": "node ./scripts/frontend-usability-audit.mjs",
-    "audit:documentation-boundary": "node ./scripts/documentation-boundary-audit.mjs",
-    "audit:context-triggered": "node ./scripts/context-triggered-audit.mjs",
-    "audit:rules-guardian": "node ./scripts/rules-guardian-audit.mjs",
-    "audit:explain-on-demand": "node ./scripts/explain-on-demand-audit.mjs",
-    "audit:single-source-lazy-loading": "node ./scripts/single-source-lazy-loading-audit.mjs",
-    "audit:cache-layer-contract": "node ./scripts/audit-cache-layer-contract.mjs",
-    "audit:reflection-citations": "node ./scripts/audit-reflection-citations.mjs",
-    "audit:caching-scope-hygiene": "node ./scripts/audit-caching-scope-hygiene.mjs",
-    "audit:typography-palette-anti-repeat": "node ./scripts/audit-typography-palette-anti-repeat.mjs",
-    "audit:release-bundle": "node ./scripts/audit-release-bundle.mjs",
-    "audit:file-size": "node ./scripts/audit-file-size.mjs",
-    "audit:rule-id-uniqueness": "node ./scripts/audit-rule-id-uniqueness.mjs",
-    "build:release-bundle": "node ./scripts/build-release-benchmark-bundle.mjs",
-    "sync:adapters": "node ./scripts/sync-thin-adapters.mjs",
-    "check:adapters": "node ./scripts/sync-thin-adapters.mjs --check",
-    "gate:release": "node ./scripts/release-gate.mjs && node ./scripts/forbidden-content-check.mjs",
-    "prepublishOnly": "npm run gate:release",
-    "sbom:generate": "node ./scripts/generate-sbom.mjs",
-    "benchmark:detection": "node ./scripts/detection-benchmark.mjs",
-    "benchmark:token": "node ./scripts/token-optimization-benchmark.mjs",
-    "benchmark:adaptive-context": "node ./scripts/adaptive-context-benchmark.mjs",
-    "benchmark:ascx": "node ./scripts/ascx-runtime-token-saver-benchmark.mjs",
-    "benchmark:compact-natural": "node ./scripts/compact-natural-mode-benchmark.mjs",
-    "benchmark:bundle": "node ./scripts/benchmark-evidence-bundle.mjs",
-    "benchmark:writer-judge": "node ./scripts/benchmark-writer-judge-matrix.mjs",
-    "benchmark:gate": "node ./scripts/benchmark-gate.mjs",
-    "benchmark:intelligence": "node ./scripts/benchmark-intelligence.mjs",
-    "benchmark:continuity": "node ./scripts/memory-continuity-benchmark.mjs",
-    "benchmark:cache-phase-2": "node ./benchmarks/token-usage/run-cache-simulation.mjs",
-    "benchmark:anti-halu": "node ./benchmarks/anti-halu/run-benchmark.mjs",
-    "report:quality-trend": "node ./scripts/quality-trend-report.mjs",
-    "report:docs-quality-drift": "node ./scripts/docs-quality-drift-report.mjs",
-    "report:governance-weekly": "node ./scripts/governance-weekly-report.mjs",
-    "clean:local": "node ./scripts/clean-local-artifacts.mjs",
-    "validate": "node ./scripts/validate.mjs",
-    "test": "node --test ./tests/cli-smoke.test.mjs ./tests/mcp-server.test.mjs ./tests/llm-judge.test.mjs ./tests/ui-rubric-calibration.test.mjs ./tests/operations.test.mjs ./tests/knowledge-injection.test.mjs ./tests/audit-caching-scope-hygiene.test.mjs ./tests/research-dossier-migration.test.mjs ./tests/typography-palette-anti-repeat-audit.test.mjs ./tests/audit-design-anti-repeat-command.test.mjs ./tests/adaptive-context.test.mjs ./tests/ascx-runtime-token-saver.test.mjs ./tests/compact-natural-mode.test.mjs ./benchmarks/token-usage/lib/token-counter.test.mjs ./benchmarks/token-usage/lib/provider-cache-matrix.test.mjs ./benchmarks/token-usage/lib/cache-layer-contract.test.mjs ./benchmarks/token-usage/lib/cache-economics.test.mjs"
-  },
-  "devDependencies": {
-    "@anthropic-ai/sdk": "^0.96.0",
-    "@google/genai": "^2.3.0",
-    "tiktoken": "^1.0.22",
-    "yaml": "^2.9.0"
+    "test": "node --test ./tests/adapter.test.mjs"
   }
 }

package/plugin.yaml

@@ -0,0 +1,16 @@
+name: agentic-senior-core
+version: 5.1.0
+description: Universal AI coding rules. Write code like a staff engineer.
+author: fatidaprilian
+provides_hooks:
+  - pre_llm_call
+provides_commands:
+  - asc-refactor
+  - asc-review
+  - asc-audit
+  - asc-help
+provides_skills:
+  - asc
+  - asc-refactor
+  - asc-review
+  - asc-audit

package/scripts/uninstall.js

@@ -0,0 +1,38 @@
+#!/usr/bin/env node
+/**
+ * Uninstall cleanup script.
+ * Run this BEFORE removing the plugin from the host, since the host
+ * removal deletes the plugin directory (including this script).
+ *
+ * Cleans up:
+ * - Optional config at ~/.config/agentic-senior-core/
+ * - StatusLine entries in ~/.claude/settings.json (if any were added)
+ */
+import fs from 'node:fs/promises';
+import path from 'node:path';
+import os from 'node:os';
+
+const HOME = os.homedir();
+
+async function pathExists(filePath) {
+  try {
+    await fs.access(filePath);
+    return true;
+  } catch {
+    return false;
+  }
+}
+
+async function main() {
+  const configDir = path.join(HOME, '.config', 'agentic-senior-core');
+  if (await pathExists(configDir)) {
+    await fs.rm(configDir, { recursive: true, force: true });
+    console.log(`Removed config directory: ${configDir}`);
+  }
+
+  console.log('Cleanup complete. You can now remove the plugin from your IDE.');
+}
+
+main().catch((error) => {
+  console.error('Uninstall cleanup failed:', error.message);
+});

package/skills/asc/SKILL.md

@@ -0,0 +1,16 @@
+# Agentic Senior Core
+
+Universal AI coding rules. Write code like a staff engineer.
+
+## Available Commands
+
+- `/asc-refactor` -- Structured refactoring workflow with pre-checks and validation
+- `/asc-review` -- Production-risk code review with severity-ordered findings
+- `/asc-audit` -- Security and architecture audit
+- `/asc-help` -- Show this help
+
+## What It Does
+
+Loads universal engineering rules on every session: code quality, architecture, security, error handling, testing, API design, database, frontend, infrastructure, resilience, and async patterns.
+
+Rules apply to any project, stack, language, or framework. No per-project configuration needed.

package/skills/asc-audit/SKILL.md

@@ -0,0 +1,28 @@
+# Audit Skill
+
+Security and architecture audit. Deeper than review, focused on finding vulnerabilities and structural anti-patterns.
+
+## Audit Scope
+
+1. **Trust boundaries**: Every point where external input enters the system. Validate that inputs are sanitized, normalized, and rejected when invalid.
+2. **Authentication and authorization**: Verify auth checks exist on every endpoint. Check for resource-level authorization, not just identity.
+3. **Data handling**: Secrets in code or logs, PII exposure, unsafe deserialization, SQL injection, command injection.
+4. **Architecture boundaries**: Business logic in transport layer, shared databases between services, circular dependencies, internal model leakage through public APIs.
+5. **Dependency health**: Known vulnerabilities, unmaintained packages, excessive dependency surface.
+6. **Error exposure**: Stack traces, internal paths, or implementation details exposed to clients.
+
+## For Every Finding
+
+```
+Severity: critical | high | medium | low
+Class: vulnerability class (e.g., SQL Injection, Broken Access Control)
+Location: file:line
+Impact: who or what is affected
+Evidence: exact code, behavior, or command output
+Remediation: specific fix direction
+Validation: how to prove it is fixed
+```
+
+## Output
+
+Findings ordered by severity. If no findings, state that explicitly and describe audit coverage.

package/skills/asc-refactor/SKILL.md

@@ -0,0 +1,35 @@
+# Refactor Skill
+
+Structured refactoring workflow. Preserves existing behavior while improving structure.
+
+## Before Editing
+
+1. Read the target code and understand existing patterns.
+2. Identify the smallest relevant scope for the refactor.
+3. If the change touches UI, check accessibility and responsive behavior.
+4. If the change touches dependencies, verify current official docs.
+
+## Refactor Rules
+
+- Improve clarity, boundaries, naming, validation, error handling, and tests.
+- Prioritize maintainability over compressed one-liners.
+- Keep the main flow traceable. Use early returns where they reduce nesting.
+- Do not introduce abstractions before the repeated pattern is real.
+- Split large files when the split makes the flow easier to understand.
+- Remove code that does not carry behavior, safety, clarity, maintainability, or test value.
+- Prefer the shorter implementation only when it keeps the same guarantees.
+- Run a final simplification pass before completion.
+- Update tests and docs whenever behavior contracts, public APIs, data shape, or UI contracts change.
+
+## For Every Change, Explain
+
+- What risk or friction existed.
+- What changed.
+- Why the new shape is safer or easier to maintain.
+
+## Validation
+
+- Existing behavior is preserved unless the user approved a change.
+- Edge cases, empty states, error paths, and rollback paths are handled.
+- Public contracts remain stable or are versioned.
+- Tests pass.

package/skills/asc-review/SKILL.md

@@ -0,0 +1,54 @@
+# Review Skill
+
+Production-risk code review. Prioritize findings by severity.
+
+## Before Reviewing
+
+1. Read the changed files and understand the scope.
+2. For UI changes, check accessibility and design consistency.
+3. For API changes, check contract stability and documentation sync.
+
+## Finding Priority Order
+
+1. Correctness, data loss, security, privacy, auth, and permission risks.
+2. Public contract drift: APIs, events, CLI behavior, data model, UI contract, docs.
+3. Missing tests for changed behavior.
+4. Architecture boundary drift and maintainability risk.
+5. Performance and accessibility issues with concrete impact.
+
+## For Every Finding
+
+- Include file and line reference.
+- Explain the real risk.
+- Propose the smallest safe fix.
+
+## Checklist
+
+### Correctness
+- Changed behavior matches the user request.
+- Existing behavior preserved unless user approved a change.
+- Edge cases, empty states, error paths handled.
+
+### Security
+- External input validated at trust boundaries.
+- Secrets, tokens, credentials not committed or logged.
+- Authorization enforced at a trusted boundary.
+- Error responses do not leak internals.
+
+### Architecture
+- Layer boundaries clear. Controllers do not hold business logic.
+- No premature abstraction. No clever hacks.
+- Complexity budget applied: fewer moving parts without losing safety.
+
+### Testing
+- Changed behavior has appropriate tests.
+- Tests assert behavior and contracts, not implementation trivia.
+- Critical flows include failure-path coverage.
+
+### Documentation
+- API, event, CLI, and data contract changes update docs in the same commit.
+- Root README exists and stays current.
+
+## Output
+
+Report findings ordered by severity with file/line references and concrete fixes. If no findings, say so explicitly and name any residual risk.

package/.agent-context/policies/llm-judge-threshold.json

@@ -1,29 +0,0 @@
-{
-  "selectedProfile": "beginner",
-  "profileThresholds": {
-    "beginner": {
-      "blockingSeverities": [
-        "critical"
-      ],
-      "failOnMalformedResponse": false,
-      "failOnProviderError": false
-    },
-    "balanced": {
-      "blockingSeverities": [
-        "critical",
-        "high"
-      ],
-      "failOnMalformedResponse": true,
-      "failOnProviderError": false
-    },
-    "strict": {
-      "blockingSeverities": [
-        "critical",
-        "high",
-        "medium"
-      ],
-      "failOnMalformedResponse": true,
-      "failOnProviderError": true
-    }
-  }
-}

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

@@ -1,63 +0,0 @@
-# Design Direction Prompt
-
-Use this prompt for UI, UX, frontend layout, screen, or redesign work. Create or refine `docs/DESIGN.md` before writing UI code.
-
-## Authority
-
-- 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.
-- 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 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**: 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.
-
-## Redesign Protocol
-
-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.
-
-## Output Format
-
-`docs/DESIGN.md` must be a compact token file under 400 tokens. Rationale stays in working memory.
-
-Required sections (in this order, no additions):
-
-### Anchor
-One sentence: the interaction anchor and what mechanic is borrowed.
-
-### 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
-
-### Constraints
-- WCAG 2.2 AA floor
-- Up to 3 product-specific anti-patterns
-
-### Previous Directions
-Anchors used in prior iterations (blocklist for redesign). Start empty for fresh projects.
-
-## Required Validation Gates
-
-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.
-
-## Pre-Commit Critique
-
-Before committing any UI output, answer:
-
-1. Rename test: if the product name changed to an unrelated category, would this UI still look identical? Yes = too generic, reset anchor.
-2. Token drift test: does any color, font, or spacing in the output contradict the DESIGN.md token definitions? Yes = align before commit.
-3. Security test: is user-controlled data rendered unsanitized, or does any status depend on color alone? Yes = fix before merge.
-
-Max 3 revision cycles. If unresolved, reset the anchor entirely.

package/.agent-context/prompts/compact-natural-mode.md

@@ -1,100 +0,0 @@
-# Compact Natural Mode
-
-Status: active default response contract.
-
-Use this prompt for final user-facing replies after the task-specific rule, prompt, checklist, and validation work is complete.
-
-## Purpose
-
-Write the smallest complete answer that still lets the next developer act correctly.
-
-Compact means high signal. It does not mean broken grammar, dialect, clipped fragments, or hiding evidence.
-
-## Always Remove
-
-- greetings, affirmations, and repeated restatements
-- narration about what you are about to do
-- generic closing offers
-- padding paragraphs that add no new technical content
-- repeated summaries of the same decision
-
-## Always Preserve
-
-- exact commands
-- exact file paths and line numbers
-- exact error messages, assertions, exit codes, and stack-trace highlights
-- validation status, including tests not run
-- assumptions, scope qualifiers, blockers, risks, and next actions
-- destructive-operation warnings
-- breaking changes and migration notes
-
-## Task Shapes
-
-Use natural prose inside these shapes. Omit fields that do not apply, except safety fields.
-
-Debug/root cause:
-
-```text
-Root Cause: <one sentence>
-Evidence: <exact error, command output, or file:line>
-Fix: <exact command or code direction>
-Next: <verification step>
-```
-
-Test failure:
-
-```text
-Failed: <test name>
-Expected/Got: <value> / <value>
-At: <file:line>
-Evidence: <exact assertion or root error>
-Fix direction: <one sentence>
-```
-
-Code review finding:
-
-```text
-[critical|warn|nit] <file>:<line> - <concern>. <requested change>
-```
-
-Implementation/refactor summary:
-
-```text
-Changed: <what changed>
-Reason: <why>
-Behavior: <changed, unchanged, or not verified>
-Validation: <what ran or was not run>
-Risk: <only if relevant>
-```
-
-Destructive command:
-
-```text
-WARNING: <what this destroys and whether it is reversible>
-Command: <exact command>
-Precondition: <what must be true before running>
-```
-
-Security finding:
-
-```text
-Severity: <critical|high|medium|low>
-Class: <vulnerability class>
-Location: <file:line>
-Impact: <who or what is affected>
-Evidence: <exact code, behavior, or command output>
-Remediation: <specific fix direction>
-Validation: <how to prove it is fixed>
-```
-
-Planning/architecture may be longer. Keep decision, rationale, alternatives, tradeoffs, assumptions, and open questions visible.
-
-## Second-Pass Check
-
-Before finalizing:
-
-1. Remove any sentence that adds no new technical content.
-2. Confirm mandatory evidence atoms remain exact.
-3. Confirm assumptions and validation gaps are visible.
-4. Confirm the answer has a decision or next action when the user asked for one.
-5. Confirm the tone is natural professional writing.

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

@@ -1,60 +0,0 @@
-# Project Initialization Prompts
-
-This prompt boots a repository with strict AI coding guidance context.
-
-## System Directives (Auto Execution)
-
-When a new project is created or initialized, the agent must automatically:
-1. Read [AGENTS.md](../../AGENTS.md) to understand the canonical bootstrap chain and active entrypoints.
-2. Resolve the smallest relevant rule set from [.agent-context/rules/](../rules/) instead of scanning the whole directory by default.
-3. Review dynamic runtime signals from [.agent-context/state/onboarding-report.json](../state/onboarding-report.json), repository evidence, task constraints, and live official documentation when runtime or ecosystem facts matter.
-4. If Docker or Compose is in scope, load [docker-runtime.md](../rules/docker-runtime.md) and verify the latest official Docker guidance before authoring container assets. Materialize the selected development/production assets rather than stopping at prose.
-5. For unresolved framework or package setup, recommend the latest stable compatible dependency set and official framework setup flow from live official documentation before coding unless a documented compatibility constraint blocks it.
-6. Do not default fresh web projects to Next.js, Tailwind-only styling, shadcn/ui, Vite, or any framework by habit, and do not avoid them because of this guard when they are the strongest fit. Treat explicit user constraints as constraints; otherwise compare project needs, runtime boundaries, hosting, data flow, team workflow, and official setup guidance before recommending.
-
-## Required Planning Mode
-
-If the user describes a project or feature, the agent must:
-1. Before drafting docs from a thin or ambiguous brief, ask the smallest useful set of clarifying questions needed to make delivery goals, edge cases, constraints, must-have capabilities, and non-goals explicit. If the user wants a draft anyway, document assumptions and wait for approval before coding.
-2. If the user already named a stack or framework, treat it as an explicit constraint. If not, produce a short evidence-backed recommendation from the brief, repo evidence, and live official documentation before coding. Include at least one plausible alternative when the default-looking option is Next.js, Tailwind-only styling, shadcn/ui, or another familiar web stack.
-3. For existing projects, inspect real files first. Do not derive product name, description, runtime, architecture, or design direction from the folder name alone.
-4. Draft a high-level structure plan plus the docs/bootstrap artifacts that must exist before coding.
-5. Wait for user approval before scaffolding the project.
-
-## Documentation-First Requests
-
-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` 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.
-5. Keep documentation alive. When project behavior, setup, architecture, public contracts, data shape, deployment, or UI scope changes, update the matching docs in the same change.
-6. Avoid documentation sprawl. Add a new docs file only when the topic is stable, long enough to outgrow the README or core docs, or owned by a separate workflow such as hardware setup, deployment, troubleshooting, or testing validation.
-7. Add PRD, SRS, technical-design, or separate ERD only when evidence triggers them. Use PRD for product roadmap/user-story ownership, SRS for contractual or multi-stakeholder acceptance criteria, technical-design for non-trivial architecture decisions, and a separate ERD only when `docs/database-schema.md` cannot stay readable with an embedded diagram.
-8. Stop after docs when the user only asked for docs. Do not write application, firmware, or UI code until the user explicitly asks for implementation or approves the implementation plan.
-
-## Direct Constraint Mode
-
-If the user specifies a framework, runtime, or architecture constraint, the agent must:
-1. Read [AGENTS.md](../../AGENTS.md) for role context.
-2. Resolve only the rules required by the explicit constraint and scope. Do not read unrelated backend, frontend, or DevOps rules by habit.
-3. Reference [.agent-context/state/onboarding-report.json](../state/onboarding-report.json), [AGENTS.md](../../AGENTS.md), and the relevant `.agent-context/` files for runtime evidence and any explicit constraints already applied to this project.
-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 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.
-   - 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.
-
-## Runtime and Architecture Reference
-
-See [.agent-context/state/onboarding-report.json](../state/onboarding-report.json), [AGENTS.md](../../AGENTS.md), and the relevant `.agent-context/` files for the latest shipped runtime evidence, explicit constraints, and agent-decision status.
-
-## 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 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

@@ -1,38 +0,0 @@
-# Prompt: Refactor Code
-
-Use this when code needs cleanup, splitting, or safer structure without changing user-visible behavior.
-
-```text
-Refactor the target code while preserving existing behavior.
-
-Before editing:
-1. Read AGENTS.md and the smallest relevant rules from .agent-context/rules/.
-2. Inspect the real repo conventions before introducing a new structure.
-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` 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.
-10. Enforce the complexity budget: choose fewer moving parts only when behavior, safety, clarity, and maintainability stay intact.
-
-Refactor rules:
-- Improve clarity, boundaries, naming, validation, error handling, tests, and docs.
-- Prioritize maintainability over compressed one-liners.
-- Apply the natural implementation pass from architecture.md: keep the main flow traceable, use early returns where they reduce nesting, and avoid helper chains that only make the code look abstract.
-- Do not choose a stack, framework, library, or topology from offline assumptions.
-- Keep module boundaries explicit and project-specific.
-- Split large files when the split makes the flow easier to understand.
-- Do not introduce abstractions before the repeated pattern is real.
-- Remove code that does not carry behavior, safety, clarity, maintainability, or test value.
-- Prefer the shorter implementation only when it keeps the same guarantees.
-- Run a final simplification pass before completion.
-- Update tests and docs whenever behavior contracts, public APIs, data shape, or UI contracts change.
-- When fixing a bug: append one sentence to the nearest relevant doc (`docs/flow-overview.md` or `docs/architecture-decision-record.md`) naming the root cause and how to prevent recurrence.
-
-For every meaningful change, explain:
-- what risk or friction existed
-- what changed
-- why the new shape is safer or easier to maintain
-```