diff --git a/.cursor/commands/plan.md b/.cursor/commands/plan.md
index 5375efe..7ac8853 100644
--- 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
new file mode 100644
index 0000000..f8b2e6e
--- /dev/null
+++ 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
index c02f87d..61da28a 100644
--- 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
index fa4bdce..783e72c 100644
--- a/apps/frontend-tsef/src/i18n/messages.de.xlf
+++ b/apps/frontend-tsef/src/i18n/messages.de.xlf
@@ -208,7 +208,7 @@
The fastest way to an AI-ready Nx workspace
- Der schnellste Weg zu einem KI-bereiten Nx-Workspace
+ Der schnellste Weg zu einem KI-gestützten Nx-Workspace Enterprise-grade TypeScript stack with smart Nx workflows, agent-powered tooling, and built-in compliance.
@@ -384,7 +384,7 @@
The AI-ready TypeScript Enterprise Framework
- Das KI-bereite TypeScript Enterprise Framework
+ Das KI-gestützte TypeScript Enterprise Framework Enterprise-grade Nx workflow with AI-powered development agents and built-in compliance.
@@ -432,7 +432,7 @@
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.
- 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.
+ 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.TSEF, TypeScript, Enterprise Framework, AI-ready, Angular, web development, scalable, application framework, cloud, modern apps, enterprise solutions, software tools, best practices
@@ -758,6 +758,74 @@
Built-in compliance, automated monitoring, enterprise governance rulesIntegrierte Compliance, automatisiertes Monitoring, Unternehmens-Governance-Regeln
+
+ Transform your development workflow with AI-powered automation
+ Transformieren Sie Ihren Entwicklungsworkflow mit KI-gestützter Automatisierung
+
+
+ Streamline your entire development lifecycle from research to ship with intelligent Cursor commands. Built on proven Nx monorepo architecture for enterprise-grade reliability.
+ Optimieren Sie Ihren gesamten Entwicklungslebenszyklus von Research bis Ship mit intelligenten Cursor-Befehlen. Auf bewährter Nx-Monorepo-Architektur aufgebaut für unternehmensreife Zuverlässigkeit.
+
+
+ AI-Assisted Development Workflow
+ KI-gestützter Entwicklungsworkflow
+
+
+ Follow our structured four-step workflow to ensure quality and consistency. Start with research, create a detailed plan, then implement and finally ship your features with confidence.
+ Folgen Sie unserem strukturierten Vier-Schritte-Workflow, um Qualität und Konsistenz sicherzustellen. Beginnen Sie mit Research, erstellen Sie einen detaillierten Plan, dann Implementieren Sie und schließlich Ship Sie Ihre Features mit Vertrauen.
+
+
+ /research
+ /research
+
+
+ 1. Research
+ 1. Research
+
+
+ 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.
+ 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.
+
+
+ 2. Plan
+ 2. Plan
+
+
+ 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.
+ Ü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.
+
+
+ /plan
+ /plan
+
+
+ /implement
+ /implement
+
+
+ 3. Implement
+ 3. Implementieren
+
+
+ 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.
+ 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.
+
+
+ 4. Ship
+ 4. Ausliefern
+
+
+ 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.
+ Ö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.
+
+
+ /ship
+ /ship
+
+
+ Workflow
+ Workflow
+
diff --git a/apps/frontend-tsef/src/i18n/messages.xlf b/apps/frontend-tsef/src/i18n/messages.xlf
index 14e5c10..1264788 100644
--- a/apps/frontend-tsef/src/i18n/messages.xlf
+++ b/apps/frontend-tsef/src/i18n/messages.xlf
@@ -138,6 +138,10 @@