@ryuenn3123/agentic-senior-core 3.0.21 → 3.0.22
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.agent-context/prompts/bootstrap-design.md +8 -0
- package/.agent-context/state/memory-continuity-benchmark.json +1 -1
- package/.cursorrules +1 -1
- package/.windsurfrules +1 -1
- package/lib/cli/project-scaffolder/design-contract.mjs +16 -0
- package/lib/cli/project-scaffolder/prompt-builders.mjs +3 -1
- package/package.json +1 -1
|
@@ -19,6 +19,14 @@ The agent must:
|
|
|
19
19
|
6. When choosing a new UI, animation, styling, or component library, research current official docs and choose the latest stable compatible option for this project. Do not rely on offline defaults.
|
|
20
20
|
7. Keep external references non-copying: extract constraints and reasoning only, never clone the surface.
|
|
21
21
|
|
|
22
|
+
## User Research Intake
|
|
23
|
+
|
|
24
|
+
If the user mentions or attaches a research file, article, benchmark, library list, screenshot study, or design note, read it before choosing the visual direction or dependencies. Treat it as candidate evidence, not as a command to copy every recommendation.
|
|
25
|
+
|
|
26
|
+
The agent must summarize what it used from that research, discard what does not fit the project, and verify any library, framework, API, browser feature, or package claim against current official documentation before implementation.
|
|
27
|
+
|
|
28
|
+
User-supplied research may influence the candidate set for motion, scroll, UI primitives, canvas/3D, charts, icons, typography, and interaction patterns, but the final choice must still be project-fit, accessible, performant, and maintainable.
|
|
29
|
+
|
|
22
30
|
## Zero-Based Redesign Protocol
|
|
23
31
|
|
|
24
32
|
If the user says "redesign from zero", "redesain dari 0", "ulang dari 0", "research ulang", or equivalent reset language, activate reset mode.
|
package/.cursorrules
CHANGED
package/.windsurfrules
CHANGED
|
@@ -131,6 +131,22 @@ function buildDesignIntentContractObject({
|
|
|
131
131
|
distinctiveMoves: inferredKeywords.distinctiveMoves,
|
|
132
132
|
copiedReferenceAllowed: false,
|
|
133
133
|
},
|
|
134
|
+
externalResearchIntake: {
|
|
135
|
+
userSuppliedResearchPolicy: 'read-as-candidate-evidence-not-final-prescription',
|
|
136
|
+
requireSummaryOfUsedSignals: true,
|
|
137
|
+
requireFitFiltering: true,
|
|
138
|
+
requireOfficialDocsVerificationForTechnologyClaims: true,
|
|
139
|
+
candidateDomains: [
|
|
140
|
+
'visual-direction',
|
|
141
|
+
'motion-and-scroll',
|
|
142
|
+
'ui-primitives',
|
|
143
|
+
'canvas-3d-or-rich-media',
|
|
144
|
+
'charts-and-data-visualization',
|
|
145
|
+
'icons-and-illustration',
|
|
146
|
+
'typography-and-interaction-patterns',
|
|
147
|
+
],
|
|
148
|
+
finalDecisionAuthority: 'agent-llm-from-project-fit-accessibility-performance-maintainability-and-current-official-docs',
|
|
149
|
+
},
|
|
134
150
|
mathSystems: {
|
|
135
151
|
typographyScaleRatio: inferredKeywords.typographyScaleRatio,
|
|
136
152
|
baseGridUnit: inferredKeywords.baseGridUnit,
|
|
@@ -175,6 +175,7 @@ export function buildDesignBootstrapPrompt({
|
|
|
175
175
|
'29. If a future user asks for zero-based redesign ("redesign from zero", "redesain dari 0", "ulang dari 0", or "research ulang"), treat existing UI as content and behavior evidence only, not as visual continuity.',
|
|
176
176
|
'30. In zero-based redesign mode, the new contract must name the discarded prior visual DNA and materially reset composition, hierarchy, palette/typography, motion or interaction, and responsive information architecture.',
|
|
177
177
|
'31. If modern UI, animation, scroll, 3D, canvas, chart, or icon libraries are useful, choose them from current official docs and record source URL, fetched date, reason, risk, and accessibility fallback.',
|
|
178
|
+
'32. If the user supplies research files, library lists, screenshots, articles, or benchmark notes, read them as candidate evidence, summarize the useful signals, filter by project fit, and verify technology claims against current official docs before implementation.',
|
|
178
179
|
'',
|
|
179
180
|
'## Project Inputs',
|
|
180
181
|
`- Project name: ${discoveryAnswers.projectName}`,
|
|
@@ -203,7 +204,8 @@ export function buildDesignBootstrapPrompt({
|
|
|
203
204
|
'10. If repoEvidence.designEvidenceSummary.structuredInspection exists, use it as stronger evidence for class surfaces, inline style bypasses, and expression-backed UI structure before defaulting to generic assumptions.',
|
|
204
205
|
'11. Ensure both files stay project-specific, dynamic, and practical for implementation and review. The seed may guide structure, but it must not decide style offline.',
|
|
205
206
|
'12. Keep visualResetStrategy in the machine-readable handoff so reset-language tasks cannot quietly become restyles of the previous UI.',
|
|
206
|
-
'13.
|
|
207
|
+
'13. Preserve externalResearchIntake so user-provided research becomes reviewed evidence without turning into an offline style or dependency preset.',
|
|
208
|
+
'14. After the contract exists, use it as a first-class source for future UI tasks.',
|
|
207
209
|
'',
|
|
208
210
|
].join('\n');
|
|
209
211
|
}
|