forepath · me-marcel · Oct 24, 2025 · Oct 24, 2025
diff --git a/.cursor/commands/plan.md b/.cursor/commands/plan.md
@@ -9,8 +9,12 @@ This guide defines the **REQUIRED** steps and best practices for planning new fe
 - You **MUST** review the relevant documentation, domain rules, and architectural guidelines before starting.
 - You **MUST** identify the affected applications, domains, and libraries.
 - You **SHOULD** check for existing issues, RFCs, or related work to avoid duplication.
-- You **MUST** ensure the feature aligns with the monorepo’s dependency and modularity rules.
+- You **MUST** ensure the feature aligns with the monorepo's dependency and modularity rules.
 - You **SHOULD** consult with stakeholders or team members if the feature impacts multiple domains or applications.
+- You **MUST** review any existing research that may inform the planning process.
+  - A research file reference **MAY** be provided within the chat history or as explicit reference.
+  - If research is needed but not available, you **SHOULD** recommend conducting research using [Research Guidelines](./research.md) before proceeding with planning.
+- You **MAY** summarize relevant research findings for context optimization so long as requirements are not lost in the process.
 
 ## 2. Planning
 

diff --git a/.cursor/commands/research.md b/.cursor/commands/research.md
@@ -0,0 +1,55 @@
+# Research Command
+
+This guide defines the **REQUIRED** steps and best practices for conducting research in the monorepo. All contributors **MUST** follow these steps to ensure comprehensive, well-documented research that can be effectively used during planning and implementation phases.
+
+> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
+
+## 1. Context
+
+- You **MUST** identify the research scope and objectives clearly.
+- You **MUST** determine if research is needed before planning or if it's part of an existing plan.
+- You **SHOULD** reference any existing plans, issues, or RFCs that triggered the research need.
+- You **MAY** summarize the research objectives for context optimization so long as requirements are not lost in the process.
+
+## 2. Research Execution
+
+- You **MUST** conduct comprehensive research using multiple sources and perspectives.
+- You **MUST** document all findings, sources, and methodologies used.
+- You **MUST** evaluate different approaches, technologies, and solutions objectively.
+- You **SHOULD** consider both technical and business implications of research findings.
+- You **MUST** identify potential risks, limitations, and constraints discovered during research.
+- You **SHOULD** research industry best practices, standards, and compliance requirements.
+- You **MUST** investigate existing solutions, libraries, and tools that could be leveraged.
+- You **SHOULD** analyze performance, security, and scalability implications.
+
+## 3. Documentation
+
+- You **MUST** document your research results in a Markdown (`.md`) file placed in the root-level `.research/` directory.
+- The research file **MUST** be named using the format: `YYYYMMDD_HHMMSS_research_topic.md` (e.g., `.research/20240607_153000_oauth_authentication_strategies.md`), using snake_case for the research topic and a concise, descriptive topic name.
+- You **MUST** use the [`template.md`](../../.research/template.md) file from the root-level `.research/` directory as the base structure for your research file. Copy its contents and fill in the relevant sections when creating new research.
+- You **MUST** reference the full path to the research file in related plans, issues, pull requests, and documentation for traceability.
+- You **MUST** include proper citations and references for all sources used.
+- You **SHOULD** create visual diagrams, flowcharts, or comparison tables when they add value to understanding the research.
+- You **MUST** document assumptions, limitations, and areas requiring further investigation.
+
+## 4. Research Validation
+
+- You **MUST** verify information from multiple credible sources.
+- You **SHOULD** cross-reference findings with official documentation and authoritative sources.
+- You **MUST** identify conflicting information and document how it was resolved.
+- You **SHOULD** validate technical claims through practical examples or proof-of-concepts when feasible.
+- You **MUST** document any uncertainties or areas where additional research is needed.
+
+## 5. Integration with Planning
+
+- You **MUST** ensure research findings are structured to support planning activities.
+- You **MUST** provide clear recommendations and rationale for decisions.
+- You **SHOULD** identify implementation considerations and prerequisites.
+- You **MUST** document dependencies and relationships between different research findings.
+- You **SHOULD** highlight critical decisions that will impact the planning phase.
+
+## 6. Confirmation
+
+- You **MUST** wait for confirmation before proceeding to planning or implementation phases.
+- You **SHOULD** present key findings and recommendations for stakeholder review.
+- You **MUST** address any questions or concerns raised during research review.
diff --git a/apps/frontend-tsef/src/app/app.routes.ts b/apps/frontend-tsef/src/app/app.routes.ts
@@ -1,5 +1,10 @@
 import { Route } from '@angular/router';
