Best practices for already existing Apps?

[h-aburesha]

Hey,

What are the best practices for an already existing App with BE/FE Structures and a design system?

I have been sparring with Claude and it mentioned design-os is not particularly designed for non greenfield projects, but maybe for expanding new features?

These are some of the prompts Claude recommended:

For your BE repo:

I'm setting up Design OS (https://buildermethods.com/design-os) to design new features for this existing app.

Design OS has a /data-model command that defines "the nouns of the system" - entities, relationships, and data structure. I need to give it context about what already exists so it doesn't reinvent our schema.

Analyze this codebase and create a data model summary that includes:

1. All entities/models with their fields and data types
2. Relationships between entities (one-to-many, many-to-many, etc.)
3. Any enums or constant values
4. Key API endpoints and what data they return

Format this so I can paste it as context when running Design OS commands.

For your FE repo:

I'm setting up Design OS (https://buildermethods.com/design-os) to design new features for this existing app.

Design OS has a /design-system command that defines colors, typography, and the app shell. I need to give it context about our existing design tokens so new designs match what we have.

Analyze this codebase and create a design system summary that includes:

1. Color palette (from tailwind config or CSS variables)
2. Typography (fonts, sizes, weights)
3. Main navigation/routing structure  
4. Key reusable components that already exist

Format this so I can paste it as context when running Design OS commands.

Cheers,