Notice: This page requires JavaScript to function properly.
Please enable JavaScript in your browser settings or update your browser.
Lære Watch It Build, Iterate, Brand | Customizing Claude with Plugins
AI for Office Productivity

Watch It Build, Iterate, Brand

Sveip for å vise menyen

After the discovery phase, the builder skills generate the core components of your Claude OS, including projects, scheduled tasks, and a dashboard. Because the planning work has already been completed, the process requires minimal manual setup.

The first generated version is rarely perfect. You may encounter formatting issues, unnecessary modules, or incorrect outputs. This is a normal part of the process. Review the result, identify what needs improvement, provide targeted feedback to Claude, and repeat until the system matches your needs.

If desired, you can also customize the dashboard's appearance to match an existing brand or design system. This step is optional and is primarily useful for dashboards that will be shared with a team or presented in a professional environment.

Step 1: Run the builders
expand arrow

Approve the architect's plan and let the builder skills generate projects, routines, and the dashboard automatically.

Step 2: Understand the process
expand arrow

The previous planning work is essential. It enables you to understand, customize, and troubleshoot the generated system instead of relying on a template you cannot maintain.

Step 3: Avoid duplicate components
expand arrow

If you already have working routines or projects, reuse them instead of creating duplicates to keep your Claude OS organized.

Step 4: Review the generated dashboard
expand arrow

Once the dashboard is created, open it and verify that it displays the information you expect.

Step 5: Identify issues
expand arrow

The first version may contain formatting problems, incorrect data, or placeholder content. Treat it as a draft rather than a finished product.

Step 6: Iterate with feedback
expand arrow

Provide screenshots and describe the problems clearly. Claude can use this feedback to refine the dashboard over multiple iterations.

Step 7: Add more context
expand arrow

If Claude asks follow-up questions about your tools or workflows, provide specific answers to improve the generated result.

Step 8: Stop when it is useful
expand arrow

Aim for a functional dashboard that supports your daily work. Minor improvements can always be made later.

Step 9: Customize the design (Optional)
expand arrow

If needed, update the dashboard's appearance to match your personal or company branding after the core functionality is complete.

question mark

What is the recommended way to improve the first version of a generated dashboard?

Velg det helt riktige svaret

Alt var klart?

Hvordan kan vi forbedre det?

Takk for tilbakemeldingene dine!

Seksjon 5. Kapittel 2

Spør AI

expand

Spør AI

ChatGPT

Spør om hva du vil, eller prøv ett av de foreslåtte spørsmålene for å starte chatten vår

Watch It Build, Iterate, Brand

After the discovery phase, the builder skills generate the core components of your Claude OS, including projects, scheduled tasks, and a dashboard. Because the planning work has already been completed, the process requires minimal manual setup.

The first generated version is rarely perfect. You may encounter formatting issues, unnecessary modules, or incorrect outputs. This is a normal part of the process. Review the result, identify what needs improvement, provide targeted feedback to Claude, and repeat until the system matches your needs.

If desired, you can also customize the dashboard's appearance to match an existing brand or design system. This step is optional and is primarily useful for dashboards that will be shared with a team or presented in a professional environment.

Step 1: Run the builders
expand arrow

Approve the architect's plan and let the builder skills generate projects, routines, and the dashboard automatically.

Step 2: Understand the process
expand arrow

The previous planning work is essential. It enables you to understand, customize, and troubleshoot the generated system instead of relying on a template you cannot maintain.

Step 3: Avoid duplicate components
expand arrow

If you already have working routines or projects, reuse them instead of creating duplicates to keep your Claude OS organized.

Step 4: Review the generated dashboard
expand arrow

Once the dashboard is created, open it and verify that it displays the information you expect.

Step 5: Identify issues
expand arrow

The first version may contain formatting problems, incorrect data, or placeholder content. Treat it as a draft rather than a finished product.

Step 6: Iterate with feedback
expand arrow

Provide screenshots and describe the problems clearly. Claude can use this feedback to refine the dashboard over multiple iterations.

Step 7: Add more context
expand arrow

If Claude asks follow-up questions about your tools or workflows, provide specific answers to improve the generated result.

Step 8: Stop when it is useful
expand arrow

Aim for a functional dashboard that supports your daily work. Minor improvements can always be made later.

Step 9: Customize the design (Optional)
expand arrow

If needed, update the dashboard's appearance to match your personal or company branding after the core functionality is complete.

Alt var klart?

Hvordan kan vi forbedre det?

Takk for tilbakemeldingene dine!

Seksjon 5. Kapittel 2
some-alt