-import { FrameworkComponent, GettingStartedComponent, HomeComponent } from '@forepath/landingpage/frontend';
+import {
+  FrameworkComponent,
+  GettingStartedComponent,
+  HomeComponent,
+  WorkflowComponent,
+} from '@forepath/landingpage/frontend';
 
 export const appRoutes: Route[] = [
   {
@@ -14,4 +19,8 @@ export const appRoutes: Route[] = [
     path: 'framework',
     component: FrameworkComponent,
   },
+  {
+    path: 'workflow',
+    component: WorkflowComponent,
+  },
 ];
diff --git a/apps/frontend-tsef/src/i18n/messages.de.xlf b/apps/frontend-tsef/src/i18n/messages.de.xlf
@@ -208,7 +208,7 @@
       </trans-unit>
       <trans-unit id="gettingStartedHeroTitle" datatype="html">
         <source> The fastest way to an <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>AI-ready<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> Nx workspace </source>
-        <target> Der schnellste Weg zu einem <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>KI-bereiten<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> Nx-Workspace </target>
+        <target> Der schnellste Weg zu einem <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>KI-gestützten<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> Nx-Workspace </target>
       </trans-unit>
       <trans-unit id="gettingStartedHeroSubtitle" datatype="html">
         <source><x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>Enterprise-grade<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> TypeScript stack with smart Nx workflows, agent-powered tooling, and built-in compliance. </source>
@@ -384,7 +384,7 @@
       </trans-unit>
       <trans-unit id="heroTitle" datatype="html">
         <source> The <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>AI-ready<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> TypeScript Enterprise Framework </source>
-        <target> Das <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>KI-bereite<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> TypeScript Enterprise Framework </target>
+        <target> Das <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>KI-gestützte<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> TypeScript Enterprise Framework </target>
       </trans-unit>
       <trans-unit id="heroSubtitle" datatype="html">
         <source><x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>Enterprise-grade<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> Nx workflow with AI-powered development agents and built-in compliance. </source>
@@ -432,7 +432,7 @@
       </trans-unit>
       <trans-unit id="homeMetaDescription" datatype="html">
         <source>TSEF is the AI-ready TypeScript Enterprise Framework. Easily build, deploy, and scale modern enterprise applications with best practices, advanced tooling, and AI capabilities out of the box.</source>
-        <target>TSEF ist das KI-bereite TypeScript Enterprise Framework. Erstellen, deployen und skalieren Sie mühelos moderne Enterprise-Anwendungen mit Best Practices, fortschrittlichen Tools und KI-Funktionen out-of-the-box.</target>
+        <target>TSEF ist das KI-gestützte TypeScript Enterprise Framework. Erstellen, deployen und skalieren Sie mühelos moderne Enterprise-Anwendungen mit Best Practices, fortschrittlichen Tools und KI-Funktionen out-of-the-box.</target>
       </trans-unit>
       <trans-unit id="homeMetaKeywords" datatype="html">
         <source>TSEF, TypeScript, Enterprise Framework, AI-ready, Angular, web development, scalable, application framework, cloud, modern apps, enterprise solutions, software tools, best practices</source>
@@ -758,6 +758,74 @@
         <source>Built-in compliance, automated monitoring, enterprise governance rules</source>
         <target>Integrierte Compliance, automatisiertes Monitoring, Unternehmens-Governance-Regeln</target>
       </trans-unit>
+      <trans-unit id="workflowHeroTitle" datatype="html">
+        <source> Transform your <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>development workflow<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> with AI-powered automation </source>
+        <target> Transformieren Sie Ihren <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>Entwicklungsworkflow<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> mit KI-gestützter Automatisierung </target>
+      </trans-unit>
+      <trans-unit id="workflowHeroSubtitle" datatype="html">
+        <source> Streamline your entire development lifecycle from <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>research<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> to <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>ship<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> with intelligent Cursor commands. Built on proven Nx monorepo architecture for enterprise-grade reliability. </source>
+        <target> Optimieren Sie Ihren gesamten Entwicklungslebenszyklus von <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>Research<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> bis <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>Ship<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> mit intelligenten Cursor-Befehlen. Auf bewährter Nx-Monorepo-Architektur aufgebaut für unternehmensreife Zuverlässigkeit. </target>
+      </trans-unit>
+      <trans-unit id="gsWorkflowTitle" datatype="html">
+        <source>AI-Assisted Development Workflow</source>
+        <target>KI-gestützter Entwicklungsworkflow</target>
+      </trans-unit>
+      <trans-unit id="gsWorkflowIntro" datatype="html">
+        <source> Follow our structured four-step workflow to ensure quality and consistency. Start with <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>research<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/>, create a detailed <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>plan<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/>, then <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>implement<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> and finally <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>ship<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> your features with confidence. </source>
+        <target> Folgen Sie unserem strukturierten Vier-Schritte-Workflow, um Qualität und Konsistenz sicherzustellen. Beginnen Sie mit <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>Research<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/>, erstellen Sie einen detaillierten <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>Plan<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/>, dann <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>Implementieren<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> Sie und schließlich <x id="START_TAG_SPAN" ctype="x-span" equiv-text="&lt;span class=&quot;text-highlight&quot;&gt;"/>Ship<x id="CLOSE_TAG_SPAN" ctype="x-span" equiv-text="&lt;/span&gt;"/> Sie Ihre Features mit Vertrauen. </target>
+      </trans-unit>
+      <trans-unit id="workflowResearchCommand" datatype="html">
+        <source>/research</source>
+        <target>/research</target>
+      </trans-unit>
+      <trans-unit id="workflowResearchTitle" datatype="html">
+        <source>1. Research</source>
+        <target>1. Research</target>
+      </trans-unit>
+      <trans-unit id="workflowResearchDesc" datatype="html">
+        <source> Conduct comprehensive research using multiple sources and perspectives. Document findings, evaluate approaches, and identify risks and constraints. Create a research file in .research/ with proper citations and recommendations to inform planning. </source>
+        <target> Führen Sie umfassende Recherchen mit mehreren Quellen und Perspektiven durch. Dokumentieren Sie Ergebnisse, bewerten Sie Ansätze und identifizieren Sie Risiken und Einschränkungen. Erstellen Sie eine Research-Datei in .research/ mit ordnungsgemäßen Zitaten und Empfehlungen zur Informationsgrundlage für die Planung. </target>
+      </trans-unit>
+      <trans-unit id="workflowPlanTitle" datatype="html">
+        <source>2. Plan</source>
+        <target>2. Plan</target>
+      </trans-unit>
+      <trans-unit id="workflowPlanDesc" datatype="html">
+        <source> Review documentation and research findings, then break down features into actionable tasks. Determine appropriate locations following domain rules and use Nx generators. Document the plan in .plans/ with clear acceptance criteria and wait for confirmation. </source>
+        <target> Überprüfen Sie Dokumentation und Rechercheergebnisse, zerlegen Sie dann Features in umsetzbare Aufgaben. Bestimmen Sie geeignete Standorte gemäß Domänenregeln und verwenden Sie Nx-Generatoren. Dokumentieren Sie den Plan in .plans/ mit klaren Akzeptanzkriterien und warten Sie auf Bestätigung. </target>
+      </trans-unit>
+      <trans-unit id="workflowPlanCommand" datatype="html">
+        <source>/plan</source>
+        <target>/plan</target>
+      </trans-unit>
+      <trans-unit id="workflowImplementCommand" datatype="html">
+        <source>/implement</source>
+        <target>/implement</target>
+      </trans-unit>
+      <trans-unit id="workflowImplementTitle" datatype="html">
+        <source>3. Implement</source>
+        <target>3. Implementieren</target>
+      </trans-unit>
+      <trans-unit id="workflowImplementDesc" datatype="html">
+        <source> Implement features following the plan, established conventions, and naming standards. Create feature branches, make focused commits, and update documentation. Write comprehensive tests and run validation tasks to ensure quality before confirming. </source>
+        <target> Implementieren Sie Features gemäß Plan, etablierten Konventionen und Namensstandards. Erstellen Sie Feature-Branches, machen Sie fokussierte Commits und aktualisieren Sie die Dokumentation. Schreiben Sie umfassende Tests und führen Sie Validierungsaufgaben aus, um die Qualität vor der Bestätigung sicherzustellen. </target>
+      </trans-unit>
+      <trans-unit id="workflowShipTitle" datatype="html">
+        <source>4. Ship</source>
+        <target>4. Ausliefern</target>
+      </trans-unit>
+      <trans-unit id="workflowShipDesc" datatype="html">
+        <source> Open a pull request with a descriptive title and complete the PR template. Request review from code owners and stakeholders. Address feedback promptly and ensure all checks pass before merging. </source>
+        <target> Öffnen Sie einen Pull Request mit aussagekräftigem Titel und vervollständigen Sie die PR-Vorlage. Fordern Sie Reviews von Code-Ownern und Stakeholdern an. Beantworten Sie Feedback umgehend und stellen Sie sicher, dass alle Checks bestehen, bevor Sie mergen. </target>
+      </trans-unit>
+      <trans-unit id="workflowShipCommand" datatype="html">
+        <source>/ship</source>
+        <target>/ship</target>
+      </trans-unit>
+      <trans-unit id="headerWorkflow" datatype="html">
+        <source>Workflow</source>
+        <target>Workflow</target>
+      </trans-unit>
     </body>
   </file>
 </xliff>