Files

pukpuk cf0f779ad4 feat: introduce spec-workflow and upgrade frontend dependencies

This commit introduces the spec-workflow, a set of templates for creating design, product, requirements, and other specification documents. These templates are added to both the root directory and the `apps/frontend` workspace.

Additionally, this commit upgrades the frontend development dependencies for the Astro application. The key changes include:
- Migration from `@astrojs/tailwind` to `@tailwindcss/vite` for Tailwind CSS integration.
- Deletion of the `postcss.config.cjs` file, as it is no longer needed with the new setup.
- Updates to `astro.config.mjs` to use the new Vite plugin for Tailwind CSS.
- General upgrade of Astro and other related dependencies in `apps/frontend/package.json` and the corresponding `pnpm-lock.yaml` file.

2025-10-06 12:35:06 +08:00

2.6 KiB

Raw Blame History

Design Document

Overview

[High-level description of the feature and its place in the overall system]

Steering Document Alignment

Technical Standards (tech.md)

[How the design follows documented technical patterns and standards]

Project Structure (structure.md)

[How the implementation will follow project organization conventions]

Code Reuse Analysis

[What existing code will be leveraged, extended, or integrated with this feature]

Existing Components to Leverage

[Component/Utility Name]: [How it will be used]
[Service/Helper Name]: [How it will be extended]

Integration Points

[Existing System/API]: [How the new feature will integrate]
[Database/Storage]: [How data will connect to existing schemas]

Architecture

[Describe the overall architecture and design patterns used]

Modular Design Principles

Single File Responsibility: Each file should handle one specific concern or domain
Component Isolation: Create small, focused components rather than large monolithic files
Service Layer Separation: Separate data access, business logic, and presentation layers
Utility Modularity: Break utilities into focused, single-purpose modules

graph TD
    A[Component A] --> B[Component B]
    B --> C[Component C]

Components and Interfaces

Component 1

Purpose: [What this component does]
Interfaces: [Public methods/APIs]
Dependencies: [What it depends on]
Reuses: [Existing components/utilities it builds upon]

Component 2

Purpose: [What this component does]
Interfaces: [Public methods/APIs]
Dependencies: [What it depends on]
Reuses: [Existing components/utilities it builds upon]

Data Models

Model 1

[Define the structure of Model1 in your language]
- id: [unique identifier type]
- name: [string/text type]
- [Additional properties as needed]

Model 2

[Define the structure of Model2 in your language]
- id: [unique identifier type]
- [Additional properties as needed]

Error Handling

Error Scenarios

Scenario 1: [Description]
- Handling: [How to handle]
- User Impact: [What user sees]
Scenario 2: [Description]
- Handling: [How to handle]
- User Impact: [What user sees]

Testing Strategy

Unit Testing

[Unit testing approach]
[Key components to test]

Integration Testing

[Integration testing approach]
[Key flows to test]

End-to-End Testing

[E2E testing approach]
[User scenarios to test]

2.6 KiB Raw Blame History