ספריית פרומפטים ל-Claude Cowork

Before doing anything, ask me to choose one workflow:

1. Brutal UI Review
2. New Product UX Planning
3. Design System Creation
4. Redesign Options
5. Implementation Prompt
6. QA After Build
7. Convert Screenshot to Modern UI
8. Create Live Artifact Prototype
9. Prepare Claude Code Handoff
10. Prepare Cursor Handoff

For every workflow, give me 4–5 clear options before recommending one.

Do not start implementation until I choose a workflow.

Use the Ran UI Quality Gate skill for this task.

Apply all skill rules:
- Do not jump directly to code.
- First understand the product, user, and main action.
- Review hierarchy, layout, typography, colors, components, mobile, and trust.
- Always give me at least 4–5 options for major decisions.
- Mark one option as recommended, but keep the alternatives visible.
- Produce a practical handoff prompt for implementation.

I want to create a new AI product.

Before writing code, interview the product idea using this structure:

1. Who is the target user?
2. What problem are we solving?
3. What is the main user action?
4. What is the simplest useful version?
5. What should be on the first screen?
6. What should not be built yet?
7. What would make this feel premium, modern, and trustworthy?

Then produce:
1. Product brief
2. UX structure
3. Screen list
4. First screen wireframe description
5. 5 design direction options
6. 5 layout options
7. Product-specific design system
8. Implementation prompt for Claude Code / Cursor / Lovable / v0

Run a brutal UI/UX review.

Do not be polite. Tell me exactly why this looks outdated, generic, cheap, confusing, or unfinished.

Review:
1. First impression
2. Information hierarchy
3. Layout and spacing
4. Typography
5. Colors
6. Buttons
7. Cards
8. Forms
9. Tables
10. Mobile behavior
11. Trust and premium feel
12. Generic AI-demo risk

Output:
1. Immediate diagnosis
2. Top 10 problems
3. What to remove
4. What to simplify
5. What to make more prominent
6. 5 redesign direction options
7. 5 layout options
8. Recommended redesign depth
9. Implementation instructions
10. Final QA checklist

Give me 5 distinct redesign options for this product.

For each option include:
- Name
- Best used when
- Visual style
- Layout idea
- Main advantage
- Tradeoff / risk
- Implementation difficulty
- Recommendation level

Options should be meaningfully different, not cosmetic.

Include at least:
1. Premium Minimal
2. Modern SaaS Dashboard
3. Clean Utility App
4. Dark Professional
5. Enterprise Clean

At the end, recommend one option and explain why.

Create a product-specific design system.

The design system must include:

1. Product design principle
2. Layout rules
3. Typography scale
4. Color palette
5. Spacing system
6. Button system
7. Input and form system
8. Card system
9. Table system
10. Navigation rules
11. Empty states
12. Loading states
13. Error states
14. Mobile behavior
15. RTL rules if relevant

Also give me 4–5 alternative visual directions and mark the recommended one.

Avoid:
- Bootstrap look
- Default Tailwind look
- Random gradients
- Too many icons
- Heavy shadows
- Weak gray text
- Generic SaaS template feel

Create a precise implementation handoff prompt for Claude Code / Cursor.

Include:

1. Product goal
2. Target user
3. Main user action
4. Current UI problems
5. Selected design direction
6. Selected layout
7. Selected redesign depth
8. Design system rules
9. Component rules
10. Mobile rules
11. What to remove
12. What to simplify
13. What to make more prominent
14. Files/components likely to change
15. Step-by-step implementation plan
16. Final QA checklist

Important:
- Do not produce vague advice.
- Write a copy-paste prompt.
- Include strict rules against generic UI.
- Ask the coding tool to summarize planned changes before editing.

Prepare a Claude Code handoff.

Goal:
Improve the UI without breaking existing functionality.

Instructions for Claude Code:
1. Inspect the project structure first.
2. Identify the relevant UI files before editing.
3. Summarize the planned changes.
4. Do not rewrite unrelated business logic.
5. Preserve existing data flow unless a UX issue requires change.
6. Apply the selected design system consistently.
7. Refactor components instead of duplicating styles.
8. Make the UI responsive and mobile-safe.
9. Run a final self-review against the UI checklist.

Output a copy-paste prompt I can give directly to Claude Code.

Prepare a Cursor handoff prompt.

The prompt should:
1. Explain the UI goal clearly.
2. Tell Cursor which files/components to inspect first.
3. List the exact UI problems to fix.
4. Define the design system rules.
5. Define the component behavior.
6. Require responsive/mobile checks.
7. Prevent random styling changes.
8. Require a before/after summary.

Make it practical for editing an existing codebase in an IDE.

