feat: add frontend development guidelines and structure documentation

- Introduced API guidelines for interface contracts and request handling.
- Added design tokens usage guidelines for consistent styling across the project.
- Established DTO guidelines for defining request parameters and response data types.
- Created frontend structure guidelines to clarify directory organization and code placement rules.
- Compiled a comprehensive frontend development guideline document covering various aspects of the development process.
- Implemented quality guidelines to ensure code maintainability and adherence to best practices.

AI-RD-Workflow/20-skills/se-requirement-review/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: se-requirement-review
+description: Review PM-side requirement artifacts from an SE perspective. Use when Codex needs to evaluate whether UR, requirement analysis, and scenario analysis are ready to become engineering objective requirements and development requirements.
+---
+
+# SE Requirement Review
+
+Review PM artifacts for engineering readiness.
+
+## Inputs
+
+- UR.
+- RA.
+- SA.
+- PM open questions and review notes.
+
+## Process
+
+1. Check whether business requirements can be translated into engineering outcomes.
+2. Identify missing non-functional requirements.
+3. Identify interface, data, dependency, integration, permission, migration, and compatibility concerns.
+4. Identify architectural or delivery risks.
+5. Mark unresolved questions that block OR or DR.
+
+## Output
+
+Produce an SE review note with:
+
+- Engineering readiness decision.
+- Blocking questions.
+- Required technical clarifications.
+- Risk list.
+- Suggested OR/DR breakdown.
+
+## Decision
+
+Use one of:
+
+- `ready-for-or-dr`
+- `ready-with-risks`
+- `blocked`