Create a strict prompt for Lovable / v0 to generate a modern UI.

The prompt must include:
1. Product purpose
2. Target user
3. Main action
4. Required sections
5. Selected design direction
6. Selected layout
7. Product-specific design system
8. Component rules
9. Mobile-first behavior
10. Things to avoid

Important:
Tell Lovable / v0:
- Do not generate generic SaaS template UI.
- Do not use random gradients.
- Do not overuse icons.
- Do not create crowded cards.
- Do not use weak gray text everywhere.
- Use strong hierarchy, clean spacing, and one primary action color.

Output a single copy-paste prompt.

Run a final UI QA review after implementation.

Score from 1–5:
1. First impression
2. Main action clarity
3. Information hierarchy
4. Layout and spacing
5. Typography
6. Colors
7. Component consistency
8. Mobile readiness
9. Trust and premium feel
10. Generic AI-demo risk

Then output:
1. Total score
2. What improved
3. What still looks weak
4. What should be fixed next
5. 5 next-step options
6. Recommended next action

Be direct. If it still looks like a demo, say so.

Analyze this screenshot and redesign it as a modern product UI.

Steps:
1. Identify the screen purpose.
2. Identify the main user action.
3. Diagnose why the current UI feels outdated/generic.
4. Propose 5 redesign directions.
5. Propose 5 layout structures.
6. Recommend one direction and one layout.
7. Create a product-specific design system.
8. Create an implementation prompt.

Do not only polish the existing screen if the structure is weak.
Redesign deeply when needed.

Create a persistent interactive Live Artifact called:

Ran UI Quality Control Dashboard

The artifact must be an interactive Hebrew RTL dashboard for reviewing, scoring, and upgrading AI-generated product interfaces.

It must include:
1. Product intake form
2. UI scorecard
3. Red flags checklist
4. 5 design direction options
5. 5 layout options
6. 5 redesign depth options
7. 5 implementation path options
8. Generated prompt area
9. Brutal UI review generator
10. Product-specific design system generator
11. Claude Code / Cursor / Lovable handoff generators
12. History table

Design:
- Modern SaaS
- Premium Minimal
- Clean utility dashboard
- Strong typography
- Spacious layout
- One primary action color
- RTL Hebrew labels
- Mobile friendly
- No Bootstrap look
- No generic Tailwind look

Build the full interactive artifact now.

Safety rules for this Cowork task:

Work only inside the project folder I specify.
Do not delete files.
Do not send messages.
Do not publish anything.
Do not make purchases.
Do not change source files before summarizing the plan.
Ask before making destructive or irreversible changes.
If something is ambiguous, choose the safest non-destructive path.
At the end, summarize exactly what you changed and what you did not change.

Run a Before / After UI improvement loop.

Workflow:
1. Review the before version.
2. Score it from 1–5 in key UI areas.
3. Identify the top problems.
4. Give 5 redesign options.
5. Wait for my selected option.
6. Generate an implementation handoff.
7. After implementation, review the after version.
8. Score again.
9. Compare before vs after.
10. Give 5 next-step options.

Do not skip the scoring step.
Do not jump directly to implementation.

Improve the UI of this existing product without breaking functionality.

Rules:
1. Preserve existing business logic.
2. Preserve existing data flow unless there is a clear UX reason to change it.
3. Focus on layout, typography, colors, spacing, and component consistency.
4. Identify reusable components.
5. Remove duplicate styling.
6. Apply a clear design system.
7. Improve mobile behavior.
8. Do not introduce unnecessary dependencies.
9. Summarize changes before implementation.
10. Run final QA after implementation.

Before editing, give me:
- 5 redesign depth options
- Recommended level
- Files likely to be changed
- Risks

Important rule:

For every major decision, give me at least 4–5 clear options.

This includes:
- Design direction
- Layout
- Redesign depth
- Implementation path
- Product structure
- Next steps
- Visual style
- Tool choice

For each option include:
1. Short name
2. Best used when
3. Main advantage
4. Tradeoff / risk
5. Recommendation level

You may recommend one option, but do not hide the alternatives.

The current design risks looking like a generic AI-generated template.

Upgrade it using these rules:

Avoid:
- Default Tailwind look
- Bootstrap admin-panel feel
- Random gradients
- Too many icons
- Too many floating cards
- Weak gray text
- Heavy shadows
- Crowded layout
- Hero section that feels like a template
- Generic SaaS dashboard structure

Improve:
- Stronger information hierarchy
- More deliberate spacing
- Better typography
- Clearer primary action
- Fewer but stronger components
- Better mobile layout
- More premium and trustworthy feel

Give me 5 concrete redesign options and recommend one.